Splunk Search

Calculate hourly usage from Machine data

shashank_24
Path Finder

Hi, I have uploaded a JSON data from one of my APM tools into Splunk to get some meaningful insights. The events are there for every hour. Every event has 2 fields timeFrameStart & timeFrameEnd which are coming as Epoch time and I have converted them into human readable format. There is another fields called Visits which tells me how many visits were there in that hour.

My requirement is to plot a hourly usage graph with time as x-axis (probably derive from timeFrameStart field) and visits on the y-axis. I've written a base query -

 

source="mydataarchive" host="splunkdev" index="test_index"
| eval startTime=strftime(timeFrameStart/1000,"%a,%d %b %Y %H:%M:%S") 
| eval endTime=strftime(timeFrameEnd/1000,"%a,%d %b %Y %H:%M:%S") 
| table startTime endTime visits

 

Let me know if anyone can advice on this using stats or timechart command.

Labels (4)
0 Karma

kamlesh_vaghela
SplunkTrust
SplunkTrust

@shashank_24 

Can you please try this for timechart?

source="mydataarchive" host="splunkdev" index="test_index"
| eval timeFrameStart=timeFrameStart/1000, timeFrameEnd=timeFrameEnd/1000, usage=timeFrameEnd-timeFrameStart, _time=timeFrameStart
| timechart span=1h sum(usage) as usage sum(Visits) as Visits

 

shashank_24
Path Finder

@kamlesh_vaghela  It's not working. What i want is hourly chart with visits on y-axis. _time field is coming as index time which I don't want.

I want to plot against the time field 

timeFrameStart
0 Karma

kamlesh_vaghela
SplunkTrust
SplunkTrust

@shashank_24 

If you observe the search I'm overwrite the _time by doing eval. It isn't working? 

_time=timeFrameStart

 

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...