Splunk AppDynamics

Health Rule Violation not clearing

CommunityUser
Splunk Employee
Splunk Employee

Howdy,

I originally had my agents on an Amazon LightSail instance with only 1GB of RAM.  I logged into my app dashboard and had a Health Rule Violation "memory utilization" warning for my nodes.  True enough the memory consumption was over 70%.  

I redeployed the instance on a machine with 2GB RAM and my Tier/Node Server dashboard is showing about 40% memory utilization.  However the Health Rule Violation is still present.  For any selected time range.

How do I clear this?  I even tried changing the warning threshold. Tried disabling that particular health rule.  Neither worked.  Any ideas?

Thanks

t

Labels (1)
0 Karma
2 Solutions

Pratik_Maskey
Communicator

Hi Tim,

Is the health rule violation displaying in continuous/ongoing status. If yes could you verify and share screen shot of the health rule configurtion, metric screen shot from metric browser and the violation alert you are getting from appdyanmics.

Do verify the meric values getting reported under metric browser for the required metric and on the basis of reported values we can amend the condition provided under health rule.

Thanks,

Pratik

View solution in original post

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Howdy,

I reset the agents and when that didn’t work, I deleted the nodes. When they came back (or were rediscovered by the controller), it was resolved.

Thanks!

Tim

View solution in original post

0 Karma

Pratik_Maskey
Communicator

Hi Tim,

Is the health rule violation displaying in continuous/ongoing status. If yes could you verify and share screen shot of the health rule configurtion, metric screen shot from metric browser and the violation alert you are getting from appdyanmics.

Do verify the meric values getting reported under metric browser for the required metric and on the basis of reported values we can amend the condition provided under health rule.

Thanks,

Pratik

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Howdy,

I reset the agents and when that didn’t work, I deleted the nodes. When they came back (or were rediscovered by the controller), it was resolved.

Thanks!

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

Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass

Hello Splunkers,  We’re excited to kick off a Splunk Dashboard contest! We know that dashboards are a primary ...

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...

Network to App: Observability Unlocked [May & June Series]

In today’s digital landscape, your environment is no longer confined to the data center. It spans complex ...