This product is not supported for your selected
Datadog site. (
).
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、
お気軽にご連絡ください。
Overview
After installing and configuring BYOC (Bring Your Own Cloud) Logs, you need to set up log ingestion to start sending log data from your applications and infrastructure. BYOC Logs supports multiple ingestion methods to accommodate different architectures and requirements.
BYOC Logs accepts logs as JSON objects sent to the /api/v2/logs endpoint. Each request body must be a JSON array of log objects:
[
{"message": "First log entry", "service": "my-app", "level": "info"},
{"message": "Second log entry", "service": "my-app", "level": "error"}
]
NDJSON (newline-delimited JSON) is not supported. If your log source sends one JSON object per line without array wrapping, use Observability Pipelines to reformat the payload before sending to BYOC Logs.
Log ingestion methods
Choose the appropriate ingestion method based on your infrastructure and requirements:
Additional ingestion paths
Datadog Lambda Forwarder
The Datadog Lambda Forwarder can send AWS CloudWatch Logs to BYOC Logs by setting the DD_URL environment variable to your BYOC Logs endpoint:
The forwarder sends logs to https://<DD_URL>:443/api/v2/logs.
Note: API key validation (/api/v1/validate) is sent to Datadog SaaS (controlled by DD_API_URL), not to BYOC Logs. This means you need a valid Datadog API key even when forwarding to BYOC Logs.
OpenTelemetry
BYOC Logs can receive logs from OpenTelemetry collectors through Observability Pipelines. See Send OTel logs to BYOC Logs with Observability Pipelines for setup instructions.
