![]() |
VOOZH | about |
Logs
Use Observability Pipelines’ Datadog Logs destination to send logs to Datadog Log Management. You can also use AWS PrivateLink to send logs from Observability Pipelines to Datadog.
Configure the Datadog Logs destination when you set up a pipeline. You can set up a pipeline in the UI, using the API, or with Terraform. The steps in this section are configured in the UI.
After you select the Datadog Logs destination in the pipeline UI, you can configure these optional settings.
You can route logs to multiple Datadog organizations. After routing has been set up, you can view metrics for the component or specific organizations to which you are routing logs.
Note: You can route up to 100 Datadog organizations.
Click Route to Multiple Organizations to set up routing to multiple Datadog organizations.
Note: If you don’t set up routing to multiple Datadog organizations, logs are routed to the default Datadog organization, which is the organization that is tied to the API key when you install the Worker.
Data dropped (intentional) shows the number logs that do not match the filters and are dropped.Toggle the switch to enable Buffering Options. Enable a configurable buffer on your destination to ensure intermittent latency or an outage at the destination doesn’t create immediate backpressure, and allow events to continue to be ingested from your source. Disk buffers can also increase pipeline durability by writing data to disk, ensuring buffered data persists through a Worker restart. See Destination buffers for more information.
Note: If you entered identifiers for yours secrets and then choose to use environment variables, the environment variable is the identifier entered prepended with DD_OP. For example, if you entered PASSWORD_1 for the a password identifier, the environment variable for the password is DD_OP_PASSWORD_1.
There are no secret identifiers for this destination.
No environment variables required.
You can view metrics at the component level or organization level.
To view metrics for the overall Datadog Logs destination:
Note: The Data dropped (intentional) metric shows logs that didn’t match any of the organizations’ filters.
To view metrics for a specific Datadog organization:
Alternatively, you can click on Review Configured Organizations in the Datadog Logs destination, and click the graph icon in the Metrics column for the organization you are interested in.
A batch of events is flushed when one of these parameters is met. See event batching for more information.
| Maximum Events | Maximum Size (MB) | Timeout (seconds) |
|---|---|---|
| 1,000 | 4.25 | 5 |
To send logs from Observability Pipelines to Datadog using AWS PrivateLink, see Connect to Datadog over AWS PrivateLink for setup instructions. The two endpoints you need to set up are:
Note: The obpipeline-intake.datadoghq.com endpoint is used for Live Capture and is not available as a PrivateLink endpoint.
To send logs from Observability Pipelines to Datadog using Azure Private Link, see Connect to Datadog over Azure Private Link for setup instructions. The two endpoints you need to set up are:
http-intake.logs.us3.datadoghq.comconfig.us3.datadoghq.comNote: The obpipeline-intake.datadoghq.com endpoint is used for Live Capture and is not available as a Private Link endpoint.
| |