JBoss/WildFly

Host

To configure this check for an Agent running on a host:

Metric collection

1. Edit the jboss_wildfly.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your JBoss or WildFly application server’s performance data. See the sample jboss_wildfly.d/conf.yaml for all available configuration options.

   Depending on your server setup (particularly when using the remote+http JMX scheme), you may need to specify a custom JAR to connect to the server. Place the JAR on the same machine as your Agent, and add its path to the custom_jar_paths option in your jboss_wildfly.d/conf.yaml file.

   Note: The JMX url scheme is different according to your WildFly version:

   • For Wildfly 9 and older: service:jmx:http-remoting-jmx://<HOST>:<PORT>
   • For Wildfly 10+: service:jmx:remote+http://<HOST>:<PORT>

   Refer to the WildFly JMX subsystem configuration page for more information.

2. Restart the Agent.

Log collection

Available for Agent versions >6.0

1. Collecting logs is disabled by default in the Datadog Agent, enable it in your datadog.yaml file:

   logs_enabled: true

2. Next, edit jboss_wildfly.d/conf.yaml by uncommenting the logs lines at the bottom. Update the logs path with the correct path to your JBoss log files.

   logs:
    - type: file
      path: /opt/jboss/wildfly/standalone/log/*.log
      source: jboss_wildfly
      service: '<APPLICATION_NAME>'

3. Restart the Agent.

Containerized

Metric collection

For containerized environments, see the Autodiscovery with JMX guide.

Log collection

Available for Agent versions >6.0

Collecting logs is disabled by default in the Datadog Agent. To enable it, see the Kubernetes log collection documentation.