Agent Check: JBoss/WildFly

Overview

This check monitors JBoss and WildFly applications.

Setup

Installation

The JBoss/WildFly check is included in the Datadog Agent package. 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 the path to the custom_jar_paths option.

Configuration

Host

Follow the instructions below to configure this check for an Agent running on a host. For containerized environments, see the Containerized section.

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.

   Note:This check has a limit of 350 metrics per instance. The number of returned metrics is indicated in the info page. You can specify the metrics you are interested in by editing the configuration below. To learn how to customize the collected metrics, visit the JMX Checks documentation for more detailed instructions. If you need to monitor more metrics, contact Datadog support.

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 Docker log collection.

Parameter	Value
<LOG_CONFIG>	{"source": "jboss_wildfly", "service": "<SERVICE_NAME>"}

Validation

Run the Agent's status subcommand and look for jboss_wildfly under the Checks section.

Data Collected

Metrics

See metadata.csv for a list of metrics provided by this integration.

Events

The JBoss/WildFly integration does not include any events.

Service Checks

jboss.can_connect:
Returns CRITICAL if the Agent is unable to connect to and collect metrics from the monitored JBoss/WildFly instance, otherwise returns OK.

Troubleshooting

Need help? Contact Datadog support.