Skip to main content
All Devin integration capabilities

​
About

Ship Devin CLI session telemetry to Sazabi using Devin CLI’s built-in OTLP exporter. Once configured, every session emits structured events covering session start and end, user prompts, model API requests with token counts, and tool calls — no code changes to your projects required. The same configuration applies to the Devin CLI bundled with Devin Desktop.
Devin CLI exports prompt and response text and tool arguments by default, including any sensitive content typed or pasted during sessions. Add "disable_user_prompt_logging": true and "disable_tool_logging": true to the otel block to keep that content out of your logs.

​
Prerequisites

  • Devin CLI installed and signed in (devin auth status)
  • Your Sazabi intake URL, shown above — open the log source and copy the Intake URL from its setup screen (the public key is embedded in the URL)

​
Set up in the dashboard

1

​
Add an otel block to the Devin CLI config

Open or create ~/.config/devin/config.json (on Windows, %APPDATA%\devin\config.json) and add an otel block, keeping the file’s other top-level keys:
~/.config/devin/config.json
Replace <your intake URL> with the intake URL shown above, keeping the /v1/logs path. If an otel block already exists, set logs_endpoint inside it instead of adding a second one.Use logs_endpoint, not endpoint — endpoint also sends metrics, which this setup leaves off to keep volume down.
2

​
Check the configuration

Run devin doctor. The otel logs export row shows your intake URL with /v1/logs, and otel metrics export shows off.
3

​
Restart Devin CLI

Devin CLI loads its config at startup. Quit any running Devin CLI session and start a new one for the otel block to take effect.

​
Set up with the CLI

You can also register the Devin CLI log source with the Sazabi CLI (installed and authenticated — see CLI reference). Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):
The command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run sazabi log-sources get <log-source-id> at any time to reprint the endpoint, or sazabi log-sources list to see every log source in the project.

​
Verify

Start a Devin CLI session and run a prompt. Open the Intake page in the Sazabi dashboard and confirm events from the Devin CLI source appear within a minute or two.

​
Troubleshooting

No events after restarting — Run devin doctor. If it reports otel export off, confirm ~/.config/devin/config.json is valid JSON and the otel block sits at the top level. Devin CLI exports only while signed in; run devin auth status. Events go somewhere else — An OTEL_EXPORTER_OTLP_ENDPOINT environment variable overrides the configured endpoint. Unset it, or point it at your intake URL. CFG006 warning — Devin CLI ignores some OTEL_EXPORTER_OTLP_* variables, including every OTEL_EXPORTER_OTLP_TRACES_* variable. Unset the variable devin doctor names. Team settings override the local config — On Devin Enterprise, team settings can enforce or disable telemetry export and content capture. devin doctor reports the team settings it loaded. Metric data points show up as log records — endpoint or metrics_endpoint is set, so Devin CLI is also exporting metrics. Sazabi is not a metrics store and keeps each data point as a log record. Switch to logs_endpoint and leave metrics_endpoint unset.

​
Further reading

Devin CLI configuration

Devin CLI config file locations and settings.

Intake

See per-source ingestion volume and health.

Log sources

Browse the full log source catalog.