I was comparing the "Memory Usable" metric collected by JMX with the built-in "Memory Usable" metric collected by the Java Agent on a CentOS server and noticed discrepancies between the two:
When I ran the "free" command, I saw the following:
free
total used free shared buff/cache available
Mem: 15401136 730028 13714196 49436 956912 12840340
Swap: 0 0 0
How is the "Memory Usable" metric being calculated by the Java Agent? And will this discrepancy apply to all of the other host metrics?
DECEMBER 12, 10:00 AM GMT / 2:00 PM ET
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 10, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 10, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 10, 4:00 pm CET / 10:00 am ET
Register here
Instrumenting Agents on Apigee Components 2 Answers
Anyone know how to monitor hp service manager (sm) backend ? 2 Answers
Disconnected transaction flow 1 Answer
leak analysis memory snapshot automatically triggered settings capture string 6.5 appmon 6 Answers
WARNING [AbstractBaselinesCenter] [Baselining] in Server.log 1 Answer