Monitoring: JMX alerts

Request description

We are currently workig to improve our monitoring activity in Dynatrace, the tool used internally in our company.
We are already exploiting the following metrics :

Domaine : Simplicite

  • List item
  • Activeusers
  • Cacheobject
  • Cacheobjectmax
  • Cacheprocess
  • Cacheprocessmax
  • Contextpath
  • Encoding
  • Heapfreesize
  • Heapmaxsize
  • Heapsize
  • Inactiveusers
  • Licensedusers
  • Pendingusers
  • Sessions
  • Version

Domaine : org.apache.commons.pool2

  • BorrowedCount
  • CreatedCount
  • DestroyedByBorrowValidationCount
  • DestroyedByEvictorCount
  • DestroyedCount
  • MaxBorrowWaitTimeMillis
  • MaxIdlePerKey
  • MaxTotal
  • MaxTotalPerKey
  • MaxWaitMillis
  • MeanActiveTimeMillis
  • MeanBorrowWaitTimeMillis
  • MeanIdleTimeMillis
  • MinEvictableIdleTimeMillis
  • MinIdlePerKey
  • NumActive
  • NumIdle
  • NumTestsPerEvictionRun
  • NumWaiters
  • RemoveAbandonedTimeout
  • ReturnedCount
  • TimeBetweenEvictionRunsMillis

Question: Do you think about other metrics within other classes that we could exploit?

thumbnail_image007

Best regards,
Thierry

Some of the JMX attributs you indicate are not “metrics” but rather confguration constants (e.g. Simplicité platform’s encoding or version, or pools’ max values, etc.) that are not necessarly worth monitoring.

You can also monitor some JMX metrics at Tomcat server-level.

E.g. Tomcat active sessions:

or datasource(s) active connections:

Note: their JMX path may vary depending on your deployment configuration

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.