Monitoring JBoss AS
TABLE OF CONTENTS
Currently, supported versions are JBoss 4.0, or newer, and Wildfly.
Currently, Instana cannot automatically enable the Wildfly statistics it uses.
For Wildfly to collect metrics, Instana uses enable statistics for undertow and datasources like this:
<subsystem xmlns="urn:jboss:domain:undertow:3.0" statistics-enabled="true"> <datasource jta="true" jndi-name="java:jboss/datasources/DemoDS" pool-name="DemoDS" enabled="true" statistics-enabled="true">
Instana is naming a JBoss using the
jboss node name that can be specified using:
At large scale, the JBoss API seems to be really inefficient at large scale. Therefore, the sensor polls performance metrics every 5 seconds, and it can be configured using the
On some legacy JBoss versions and due to bugs, calls to retrieve EJB deployments data can cause various errors.
The sensor monitors EJB deployments by default, but in case these bugs happen or if it's just unnecessary,
it can be disabled with the
monitor-ejb-deployments flag in the configuration file
com.instana.plugin.jbossas: metrics-interval: 5 # seconds monitor-ejb-deployments: false
- Requests, Response Times
- EJB Pool
- Connection Pools (available only for JBoss 4)
- Thread Pools (available only for JBoss 4)
For each sensor, there is a curated knowledgebase of health signatures that are evaluated continuously against the incoming metrics and are used to raise issues or incidents depending on user impact.
Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of any given entity.
For information about built-events for the JBoss AS sensor, see the Built-in events reference.