Add attribute precedence table for log pipelines/processors#38026
Open
10kaoru12 wants to merge 4 commits into
Open
Add attribute precedence table for log pipelines/processors#3802610kaoru12 wants to merge 4 commits into
10kaoru12 wants to merge 4 commits into
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Preview links (active after the
|
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
Thanks for the update @10kaoru12, I moved the section down the page so that it follows the processor information(#38042). Let me know if you have any questions |
…38042) - Relocate attribute precedence section after processor configuration steps for better logical flow - Clarify log date remapper exception upfront in "First write wins" description - Update link reference to use consistent documentation format [3] Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Author
|
@estherk15 |
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
2 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 an Attribute precedence section to the Log Pipelines page that explains, in one place, what happens when the same attribute is set by more than one processor across matching pipelines.
Today this behavior is only documented piecemeal on individual processor pages (for example, the "only the first one is considered" note on the log status remapper, and the "last one is taken into account" note on the log date remapper), and several processors document nothing at all. Customers configuring multiple pipelines/processors have no single reference for which write wins.
The new section groups all processors into three behaviors:
override_on_conflict(Remapper, Array processor; defaultfalse= do not override)Wording is reused verbatim from the existing processor pages to stay consistent.
Merge readiness
For Datadog employees:
<name>/<description>convention.AI assistance
Drafted with Claude Code. Wording was reused verbatim from existing processor pages (log_status_remapper, service_remapper, log_message_remapper, log_date_remapper, remapper). The precedence behavior was independently verified against the logs-backend source before writing.
Additional notes
English (
content/en) only, per the contributing guidelines (translated files are managed by the translation service). Opened as a draft to review the preview build and Vale results before marking ready.