@@ -6,24 +6,24 @@ steps if you want to migrate from this distribution to the upstream
66OpenTelemetry .NET project.
77
88- Set appropriate environment variables or ` web.config ` /` app.config ` values as
9- explained here: [ Send data to the Grafana Cloud OTLP endpoint] [ publish-otlp ]
9+ explained here: [ Send data to the Grafana Cloud OTLP endpoint] [ publish-otlp ]
1010- Install and activate the OpenTelemetry SDK,
11- as covered in the upstream [ Getting Started] [ getting-started ] guide
11+ as covered in the upstream [ Getting Started] [ getting-started ] guide
1212- Setup the OTLP exporter for metrics, logs, and traces - see the
13- [ exporter README] [ exporter-readme ] for details. The exporter will respect the
14- previously set environment variables:
15- - ` OTEL_EXPORTER_OTLP_PROTOCOL `
16- - ` OTEL_EXPORTER_OTLP_ENDPOINT `
17- - ` OTEL_EXPORTER_OTLP_HEADERS `
13+ [ exporter README] [ exporter-readme ] for details. The exporter will respect the
14+ previously set environment variables:
15+ - ` OTEL_EXPORTER_OTLP_PROTOCOL `
16+ - ` OTEL_EXPORTER_OTLP_ENDPOINT `
17+ - ` OTEL_EXPORTER_OTLP_HEADERS `
1818- Install and configure any desired instrumentation packages
1919 [ listed here] ( ./supported-instrumentations.md )
2020- [ Add the OpenTelemetry resource attributes] [ resource-attributes ]
21- via the ` OTEL_RESOURCE_ATTRIBUTES ` environment variable
22- - ` service.name `
23- - ` service.namespace `
24- - ` service.instance.id `
25- - ` service.version `
26- - ` deployment.environment `
21+ via the ` OTEL_RESOURCE_ATTRIBUTES ` environment variable
22+ - ` service.name `
23+ - ` service.namespace `
24+ - ` service.instance.id `
25+ - ` service.version `
26+ - ` deployment.environment `
2727
2828``` shell
2929export OTEL_RESOURCE_ATTRIBUTES=service.instance.id=< pod123> ,deployment.environment=...
0 commit comments