From 4d2e79af3229b3dec023239c73ec5bae333afe15 Mon Sep 17 00:00:00 2001 From: Israel Blancas Date: Wed, 13 Sep 2023 16:28:47 +0200 Subject: [PATCH] Add documentation for Prometheus Receiver Signed-off-by: Israel Blancas --- .../distr-tracing-otel-config-collector.adoc | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/modules/distr-tracing-otel-config-collector.adoc b/modules/distr-tracing-otel-config-collector.adoc index a76d6eb0dbc4..d32ab64a34b2 100644 --- a/modules/distr-tracing-otel-config-collector.adoc +++ b/modules/distr-tracing-otel-config-collector.adoc @@ -211,6 +211,36 @@ The Jaeger receiver ingests data in Jaeger formats. <4> The Jaeger Thrift Binary endpoint. If omitted, the default `+0.0.0.0:6832+` is used. <5> The TLS server side configuration. See the OTLP receiver configuration section for more details. +[id="prometheus-receiver_{context}"] +==== Prometheus Receiver + +The Prometheus receiver scrapes metrics endpoints.. + +* Support level: link:https://access.redhat.com/support/offerings/techpreview[Technology Preview] +* Supported signals: metrics + +.OpenTelemetry Collector custom resource with an enabled Prometheus receiver +[source,yaml] +---- + config: | + receivers: + prometheus: + config: + scrape_configs: <1> + - job_name: 'my-app' <2> + scrape_interval: 5s <3> + static_configs: + - targets: ['my-app.example.svc.cluster.local:8888'] <4> + service: + pipelines: + metrics: + receivers: [prometheus] +---- +<1> Scrape configurations using Prometheus format. +<2> Prometheus job name. +<3> Interval to scrape the metrics data. +<4> Targets where the metrics are exposed. This example scrapes the metrics from an application called "my-app" in the "example" Project. + [id="zipkin-receiver_{context}"] ==== Zipkin Receiver