Extract custom metrics from any OpenMetrics endpoints.
All the metrics retrieved by this integration are considered custom metrics.
Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.
For each instance the following parameters are required:
The URL where your application metrics are exposed by OpenMetrics (must be unique).
The namespace to prepend to all metrics.
A list of metrics to retrieve as custom metrics. Add each metric to the list as metric_name or metric_name: renamed to rename it. The metrics are interpreted as regular expressions. Use .* as a wildcard (metric.*) to fetch all matching metrics. Note: Regular expressions can potentially send a lot of custom metrics.
Note: This is a new default OpenMetrics check example. If you previously implemented this integration, see the legacy example.
Note: This check has a limit of 2000 metrics per instance. The number of returned metrics is indicated when running the Datadog Agent status command. You can specify the metrics you are interested in by editing the configuration. To learn how to customize the metrics to collect, see the Prometheus and OpenMetrics Metrics Collection for more detailed instructions. If you need to monitor more metrics, contact Datadog support.