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
Get Updates on the Splunk Community!

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...

Announcing the Migration of the Splunk Add-on for Microsoft Azure Inputs to ...

Announcing the Migration of the Splunk Add-on for Microsoft Azure Inputs to Officially Supported Splunk ...