Skip to content

Clarify reserved service attribute behavior - #39720

Open
wjiang720 wants to merge 3 commits into
masterfrom
codex/clarify-event-service-tag
Open

Clarify reserved service attribute behavior#39720
wjiang720 wants to merge 3 commits into
masterfrom
codex/clarify-event-service-tag

Conversation

@wjiang720

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Clarifies how the reserved service attribute behaves when an event contains multiple service tags. Recommends sending one service tag per event, explains how to represent additional dimensions, and distinguishes reserved-attribute searches from raw-tag searches.

Merge readiness

  • Ready for merge

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
  • 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

AI assistance was used to identify the documentation gap and draft the clarification.

Additional notes

@wjiang720
wjiang720 requested a review from a team as a code owner September 3, 2026 18:51
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@joepeeples joepeeples left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with a small non-blocking formatting suggestion, thanks!

- V1 selects the first `service` tag it processes. Because tags are not sorted, the result is not deterministic.
- V2 sorts the tags alphabetically and selects the first `service` tag.

For example, consider an event with `env:prod`, `service:payments`, `team:store`, and `service:checkout`. V1 can assign either service value. V2 assigns `checkout`, because `service:checkout` comes before `service:payments` alphabetically.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For example, consider an event with `env:prod`, `service:payments`, `team:store`, and `service:checkout`. V1 can assign either service value. V2 assigns `checkout`, because `service:checkout` comes before `service:payments` alphabetically.
For example, consider an event with `env:prod`, `service:payments`, `team:store`, and `service:checkout`. V1 can assign either `service` value. V2 assigns `checkout`, because `service:checkout` comes before `service:payments` alphabetically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants