Skip to content

Add note about reserved tags in Multi Alert #39380

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
khy1226 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add note about reserved tags in Multi Alert #39380

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions hugo/content/en/monitors/notify/variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,6 +267,8 @@

**Note**: When you use the `group_by` field in aggregation, additional tags and alerts from the monitor may be inherited automatically. This means that any alerts or configurations set on the monitored endpoint could be applied to each group resulting from the aggregation.

**Note**: [Reserved tag keys](https://docs.datadoghq.com/getting_started/tagging/) will exist independently regardless of the group-by dimension

Check warning on line 270 in hugo/content/en/monitors/notify/variables.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense 

Avoid temporal words like 'will'.

Comment on lines 268 to +271

@OliviaShoup OliviaShoup Aug 21, 2026

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.

putting these two notes together to make it a bit easier to scan. also changing the link format to our style guide convention. i can't comment on that part of the file, but this needs to go at the very end of the link list on line 772:

Suggested change
**Note**: When you use the `group_by` field in aggregation, additional tags and alerts from the monitor may be inherited automatically. This means that any alerts or configurations set on the monitored endpoint could be applied to each group resulting from the aggregation.
**Note**: [Reserved tag keys](https://docs.datadoghq.com/getting_started/tagging/) will exist independently regardless of the group-by dimension
**Note**: When you use the `group_by` field in aggregation, additional tags and alerts from the monitor may be inherited automatically, so any alerts or configurations set on the monitored endpoint could apply to each group resulting from the aggregation. [Reserved tag keys][21] are exceptions. They're available in every alert regardless of the selected group-by dimension.

{{< tabs >}}
{{% tab "Group by tag" %}}

Expand Down
Loading