---
title: cert-manager
description: Track all your cert-manager metrics with Datadog
breadcrumbs: Docs > Integrations > cert-manager
---

# cert-manager
Supported OS Integration version6.4.1
## Overview{% #overview %}

This check collects metrics from [cert-manager](https://github.com/jetstack/cert-manager).



**Minimum Agent version:** 7.22.0

## Setup{% #setup %}

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](https://app.datadoghq.com/account/settings/agent/latest) for guidance on applying these instructions.

### Installation{% #installation %}

The cert_manager check is included in the [Datadog Agent](https://app.datadoghq.com/account/settings/agent/latest) package. No additional installation is needed on your server.

### Configuration{% #configuration %}

1. 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](https://github.com/DataDog/integrations-core/blob/master/cert_manager/datadog_checks/cert_manager/data/conf.yaml.example) for all available configuration options.

1. [Restart the Agent](https://docs.datadoghq.com/agent/guide/agent-commands.md#start-stop-and-restart-the-agent).

### Validation{% #validation %}

[Run the Agent's status subcommand](https://docs.datadoghq.com/agent/guide/agent-commands.md#agent-status-and-information) and look for `cert_manager` under the Checks section.

## Data Collected{% #data-collected %}

### Metrics{% #metrics %}

|  |
|  |
| **cert\_manager.certificate.expiration\_timestamp**(gauge)            | The date after which the certificate expires. Expressed as a Unix Epoch Time*Shown as second*      |
| **cert\_manager.certificate.ready\_status**(gauge)                    | The ready status of the certificate                                                                |
| **cert\_manager.certificate.renewal\_timestamp**(gauge)               | The date at which the certificate will be renewed. Expressed as a Unix Epoch Time*Shown as second* |
| **cert\_manager.clock\_time**(gauge)                                  | The clock time given in seconds (from 1970/01/01 UTC)*Shown as second*                             |
| **cert\_manager.controller.sync\_call.count**(count)                  | The number of sync() calls made by a controller                                                    |
| **cert\_manager.http\_acme\_client.request.count**(count)             | The number of requests made by 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.http\_acme\_client.request.duration.sum**(count)      | The sum of the HTTP request latencies in seconds for the ACME client                               |

### Events{% #events %}

The cert_manager integration does not include any events.

### Service Checks{% #service-checks %}

**cert\_manager.openmetrics.health**

Returns `CRITICAL` if the agent fails to connect to the OpenMetrics endpoint, otherwise `OK`.

*Statuses: ok, critical*

## Troubleshooting{% #troubleshooting %}

### Duplicate name tags{% #duplicate-name-tags %}

Each certificate name is exposed within the `name` label in the Prometheus payload and is converted to a tag by the Datadog Agent. If your hosts also use the `name` tag (for instance, automatically collected by the [AWS integration](https://docs.datadoghq.com/integrations/amazon_web_services.md)), metrics coming from this integration will present both values. To avoid duplicate `name` tags, you can use the [`rename_labels`configuration parameter](https://github.com/DataDog/integrations-core/blob/81b91a54328f174c5c1e92cb818640cba1ddfec3/cert_manager/datadog_checks/cert_manager/data/conf.yaml.example#L153-L155) to map the Prometheus label `name` to the Datadog tag `cert_name`. This ensures you have a single value within the tag `cert_name` to identify your certificates :

```yaml
init_config:
instances:
- openmetrics_endpoint: <OPENMETRICS_ENDPOINT>
  rename_labels:
    name: cert_name
```

Need further help? Contact [Datadog support](https://docs.datadoghq.com/help/).