The OpenTelemetry Collector, when configured with a Prometheus receiver, provides an integration with ExternalDNS to scrape Prometheus metrics. The Collector uses the Prometheus receiver to fetch metrics from the ExternalDNS endpoint. From there, the metrics are processed and exported to Cloud Observability.
To complete the integration, perform the following steps:
ExternalDNS exposes metrics using a Prometheus HTTP endpoint by default. See the ExternalDNS example for an integration inside a Kubernetes cluster.
In the Collector configuration file, specify ExternalDNS Prometheus endpoint as a scrape target.
1 2 3 4 5 6 7 receivers: prometheus: config: scrape_configs: - job_name: otel-external-dns static_configs: - targets: [external-dns:7979]
The OpenTelemetry repository readme provides additional details about Prometheus receiver configuration.
Complete information about the Prometheus scrape configuration can be found in the Prometheus documentation.
After the ExternalDNS receiver is configured, enable it by adding it to one or more pipelines as described in the Collector configuration documentation.
You can validate that metrics are reporting to Cloud Observability on the Metrics details page in Project settings.
In Cloud Observability, click Project settings > Metric details.
Search for ExternalDNS metric names.
See the ExternalDNS documentation for a complete list of emitted metrics.
If needed, select the metric to edit the description and how the units are displayed in Cloud Observability.
Use the Cloud Observability Terraform Provider to create a dashboard for the metrics.
Updated Dec 1, 2022