Supported telemetry types
The cert-manager integration supports these telemetry types:Prerequisites
Meet these requirements before configuring the integration:- Expose each controller’s
Prometheus metrics endpoint
at
/metrics. - For controller pods, allow the node Collector to connect to the pods.
- For Services or static targets, allow the cluster Collector to connect to each target.
Configure
The cert-manager integration is enabled by default. You can configure targets either by annotating controller pods in your Kubernetes cluster or by listing static endpoints in your Helm values. To configure the cert-manager integration, follow these steps:-
To collect from cert-manager controller pods in Kubernetes, add a CXDOT integration
annotation to the pod template. The annotation key must end with the container name.
For example, add the following annotation to your cert-manager controller Deployment:
The Collector replaces
${target.host}with the pod IP address and${target.port.http-metrics}with the container port namedhttp-metrics. The Collector also discovers controller pods that carry theapp.kubernetes.io/name: cert-managerandapp.kubernetes.io/component: controllerlabels and listen on port9402. A CXDOT integration annotation takes precedence over the labels for its container. To stop collecting from a container, setcert_manager: {enabled: false}in the annotation. For more information, see autodiscovery. -
Optional: To collect from specific cert-manager endpoints, configure static
targets by listing their
host:portvalues inendpoints. The instance then scrapes only those targets. For example:Each static target resolves tohttp://<host>:<port>/metrics. -
Optional: To combine annotated pods and static targets, configure separate
instances. The bare
cert_managerkey discovers pods, and the named instance scrapes the static targets:
Validate
-
In the
Live Telemetry Analyzer,
add the following label filters:
- Set Label to
__name__and Value tocxdot.integration.target.health. - Set Label to
cxdot.integration.nameand Value tocert_manager.
cxdot.integration.target, and confirm that the metric reports1for each target. - Set Label to
-
In
Metrics Explorer,
run the following query:
Confirm that the query returns a time series for each certificate condition.
Disable the cert-manager integration
Deleting everycert_manager block restores the default unnamed instance. To remove
custom settings and stop collection, retain a disabled configuration:
Configuration reference
Configure one cert-manager integration instance with the following settings. In Helm values, place these settings undercollection.cxdot.integrations.cert_manager. In a Collector
configuration file, place them under cxdot.integrations.cert_manager.
Optional settings
-
enabledType:boolean. Optional. Default:true. Whether to enable this cert-manager integration instance. If true, the Collector runs the instance. If false, the Collector doesn’t run it. -
endpointsType:array of object. Optional. Default:[]. Targets for cert-manager. Specify each target ashost:port. The Collector requestshttp://<host>:<port>/metrics. -
endpoints[].endpointType:string. Required. cert-manager target inhost:portformat. -
collection_intervalType:duration. Optional. Default:60s. How often the Collector collects metrics from each cert-manager target. -
timeoutType:duration. Optional. Default:60s. Maximum time allowed to collect metrics from one cert-manager target. The value must not exceedcollection_interval.