From 82307d9b3219bfda13f3d46fd6df9be390987127 Mon Sep 17 00:00:00 2001 From: Phil Freeman Date: Fri, 16 Feb 2024 11:49:03 -0800 Subject: [PATCH] Clarify use of OTEL_EXPORTER_OTLP_ENDPOINT --- rfcs/0000-deployment.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/rfcs/0000-deployment.md b/rfcs/0000-deployment.md index f1f7594b..361a3b8c 100644 --- a/rfcs/0000-deployment.md +++ b/rfcs/0000-deployment.md @@ -32,7 +32,8 @@ _This RFC does not specify the following planned changes:_ - `HASURA_*` - `OTEL_EXPORTER_*` - Connectors can use environment variables as part of their configuration. Configuration that varies between different environments or regions (like connection strings) should be configurable via environment variables. -- The connector should send any relevant trace spans in the OTLP format to the OTEL collector hosted at the URL provided by the `OTEL_EXPORTER_OTLP_ENDPOINT` environment variable. +- The connector should send any relevant trace spans in the OTLP format to the OTEL collector hosted at the URL provided by the `OTEL_EXPORTER_OTLP_ENDPOINT` environment variable. + - Note: `OTEL_EXPORTER_OTLP_ENDPOINT` indicates the _root URL_ of the collector, and not the `/v1/traces` endpoint. - Spans should indicate the service name provided by the `OTEL_SERVICE_NAME` environment variable. - If the `HASURA_SERVICE_TOKEN_SECRET` environment variable is specified and non-empty, then the connector should implement bearer-token HTTP authorization using the provided static secret token. - Information log messages should be logged in plain text to standard output.