Datadog Agent
Forward logs to Sazabi while keeping Datadog as your primary observability platform
Configure the Datadog Agent to forward logs to Sazabi while keeping Datadog as your primary observability platform.
About this data source
The Datadog Agent supports dual-shipping logs to multiple destinations using additional endpoints. This allows you to send logs to both Datadog and Sazabi simultaneously without changing your existing logging infrastructure.
With this integration, you can:
- Keep Datadog as your primary observability platform
- Leverage Sazabi's AI-powered log analysis alongside Datadog
- Forward all agent-collected logs without application changes
- Maintain a single logging configuration for both destinations
Prerequisites
Before you begin, make sure you have:
- Datadog Agent installed (v6.0 or later)
- A Sazabi public API key (project-scoped)
Get your API key
Create a public key
Click Create API key and select Public as the key type. Public keys are safe to use in client-side code and are scoped to a single project.
Copy the key and store it securely. You will not be able to see it again.
Configuration
Edit your datadog.yaml configuration file to enable logs and add Sazabi
as an additional endpoint:
logs_enabled: true
additional_endpoints:
- api_key: "YOUR_SAZABI_PUBLIC_KEY"
host: "intake.sazabi.com"
port: 443
use_ssl: trueReplace YOUR_SAZABI_PUBLIC_KEY with the key you created in the previous
step.
After updating the configuration, restart the Datadog Agent:
sudo systemctl restart datadog-agentConfigure the Datadog Agent using environment variables:
DD_LOGS_ENABLED=true
DD_ADDITIONAL_ENDPOINTS='[{"api_key": "YOUR_SAZABI_PUBLIC_KEY", "host": "intake.sazabi.com", "port": 443, "use_ssl": true}]'Replace YOUR_SAZABI_PUBLIC_KEY with the key you created in the previous
step.
This is useful for containerized deployments where you configure the agent through environment variables.
The additional endpoints configuration dual-ships all logs to both Datadog and Sazabi. Your logs will continue flowing to Datadog unchanged while also being forwarded to Sazabi for AI-powered analysis.
How it works
When you configure an additional endpoint, the Datadog Agent sends a copy of every log entry to both destinations:
- Logs are collected from your applications and systems as usual
- The agent forwards logs to Datadog's intake endpoint (primary)
- The agent simultaneously forwards the same logs to Sazabi (additional endpoint)
- Both platforms receive and process the logs independently
This approach requires no changes to your application logging code or existing Datadog integrations.
Verifying logs are flowing
Once you have configured the agent, verify that logs are flowing to Sazabi:
Check agent status
Run the agent status command to verify the additional endpoint is configured:
datadog-agent statusLook for the logs section showing your additional endpoint is active.
Ask the assistant
Open a thread in Sazabi and ask "Show me recent logs" or "What logs have come in from the Datadog Agent in the last 5 minutes?"
Troubleshooting
Logs not appearing in Sazabi
- Run
datadog-agent statusto verify the additional endpoint is configured - Check that
logs_enabledis set totrue - Verify your Sazabi API key is correct and has the Public scope
- Ensure the agent has been restarted after configuration changes
Connection refused errors
- Verify your network allows outbound HTTPS connections to
intake.sazabi.com - Check firewall rules for port 443
- If behind a proxy, configure the agent's proxy settings
Duplicate logs appearing
- Ensure you have only one
additional_endpointsconfiguration - Check that you are not configuring the endpoint in both
datadog.yamland environment variables - Verify the agent is not running multiple instances
401 Unauthorized errors
- Your API key may be invalid or expired
- Create a new public API key in Settings -> API Keys
- Verify the key is for the correct project