From a44ceb38fe9644665dc329fe664c89ac0472ec76 Mon Sep 17 00:00:00 2001 From: Paulin Todev Date: Fri, 20 Dec 2024 13:12:59 +0200 Subject: [PATCH] Fix non-working Promtool example. The example was malformed. --- .../reference/components/prometheus/prometheus.remote_write.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/reference/components/prometheus/prometheus.remote_write.md b/docs/sources/reference/components/prometheus/prometheus.remote_write.md index d2614a2e52..a919d750f0 100644 --- a/docs/sources/reference/components/prometheus/prometheus.remote_write.md +++ b/docs/sources/reference/components/prometheus/prometheus.remote_write.md @@ -427,7 +427,7 @@ To troubleshoot, take the following steps in order: You can use [Promtool][promtool] to inspect it and find out which metric series were sent by this {{< param "PRODUCT_NAME" >}} instance since the last WAL truncation event. For example: ``` - ./promtool tsdb dump --match='{__name__=\"otelcol_connector_spanmetrics_duration_seconds_bucket\", http_method=\"GET\", job=\"ExampleJobName\"' /path/to/wal/ + ./promtool tsdb dump --match='{__name__="otelcol_connector_spanmetrics_duration_seconds_bucket", http_method="GET", job="ExampleJobName"}' /path/to/wal/ ``` [clustering]: ../../configure/clustering