[Data Observability] Add Logs Correlation section to Custom Jobs/OpenLineage docs#38360
Merged
Merged
Conversation
heron--
changed the title
heron--
marked this pull request as ready for review
July 21, 2026 17:04
heron--
changed the title
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
aboitreaud
approved these changes
Jul 21, 2026
heron--
force-pushed
the
devin.marsh/openlineage-logs-correlation
branch
from
July 21, 2026 17:05
b1108b7 to
def8434
Compare
Contributor
Preview links (active after the
|
drichards-87
approved these changes
Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Adds a "Correlate logs with job runs" section to the Custom Jobs using OpenLineage page. The section explains how to correlate application logs with an OpenLineage job run in Datadog by emitting logs with the run ID under the
@openlineage.run_idfacet, set to the samerunIdsent in OpenLineage run events. It stays intentionally open-ended about how customers attach the value (structured JSON field nested underopenlineage, or logger context binding), and notes that Datadog automatically flattens nested JSON into dot-notation facets.Merge instructions
Merge readiness:
Additional notes