Configuration

The config is flat and has exactly four options.

Option	Type	Default	Meaning
`serviceName`	string	`dsh`	The service name. `OTEL_SERVICE_NAME` wins over this option.
`endpoint`	string	`http://localhost:4318`	The OTLP HTTP base URL. The plugin uses it only when no OTLP endpoint variable is set.
`captureContent`	boolean	`false`	Records the message content, the tool arguments, and the tool result.
`useGlobalProviders`	boolean	`false`	`true` uses the `@opentelemetry/api` globals. The plugin then sets up no SDK.

A standard environment variable wins over the config option.

Variable	Effect
`OTEL_EXPORTER_OTLP_ENDPOINT`	The base URL for both signals. The plugin then passes no URL to the exporters.
`OTEL_EXPORTER_OTLP_TRACES_ENDPOINT`, `OTEL_EXPORTER_OTLP_METRICS_ENDPOINT`	The URL for one signal, used as it is.
`OTEL_EXPORTER_OTLP_HEADERS`, `_TIMEOUT`, `_COMPRESSION`, `_CERTIFICATE`	Read by the exporters.
`OTEL_SERVICE_NAME`, `OTEL_RESOURCE_ATTRIBUTES`	Read by the plugin through the environment resource detector.
`OTEL_SDK_DISABLED=true`	The plugin does nothing.
`OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT=true`	Turns the content capture on.
`OTEL_BSP_*`, `OTEL_TRACES_SAMPLER`	Read by `@opentelemetry/sdk-trace-base`.

The content capture is off by default. The message content can hold user data and personal data.

dsh-otel