Splunk AppDynamics

Monitor application is running or not from appdynamics

CommunityUser
Splunk Employee
Splunk Employee

Hi All,

Good Morning/Good Evening/Good Afternoon,

I have a requirement like, I am having one application running in PCF. I need to receive a mail notification whenever the application goes down. I am able to create policy and alerts in AppDynamics dashboard but the alerts are coming only when at the time of restarting the application and some specific scenarios. But I need something like AppDynamics should check the application in 10 to 15 minutes of time gaps and if the application is down it should send an email to me.

Can you someone please help me on how to setup this.

Your help is highly apricated.  

Thanks,

Siva Nandigam

Labels (1)
0 Karma
1 Solution

Vaibhav_Vir_Sin
Communicator
Hi Siva,
Have you tried below configuration while setting up health rules? See if it helps.

*************
Using Health Rule Conditions to evaluate agent availability metrics can result in false positives. For example:

Agents may not be connecting with controllers due to communication errors for a couple of minutes.
Data may be delayed for a couple of minutes due to latency issues.

You can avoid occasional 1-2 minute metric loss due to network issues or late arrival by configuring your Health Rule as follows:
Select Nodes for what the Health Rule affects. Tiers can be set, but more often we recommend setting Nodes.
Select Node Health - Hardware, JVM, CLR as the Type.
Use the last 5 minutes, with a wait time of 10 minutes.
Set your condition to be the Sum of < Specific Value of 3.
This will generate a violation when the agent is down for more than 2 minutes in the last 5 mins.
**********

View solution in original post

Vaibhav_Vir_Sin
Communicator
Hi Siva,
Have you tried below configuration while setting up health rules? See if it helps.

*************
Using Health Rule Conditions to evaluate agent availability metrics can result in false positives. For example:

Agents may not be connecting with controllers due to communication errors for a couple of minutes.
Data may be delayed for a couple of minutes due to latency issues.

You can avoid occasional 1-2 minute metric loss due to network issues or late arrival by configuring your Health Rule as follows:
Select Nodes for what the Health Rule affects. Tiers can be set, but more often we recommend setting Nodes.
Select Node Health - Hardware, JVM, CLR as the Type.
Use the last 5 minutes, with a wait time of 10 minutes.
Set your condition to be the Sum of < Specific Value of 3.
This will generate a violation when the agent is down for more than 2 minutes in the last 5 mins.
**********

CommunityUser
Splunk Employee
Splunk Employee

Thank you Vaibhav, it helped me as well.

Get Updates on the Splunk Community!

Good Sourcetype Naming

When it comes to getting data in, one of the earliest decisions made is what to use as a sourcetype. Often, ...

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Splunk App for Anomaly Detection End of Life Announcement

Q: What is happening to the Splunk App for Anomaly Detection?A: Splunk is officially announcing the ...