Skip to main content
All Doppler integration capabilities

​
About

Stream your Doppler Activity Logs into Sazabi to see who read or changed secrets, configs, environments, integrations, and workplace access. Doppler’s Generic HTTPS logging service sends each new Activity Log entry to Sazabi as a JSON POST. There is no agent or sidecar to deploy, and Sazabi never calls the Doppler API.

​
What Sazabi records

Each Doppler Activity Log entry becomes one Sazabi record. The record body is the event type (for example enclave.project.config.secrets.update), the timestamp is Doppler’s createdAt, and the full Doppler event is kept. These attributes are extracted for filtering: Activity Log entries name changed secrets but never include their values.

​
Prerequisites

  • A Doppler workplace on the Enterprise plan. Logging services are an Enterprise feature.
  • Workplace admin access to Settings > Logging Services in Doppler.
  • Your Sazabi intake URL (shown above).

​
Set up in the dashboard

1

​
Open the Generic HTTPS logging service

In the Doppler dashboard, navigate to Settings > Logging Services and click Connect on Generic HTTPS.
2

​
Set the URL

  • URL: Paste your Sazabi intake URL (shown above)
  • Leave the bearer token and basic auth fields empty. The intake URL already authenticates each request.
3

​
Save and verify

Save the logging service. Doppler forwards every new Activity Log entry from then on; earlier entries are not backfilled.

​
Set up with the CLI

You can also register the Doppler 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 paste it into the URL field of Doppler’s Generic HTTPS logging service. 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

Update a secret in any Doppler config, or change a member’s role, to create an Activity Log entry. Open the Intake page in the Sazabi dashboard and confirm records from the Doppler source appear. Records typically arrive within a few minutes.

​
Troubleshooting

Logging Services is missing — The workplace is not on the Enterprise plan, or your Doppler role is not a workplace admin. No records after saving — Confirm the URL in Doppler exactly matches your Sazabi intake URL, including the https:// scheme. Doppler allows one Generic HTTPS logging service per workplace, so make sure it was not replaced by another destination.

​
Further reading

Intake

See per-source ingestion volume and health in the Intake page.

Doppler Generic HTTPS

Doppler’s documentation for the Generic HTTPS logging service.

Activity Log event schema

Every field Doppler sends with an Activity Log entry.

Log sources

Browse the full log source catalog.