All Apps and Add-ons

TimeWrap Bug?

DPZ_Luke
Explorer

So I think this may be a bug. Timewrap seems to only take single number h,w,m values.
For example, this
sourcetype="wineventlog:application" "Type=Warning" "EventCode=1" earliest=-4w | timechart count span=1h | timewrap 19h series=relative
Will plot graphs of every 9 hours, NOT every 19 hours.
Ditto if I make it timewrap 11h, it will be 1 hour not 11 hours.

Comments?

Tags (1)
1 Solution

carasso
Splunk Employee
Splunk Employee

Thanks. I just fixed it.

I also threw in a new command called 'drilldown' that handles "* | top 10 host useother=t", which allows you to drilldown on 'other' values and do the right thing.

View solution in original post

0 Karma

carasso
Splunk Employee
Splunk Employee

Thanks. I just fixed it.

I also threw in a new command called 'drilldown' that handles "* | top 10 host useother=t", which allows you to drilldown on 'other' values and do the right thing.

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

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...