Alerting

Trouble Scheduling Alert With Search For Specific Time Range

theironcook
Explorer

For some reason, our network goes crazy every day from 2:30 to 2:35.
I'm trying to schedule a daily alert that will perform a search from 2:30 to 2:35 and report on that data if it's bad/slow.
I've created a daily scheduled alert that "Runs every day" at 15:00.

I then tried to specify my search with an "Advanced" time range of -30min for "Earliest" and -25min for "Latest" but Splunk doesn't like this.

How can I have an alert that is run daily that will only search for the specific time range of 2:30 - 2:35?

Tags (1)
0 Karma
1 Solution

HiroshiSatoh
Champion

I was able to perform an alert. What is the problem?

Cron schedule:0 15 * * *

index=* earliest=-30m@m latest =-25m@m

alt text

View solution in original post

HiroshiSatoh
Champion

I was able to perform an alert. What is the problem?

Cron schedule:0 15 * * *

index=* earliest=-30m@m latest =-25m@m

alt text

theironcook
Explorer

Thank you Hiroshi,
Yes, if I use the chron syntax everything works well. The issue was when I tried to use the "Run every day of the week" option and specify a time.
But the chron syntax works perfectly. Thank you.

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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...