Splunk Search
Highlighted

Dashboard Update Monthly Scans

Path Finder

Hello, I created a series of dashboards that will automatically update when data from a monthly scan is ingested. In this scenario, I have a scan that runs on the 18th of every month and automatically gets sent to Splunk shortly after the scan concludes. In this case, the scan typically finishes between 0330 and 0500. I have the "Advanced" time range configured as follows:

@mon17+3h - @mon17+6h

The issue I'm running into is that by the time the first of the month rolls around, all information on that dashboard resets because it now views the '@mon' as the current month, and there is obviously no data for 18 days into the future.

Is there a better way to configure my search ranges that someone could suggest? I appreciate any and all assistance. Thank you!

Tags (2)
0 Karma
Highlighted

Re: Dashboard Update Monthly Scans

SplunkTrust
SplunkTrust

Give this a try for your time range

earliest: +11d-1mon@mon+17+3h
latest=: +11d-1mon@mon+17+6h

0 Karma
Highlighted

Re: Dashboard Update Monthly Scans

Path Finder

This did not resolve my issue. It only set the time back to last month. Thank you for the suggestion though.

0 Karma
Highlighted

Re: Dashboard Update Monthly Scans

SplunkTrust
SplunkTrust

I think I copied it wrong in my previous comments. The correct values are earliest: +11d-1mon@mon+16d+3h and latest=: +11d-1mon@mon+16d+6h. See this runanywhere sample to see how the time range changes with current date.

| gentimes start=-50 | eval current=starttime   | table current| eval earliest=relative_time(current,"+11d-1mon@mon+16d+3h") | eval latest=relative_time(current,"+11d-1mon@mon+16d+6h") | convert ctime(*) as *_human
0 Karma
Speak Up for Splunk Careers!

We want to better understand the impact Splunk experience and expertise has has on individuals' careers, and help highlight the growing demand for Splunk skills.