Dashboards & Visualizations

timerange for the history command

paulathome
Path Finder

I've noticed that running the "| history" command will return different results based on the setting of the timerangepicker. So my question is how can I define the earliest and latest values within the search bar, or in a dashboard panel's query?

| history earliest=-24h                 does not work
earliest=-24h | history                 does not work

and I'm fairly confident that anything downstream from the history command won't be able to influence how many results were delivered initially by the history command.

0 Karma
1 Solution

paulathome
Path Finder

I was using this in a dashboard panel to nicely display the last few searches that a user performed and I was able to set the earliest and latest in the Search module. Couple that with a Pager, Table, HTML and a redirector module I was all set.

Thanks Sideview Utils,
Paul

View solution in original post

0 Karma

somesoni2
Revered Legend

You would not be able to add earliest or latest value in a query (within search bar or a dashboard query) involving '|history'. The only option is the use timerangepicker (from searchbar) or from param "earliest" or latest within dashboard xml.

paulathome
Path Finder

I was using this in a dashboard panel to nicely display the last few searches that a user performed and I was able to set the earliest and latest in the Search module. Couple that with a Pager, Table, HTML and a redirector module I was all set.

Thanks Sideview Utils,
Paul

0 Karma
Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...