Splunk AppDynamics

Specific time based Health Rules

srimukundant
New Member

Hi, I also have the same issue 

I want to trigger the alert like below.

Once the alert starts, there should an alert.

After a certain amount of time, say 4 hours, I should get another alert. I should not get the alert in between.

Did anyone reply to this or is there any solution like setting up the throttle?

This post is related to this existing Community post: https://community.appdynamics.com/t5/Dashboards/Time-based-health-rules-not-possible/m-p/29930#M337

Labels (1)
Tags (2)
0 Karma

Hiroki_Ito
Contributor

Thank you for posting to the community.
As written in the last comment at the related post, you can use "Wait time after violation" to throttle the continuing health rule violations.

For example, if you set 240 minutes(4 hours) of "Wait time after violation" on a health rule and health rule violation continues for 4 hours, then you will get an alert at the beginning and after 4 hours.
* If the violation doesn't continue for 4 hours, you will get an alert after violation is triggered again even within 4 hours. By setting "Use data from last" with a large value, the violation may continue for a long time.

Best Regards,

Hiroki
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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

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