DigitalOcean
Add a Datadog log forwarding destination to your DigitalOcean App Platform app and point it at your Sazabi intake URL to forward application logs.
About
You can also connect your DigitalOcean account to Sazabi and have Sazabi configure log forwarding destinations automatically. See DigitalOcean (connect your account) for that path.
This page covers the manual endpoint configuration: add a log forwarding destination to each App Platform app yourself. Use this approach when you want direct control over which apps forward to Sazabi.
Log destinations are per-app in DigitalOcean. Repeat the setup for each App Platform app you want to forward. Droplets, Functions, Spaces, Managed Databases, and Managed Kubernetes are not covered by this source.
Prerequisites
- A DigitalOcean App Platform app (services, workers, and jobs are all supported)
- Your Sazabi intake URL — open the log source at Settings > Log streams and copy the Intake URL from its setup screen (the public key is embedded in the URL)
Set up in the dashboard
Open log forwarding for the app
In the DigitalOcean dashboard, open the App Platform app you want to forward. Navigate to Settings > Log Forwarding and click Add Destination.
Configure the Datadog destination
DigitalOcean App Platform uses a Datadog-compatible log destination format for third-party forwarding. Set:
- Destination type: Datadog
- Endpoint (API URL): your Sazabi intake URL (shown above) — the public key embedded in its hostname is what authenticates the log stream
- API key: App Platform requires this field, but it is not used to authenticate the Sazabi stream. Paste the public key embedded in your intake URL (advanced users can copy it from Settings > Public keys).
Save and redeploy
Save the destination configuration. Redeploy the app (or wait for the next deployment) for log forwarding to take effect.
Set up with the CLI
You can also register the DigitalOcean 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):
sazabi log-sources create digital_ocean --mode connectionlessThe 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
Trigger some activity in the app — make a request to a service, or run a job. Open the Intake page in the Sazabi dashboard and confirm records from the DigitalOcean source appear within a minute or two.
Troubleshooting
No records after redeploying — Confirm the Endpoint (API URL) field holds your full Sazabi intake URL (the embedded public key is what authenticates the stream), and that the log stream and source are active in Settings > Log streams. The API key field is a DigitalOcean form requirement and does not authenticate the Sazabi stream; make sure it is not a DigitalOcean token.
Destination not available — Log forwarding is only available for App Platform apps. Droplets, Functions, Spaces, Managed Databases, and Managed Kubernetes clusters are not supported by this source.
Only one app forwarding — Log destinations are per-app. Confirm you added a destination to each app you want to forward separately.