Splunk AppDynamics

Health Rule Schedule

CommunityUser
Splunk Employee
Splunk Employee

How to setup Health Rule schedule for the below scenario. I need to avoid getting alerts between 8 AM to 2 PM.

Will the below schedule work?

Mon - 12 to 8 AM EST & 2 PM  to 11 PM EST

Monday

Start Time Cron Expression: 0 0 0,14 ? * 2

End Time Cron Expression:   0 0 8,23 ? * 2

Labels (1)
0 Karma
1 Solution

millerep
Contributor

Ahh ok, same logic, just instead of MON-FRI, you'll just have it kick off 2PM MON, and shut off at 8AM MON, so it'll run fine the other days. 

Here's some additional cron expression documentation which may help: https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm

View solution in original post

millerep
Contributor

If you're just trying to supress an alert between 8am and 2 pm, then under "manage health rule schedules" when creating the health rule, you'll want a start time at 2pm and an end time at 8am. So it'll look something like this:

0 0 14 ? * MON-FRI

0 0 8 ? * MON-FRI

CommunityUser
Splunk Employee
Splunk Employee

Thanks Eric.

But we need to avoid alerts only on Monday 8 AM to 2 PM. Rest of the weekdays we need to be active on all time.

0 Karma

millerep
Contributor

Ahh ok, same logic, just instead of MON-FRI, you'll just have it kick off 2PM MON, and shut off at 8AM MON, so it'll run fine the other days. 

Here's some additional cron expression documentation which may help: https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm

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

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

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...