JBoss AS

Supported versions

Currently supported versions are JBoss 4.0, or newer, and Wildfly.

Configuration

Required Configuration in 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">

JBoss Naming

Instana is naming a JBoss using the jboss node name that can be specified using

-Djboss.node.name=myjbossnodename

Sensor Configuration

On some legacy JBoss versions and due to bugs, calls to retrieve EJB deployments data can cause various errors.
EJB deployments data retrieval is enabled 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 <agent_install_dir>/etc/instana/configuration.yaml:

com.instana.plugin.jbossas:
  monitor-ejb-deployments: false

Metrics collection

Configuration data

  • Version
  • Home
  • Deployments

    • Web
    • EJB
  • Sockets

Performance metrics

  • Servlets
  • Requests, Response Times
  • Sessions
  • Connectors
  • EJB Pool
  • Datasources
  • Connection Pools (available only for JBoss 4)
  • Thread Pools (available only for JBoss 4)

Health Signatures

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.