AppD Archive

JVM monitoring lost

CommunityUser
Splunk Employee
Splunk Employee

A production application node started experiencing high heap usage and then AD stopped monitoring the JVM altogether.  During this state, I could still use JConsole to view the JMX data on that node.  Additionally, another monitoring tool maintained the connection.  The application node itself was still functioning (granted, performance was not great).

1) Why did AD drop this connection and stop gathering data for this node?

2)  How do I get AD to reconnect and resume gathering data on this node?

Neal

0 Karma

Arun_Dasetty
Super Champion

Hi,

We see this is part of support request# 36551, we request you to track support help ticket for further assistance on this query.

We see by default the node property heap-storage-monitor-shutdown-action is true for recent agent version say 4.x and for older agent version say 3.8.x this is false and setting the flag heap-storage-monitor-shutdown-action=false should force the agent to report to controller UI even if jvm is crossing the heap threshold, Hope that answers your query.

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...