CLIENT_KEY_CHAIN renamed to CLIENT_CERTIFICATE

open-telemetry · Feb 22, 2022 · 796312f · 796312f
1 parent 458acbb
commit 796312f
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/specification/protocol/exporter.md b/specification/protocol/exporter.md
@@ -28,9 +28,9 @@ The following configuration options MUST be available to configure the OTLP expo
  - Default: n/a
  - Env vars: `OTEL_EXPORTER_OTLP_CLIENT_KEY` `OTEL_EXPORTER_OTLP_TRACES_CLIENT_KEY` `OTEL_EXPORTER_OTLP_METRICS_CLIENT_KEY` `OTEL_EXPORTER_OTLP_LOGS_CLIENT_KEY`
 
-- **Client key chain file**: Chain trust for clients private key to use in MTLS communication in PEM format.
+- **Client certificate file**: Client certificate/chain trust for clients private key to use in mTLS communication in PEM format.
  - Default: n/a
- - Env vars: `OTEL_EXPORTER_OTLP_CLIENT_KEY_CHAIN` `OTEL_EXPORTER_OTLP_TRACES_CLIENT_KEY_CHAIN` `OTEL_EXPORTER_OTLP_CLIENT_KEY_CHAIN` `OTEL_EXPORTER_OTLP_LOGS_CLIENT_KEY_CHAIN`
+ - Env vars: `OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE` `OTEL_EXPORTER_OTLP_TRACES_CLIENT_CERTIFICATE` `OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE` `OTEL_EXPORTER_OTLP_LOGS_CLIENT_CERTIFICATE`
 
 - **Headers**: Key-value pairs to be used as headers associated with gRPC or HTTP requests. See [Specifying headers](./exporter.md#specifying-headers-via-environment-variables) for more details.
  - Default: n/a