Skip to content

Commit 589b0f8

Browse files
Wineshugatiffany76
andauthored
Apply suggestions from code review on style guide
Co-authored-by: Tiffany Hrabusa <30397949+tiffany76@users.noreply.github.com>
1 parent 495239f commit 589b0f8

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

content/en/docs/languages/_includes/exporters/prometheus-setup.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,15 @@ and use the [OTLP exporter](#otlp) (best practice),
77
and [push Prometheus to the metrics endpoint directly](#push-metrics-directly) (for development or testing purposes),
88
- or you can use the Prometheus exporter, a `MetricReader` that starts an HTTP server that collects metrics and serialize to Prometheus text format on request.
99

10-
### Backend Setup {#prometheus-setup}
10+
### Backend setup {#prometheus-setup}
1111

12-
- For [OTLP Exporter](#otlp-dependencies) or [Prometheus exporter](#prometheus-dependencies):
12+
For [OTLP Exporter](#otlp-dependencies) or [Prometheus exporter](#prometheus-dependencies):
1313

1414
To run a Prometheus server backend and begin scraping metrics, see the [Prometheus getting started guide](https://prometheus.io/docs/prometheus/latest/getting_started/). To enable the OTLP Receiver, see the [Prometheus guide for enabling the OTLP Receiver](https://prometheus.io/docs/guides/opentelemetry/#enable-the-otlp-receiver).
1515

16-
- For pushing to a metrics endpoint directly:
16+
For pushing to a metrics endpoint directly:
1717

18-
Follow this [guide for prometheus.yml configuration in this Prometheus guide](https://prometheus.io/docs/guides/opentelemetry/#configuring-prometheus).
18+
Follow the [example prometheus.yml configuration in this Prometheus guide](https://prometheus.io/docs/guides/opentelemetry/#configuring-prometheus).
1919

2020
Once you have Prometheus set up, you can set up the OTLP Exporter, Prometheus exporter, or push to a metrics endpoint directly.
2121

@@ -61,4 +61,4 @@ export OTEL_RESOURCE_ATTRIBUTES="service.instance.id=$(uuidgen)"
6161
The above assumes that the `uuidgen` command is available on your system. Make sure that `service.instance.id` is unique for each instance, and that a new `service.instance.id` is generated whenever a resource attribute changes. The [recommended way](https://github.com/open-telemetry/semantic-conventions/tree/main/docs/resource) is to generate a new UUID on each startup of an instance.
6262

6363
#### Step 2: Configuring Telemetry
64-
Update your OpenTelemetry Configuration to use the same `exporter` and `reader` from the [OTLP](#otlp-dependencies) setup. If the environment variables are set up and loaded correctly, the OpenTelemetry SDK will read them automatically.
64+
Update your OpenTelemetry Configuration to use the same `exporter` and `reader` from the [OTLP](#otlp-dependencies) setup. If the environment variables are set up and loaded correctly, the OpenTelemetry SDK reads them automatically.

0 commit comments

Comments
 (0)