Splunk Search

Timechart Dropping Empty Buckets

werz
New Member

I am trying to create a search that provides me with the predicted average usage of a machine during the course of a month. The data logging this information is in an SQL database, which I query (using the dbconnect app) to gather a set of Date and Duration pairs which describe when the machine was used and for how long.

Here is what my query looks like:

|dbquery ..... | rename Date as _time | timechart span=1d sum(Duration) as dailySumDuration | stats avg(dailySumDuration) as avgDuration | eval monthlyDuration=(avgDuration*30)

My issue with this query is that timechart does not fill in 0's for my empty buckets, so the daily average is only the average for days when the systems are used which overinflates my estimate.

Is there any way to force timechart to fill in empty days with 0's so I can average over them?

Thanks

Tags (3)
0 Karma

mishin
Explorer

I think

| timechart cont=FALSE sum(count) by IP

help you

0 Karma

sdaniels
Splunk Employee
Splunk Employee

You'll want to use fillnull.

Replaces null values with a user specified value (default 0). Null values are those missing in a particular result, but present for some other result. If a field-list is provided, fillnull is applied to only fields in the given list (including any fields that does not exist at all). Otherwise, applies to all existing fields.

http://docs.splunk.com/Documentation/Splunk/6.0/SearchReference/Fillnull

0 Karma

linu1988
Champion
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!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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 ...