Skip to content

Commit a1ccc9f

Browse files
committed
A little bit of grammar/style
1 parent fd6b3cd commit a1ccc9f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/concepts/otlp/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,14 +9,14 @@ keywords: ["otlp", "otel", "opentelemetry"]
99

1010
Sentry can ingest [OpenTelemetry](https://opentelemetry.io) traces directly via the [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/). If you have existing OpenTelemetry trace instrumentation, you can configure your OpenTelemetry exporter to send traces to Sentry directly.
1111

12-
The easiest way to configure an OpenTelemetry Exporter is with environment variables. You'll need to configure the trace endpoint URL, as well as the authentication headers.
12+
The easiest way to configure an OpenTelemetry exporter is with environment variables. You'll need to configure the trace endpoint URL, as well as the authentication headers. Set these variables on the server where your application is running.
1313

1414
```bash {filename: .env}
1515
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="___OTLP_TRACES_URL___""
1616
export OTEL_EXPORTER_OTLP_TRACES_HEADERS="x-sentry-auth=sentry sentry_key=___PUBLIC_KEY___"
1717
```
1818
19-
If you don't want to use environment variables, you can configure the OpenTelemetry Exporter directly in your application code.
19+
Alternatively, you can configure the OpenTelemetry Exporter directly in your application code.
2020
2121
```typescript {filename: app.ts}
2222
import { NodeSDK } from "@opentelemetry/sdk-node";

0 commit comments

Comments
 (0)