Splunk Search

timechart where field name and value are both in event data

kmaron
Motivator

I have a database query that runs every 5 minutes. It brings back queue names and the counts of those queues. I would like to make a timechart that would show all of the queues and their counts over time.

My data comes out like this:

2017-02-09 10:51:30 QUEUE="LIFE_UpdatePolicySecurity", LIFE_QUEUE_COUNT="5"
2017-02-09 10:51:30 QUEUE="LIFE_UpdateAnnuitySecurity", LIFE_QUEUE_COUNT="38"
2017-02-09 10:51:30 QUEUE="Policy File Document", LIFE_QUEUE_COUNT="3"
2017-02-09 10:51:30 QUEUE="Annuity File Document", LIFE_QUEUE_COUNT="25"

I would like to eventually end up with a line graph that would have a line or each queue name and show the count for each over time but I'm struggling to get the stats to line up to get it there.

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Have you tried ... | timechart max(LIFE_QUEUE_COUNT) by QUEUE ?

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Have you tried ... | timechart max(LIFE_QUEUE_COUNT) by QUEUE ?

---
If this reply helps you, Karma would be appreciated.

kmaron
Motivator

See I knew it was going to be something simple. I just had to flip my thinking. Thank you so much that's exactly what I wanted!!

0 Karma

somesoni2
Revered Legend

If you've 10 or more distinct QUEUEs, then add limit=0 ( or any feasible number) so that there is a line for every queue.

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...