Supported OS
This check collects metrics from cert-manager.
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.
The cert_manager check is included in the Datadog Agent package. No additional installation is needed on your server.
Edit the cert_manager.d/conf.yaml file in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your cert_manager performance data. See the sample cert_manager.d/conf.yaml for all available configuration options.
Run the Agent’s status subcommand and look for cert_manager under the Checks section.
| cert_manager.clock_time (gauge) | The clock time given in seconds (from 1970/01/01 UTC) Shown as second |
| cert_manager.certificate.ready_status (gauge) | The ready status of the certificate |
| cert_manager.certificate.expiration_timestamp (gauge) | The date after which the certificate expires. Expressed as a Unix Epoch Time Shown as second |
| cert_manager.http_acme_client.request.count (count) | The number of requests made by the ACME client |
| cert_manager.http_acme_client.request.duration.sum (count) | The sum of the HTTP request latencies in seconds for the ACME client |
| cert_manager.http_acme_client.request.duration.count (count) | The count of the HTTP request latencies in seconds for the ACME client |
| cert_manager.http_acme_client.request.duration.quantile (gauge) | The quantiles of the HTTP request latencies in seconds for the ACME client |
| cert_manager.controller.sync_call.count (count) | The number of sync() calls made by a controller |
The cert_manager integration does not include any events.
cert_manager.openmetrics.health
Returns CRITICAL if the agent fails to connect to the OpenMetrics endpoint, otherwise OK.
Statuses: ok, critical
Need help? Contact Datadog support.
