What happened?
Currently, getTelemetryEnabled() unconditionally activates both lightweight baseline telemetry and massive tracing overhead (recording full tool outputs, file reads, and model responses). This violates the principle that baseline telemetry should be cheap and lightweight. Decoupling the heavy OpenTelemetry "traces" from standard telemetry allows users and enterprise environments to capture basic usage metrics without bearing the massive cost and potential privacy implications of detailed traces. Tracing must be an explicit opt-in for deep debugging only.
What did you expect to happen?
As outlined in the parent issue #25146, we need a new boolean configuration option: telemetry.traces in settings.json (and its corresponding GEMINI_TELEMETRY_TRACES_ENABLED environment variable). This flag must default to false and strictly require explicit opt-in
Client information
Client Information
Run gemini to enter the interactive CLI, then run the /about command.
> /about
# paste output here
Login information
No response
Anything else we need to know?
No response
What happened?
Currently, getTelemetryEnabled() unconditionally activates both lightweight baseline telemetry and massive tracing overhead (recording full tool outputs, file reads, and model responses). This violates the principle that baseline telemetry should be cheap and lightweight. Decoupling the heavy OpenTelemetry "traces" from standard telemetry allows users and enterprise environments to capture basic usage metrics without bearing the massive cost and potential privacy implications of detailed traces. Tracing must be an explicit opt-in for deep debugging only.
What did you expect to happen?
As outlined in the parent issue #25146, we need a new boolean configuration option: telemetry.traces in settings.json (and its corresponding GEMINI_TELEMETRY_TRACES_ENABLED environment variable). This flag must default to false and strictly require explicit opt-in
Client information
Client Information
Run
geminito enter the interactive CLI, then run the/aboutcommand.Login information
No response
Anything else we need to know?
No response