What happens
ENABLE_SENSITIVE_DATA is read as a compatibility alias for
OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT, but the values accepted as true are true,
1 and yes. Python accepts true, 1, yes and on.
A deployment that sets ENABLE_SENSITIVE_DATA=on therefore captures message content in a Python
process and silently does not in a TypeScript one — which is the case the alias exists to cover.
The failure is quiet in the direction that costs debugging time: telemetry simply arrives without
the message content the operator asked for.
Expected
The same truthy set as Python, for both spellings of the variable.
Acceptance criteria
ENABLE_SENSITIVE_DATA=on enables capture.- Unset and unrecognized values leave it off, and an explicit setting through
configureObservability still wins over the environment.
What happens
ENABLE_SENSITIVE_DATAis read as a compatibility alias forOTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT, but the values accepted as true aretrue,1andyes. Python acceptstrue,1,yesandon.A deployment that sets
ENABLE_SENSITIVE_DATA=ontherefore captures message content in a Pythonprocess and silently does not in a TypeScript one — which is the case the alias exists to cover.
The failure is quiet in the direction that costs debugging time: telemetry simply arrives without
the message content the operator asked for.
Expected
The same truthy set as Python, for both spellings of the variable.
Acceptance criteria
ENABLE_SENSITIVE_DATA=onenables capture.configureObservabilitystill wins over the environment.