---
title: Use Bean regexes to filter your JMX metrics and supply additional tags
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Integrations > Integration Guides > Use Bean regexes to filter your JMX
  metrics and supply additional tags
---

# Use Bean regexes to filter your JMX metrics and supply additional tags

{% callout %}
# Important note for users on the following Datadog sites: us2.ddog-gov.com

{% alert level="info" %}
To find out if this integration is available in your organization, see your [Datadog Integrations](https://app.datadoghq.com/integrations) page or ask your organization administrator.

To initiate an exception request to enable this integration for your organization, email [support@ddog-gov.com](mailto:support@ddog-gov.com).
{% /alert %}

{% /callout %}

Datadog supports regexes to match JMX Mbean names and domain names to configure your `include` and `exclude` filters. The regexes must conform to [Java's regular expression format](https://docs.oracle.com/javase/6/docs/api/java/util/regex/Pattern.html). Note that these filters were added in version 5.5.0.

Capture groups from the provided regex can be used to supply additional tag values for your metrics.

This article provides one example of how to use the `bean_regex` from the [Java integration](https://docs.datadoghq.com/integrations/java.md), and how to reference such capture groups to set additional tags.

Suppose you have the following Mbean name: `domain.example.com:name=my.metric.name.env.dev.region.eu-central-1.method.GET.status.200`. There is some information you could use as tags once the Agent has collected the metric. For instance, you could export a metric with the following tags:

- `env`: `dev`
- `region`: `eu-central-1`
- `method`: `GET`
- `status`: `200`

Bean regexes can be supplied as a single regex or a list of regex expressions. For the latter, only the first entry of the list that matches will be taken into account. See an example of a configuration file to export your custom metrics with some additional tags:

```yaml
init_config:
  is_jmx: true

instances:
  - host: "<JMX_ENDPOINT>"
    port: "<JMX_PORT>"

    conf:
      - include:
          domain: domain.example.com
          bean_regex:
            - "domain.example.com:name=my.metric.name.*(?:\\.env\\.)([a-z]+)(?:.*\\.region\\.)([a-z-]+[0-9])(?:.*\\.method\\.)([A-Z]+)(?:.*\\.status\\.)([0-9]+)(?:.*)"
          attribute:
            attribute1:
              metric_type: gauge
              alias: "my.jmx.metric"
          tags:
              env: $1
              region: $2
              method: $3
              status_code: $4
              optional: tag
```

Each capture group is stored in a Java Map. The first capture group starts at position `0`. After you have determined which capture group you want to export as a tag, you need to reference them in the `tags` section of your `include` or `exclude` filter, as well as to the number of the group (for example, the position inside the Map).

For the provided example in `bean_regex`, the capture groups are:

- `$0`: `domain.example.com:name=my.metric.name.env.dev.region.eu-central-1.method.GET.status.200`
- `$1`: `dev`
- `$2`: `eu-central-1`
- `$3`: `GET`
- `$4`: `200`

Using the [Metrics Explorer](https://docs.datadoghq.com/metrics/explorer.md), you are able to query your metrics and filter them by the tags you have just created.

## Further Reading{% #further-reading %}

- [Java integration](https://docs.datadoghq.com/integrations/java.md)
- [View JMX data in jConsole and set up your jmx.yaml to collect them](https://docs.datadoghq.com/integrations/faq/view-jmx-data-in-jconsole-and-set-up-your-jmx-yaml-to-collect-them.md)