What you can stream and why
GitHub Enterprise audit logs capture actions taken by users and administrators across organizations and repositories (authentication events, repository changes, security configuration, token authorization, etc.). Streaming these events into your existing observability stack lets you:- Centralize monitoring and retention
- Build alerts and dashboards for suspicious activity
- Correlate GitHub activity with other telemetry

Setup overview (Datadog example)
This demo uses Datadog as the log destination. High-level steps:- In Datadog: create an API key for GitHub logs and note your Datadog endpoint/region.
- In GitHub Enterprise: navigate to Enterprise settings → Audit log → Log streaming → Configure stream → choose Datadog, paste the API key, and set the Datadog site/region.
- Validate the connection and Save. GitHub will validate the token and endpoint during setup.
- Wait for events to flow (initial propagation usually takes minutes); verify in Datadog Logs Explorer.
- In Datadog: Integrations → APIs (API Keys) → New API key
- Name the key (e.g., “GitHub Logs”), copy the key, and paste into GitHub’s Datadog configuration.

Keep API keys and tokens private. Treat Datadog API keys like secrets: rotate them periodically and avoid embedding them in public or shared code repositories.



After saving a new stream, expect a short propagation delay: typically 10–15 minutes for the first events to appear in your destination (Datadog in this demo). Delays vary with event volume and service propagation.
Verifying events in Datadog
Open Datadog Logs Explorer. If you recently enabled streaming, you may initially see no results until the first events arrive.
- The API key is correct and active.
- The Datadog
site/region matches the endpoint you specified (for example, useap1.datadoghq.comfor AP1). - The GitHub stream shows a successful validation in the UI.
- Time range filters in Datadog are set to include the period when you generated events.
Generating test audit events quickly
To surface events for a demo or validation, perform non-destructive configuration changes in the enterprise:- Toggle organization- or repository-level security settings (for example, Advanced Security options).
- Create a test repository, change visibility, and perform repository actions (create branches, update settings, etc.).
- Trigger security scans (secret scanning, Dependabot alerts) if enabled.
- Created
TestReport2 / test-repo-2 - Changed repository visibility (internal → public)
- Toggled Advanced Security settings



Example of a streamed event (Datadog)
When the stream is active, GitHub forwards events to Datadog as structured logs. A typical event includes actor information, action, repository, organization, timestamps, and user-agent metadata. Example stream data:
Troubleshooting checklist
- Confirm stream status in GitHub Enterprise UI. Look for validation success when saving.
- Verify Datadog API key and platform
site/region (e.g.,datadoghq.com,datadoghq.eu,ap1.datadoghq.com). - Ensure time range filters and saved views in Datadog include the test timeframe.
- For exports, check export job status in GitHub (exports may take longer depending on volume).
- Consult GitHub Docs and the provider’s integration docs for specifics.
Links and references
- Streaming the audit log for your enterprise — GitHub Docs
- Datadog API keys documentation
- Provider docs: consult Datadog, Splunk, AWS, GCP, and Azure integration pages for endpoint and token generation steps.