To find out if this integration is available in your organization, see your Datadog Integrations page or ask your organization administrator.
To initiate an exception request to enable this integration for your organization, email support@ddog-gov.com.
Pipeline execution with logs and log relevance
Overview
The Buildkite integration is in Preview. Reach out to your Datadog representative to sign up.
Buildkite Job Logs
This integration collects job logs from Buildkite pipelines into Datadog, giving you centralized visibility into your CI/CD build output. By connecting your Buildkite organization to Datadog, you can view, search, and analyze build logs alongside your existing pipeline traces in CI Visibility. This integration requires CI Visibility to be enabled for Buildkite; see # Buildkite Setup for CI Visibility for more info.
Key features:
- Job log collection - Automatically pull logs from Buildkite pipeline jobs into Datadog.
- CI Visibility integration - Correlate job logs with pipeline execution data for faster debugging and root cause analysis.
Setup
This integration pulls job logs for Buildkite.
Prerequisite: CI Visibility must be configured first.
Buildkite log collection depends on Datadog CI Visibility. To set it up, follow the instructions in Buildkite Setup for CI Visibility.
After CI Visibility is enabled, follow these steps to configure log collection:
- Go to Buildkite Personal Settings > API Access Tokens and create a new access token with at least the following access: read and write builds, read build logs, read artifacts, read job env, and read agents.
- Add the API key in the Buildkite integration tile and enable log collection for the desired Buildkite organizations. Make sure your API key will not expire, or set yourself a reminder with the expiry date.
Uninstallation
To uninstall the integration, go to the Buildkite integration tile and disable log collection for all the desired organizations.
Support
Need help? Contact Datadog Support.