MemoryPool stats not available on Dynatrace instrumented JVM
You can create a new dashboard with a chart on it. On that chart you put measures any measure under Server-Side Performance->Agent based Measures->Java Virtual Machine
Give that a try and let me know what you see!
Hi,
I am not able to access the System Information dashlet from DT client with my credentials, but i checked the agent log files directly and don't see any specific errors, only few like the one below related to connectivity errors:
2014-10-11 20:06:28 [ffff887c] severe [native] Exception in controller: util::SocketConnection::receiveExact(), 70014, End of file found. Retrying every 10 seconds.
2014-10-11 20:06:38 [ffff887c] warning [native] Control channel connection to dtserver.com:9903 lost. Retrying every 10 seconds.
2014-10-11 20:06:42 [80ef987d] warning [native] Instrumentation channel disconnected: server did not reply to ping request
2014-10-11 20:06:47 [fe08c87c] warning [native] Exception occurred while sending events: sendExactOnce(), 32, Broken pipe
2014-10-11 20:07:15 [80ef987d] info [native] Instrumentation channel connected successfully
Is there an option within Dynatrace where the memory pool values can be plotted to check if they are recorded ?
Is there anything in the agent log files that would indicate a problem? You can access the agent log files through the System Information dashlet.
That would be a start. If this doesnt help I would almost suggest to open a support ticket
Sorry about the junk content in the message body, looks like a browser issue that didn't render the message post area properly, hence adding the question as a comment :
We have been noticing an issue where some of the JVM stats under java.lang MemoryPool like CMS Perm Gen and CMS Old Gen are not reported correctly for Dynatrace instrumented JVMs. We have a Graphite based dashboard that pulls metrics from the JVMs and it was noticed that for instrumented JVMs the value is reported as 0 after startup, while for other non-instrumented JVMs with the exact same configuration, it's coming up fine immediately after startup (as expected). In some cases, the permgen starts reporting after a while if there's traffic to the JVM, while we have seen a server with almost no traffic, where the value remained at 0 for more than a month, until a memory snapshot was triggered from Dynatrace. The permgen value shows correctly when checked directly through JConsole.
Environment :
Linux, Dynatrace 5.6
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
