Skip to content
Draft
Changes from all commits
Commits
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
7 changes: 4 additions & 3 deletions content/en/getting_started/tagging/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,8 @@

1. Tags must **start with a letter** and after that may contain the characters listed below:

- Alphanumerics
- Letters (all Unicode letters are supported, e.g., a, ó, 気, 녕, ك, and ดี)

Check warning on line 61 in content/en/getting_started/tagging/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.abbreviations_latin

Use 'for example' instead of abbreviations like 'e.g.,'.
Copy link

@tibo-mllr tibo-mllr Mar 18, 2026

Choose a reason for hiding this comment

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

Correct me if I'm wrong, but aren't emojis a subset of Unicode? Does that mean we allow emojis in tags?

- Numbers
- Underscores
- Minuses
- Colons
Expand All @@ -68,7 +69,7 @@

Other special characters are converted to underscores.

2. Tags can be **up to 200 characters** long and support Unicode letters (which includes most character sets, including languages such as Japanese).
2. Tags can be **up to 200 characters** long.
3. Tags are converted to lowercase. Therefore, `CamelCase` tags are not recommended. Authentication (crawler) based integrations convert camel case tags to underscores, for example `TestTag` --> `test_tag`.
4. A tag can be in the format `value` or `<KEY>:<VALUE>`. Commonly used tag keys are `env`, `instance`, and `name`. The key always precedes the first colon of the global tag definition, for example:

Expand Down Expand Up @@ -171,4 +172,4 @@
[22]: /getting_started/tagging/using_tags/#developers
[23]: /account_management/billing/usage_attribution/
[24]: /getting_started/tagging/using_tags/#ci-visibility
[25]: /containers/troubleshooting/log-collection?tab=datadogoperator#missing-host-level-tags-on-new-hosts-or-nodes
[25]: /containers/troubleshooting/log-collection?tab=datadogoperator#missing-host-level-tags-on-new-hosts-or-nodes
Copy link
Author

Choose a reason for hiding this comment

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

mrrr I didn't add this back in (intentionally)

Copy link
Contributor

Choose a reason for hiding this comment

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

just lurking, and thought I'd respond :) This happens regularly...I'm not sure why though...I've seen it my own PR and other's.

Copy link
Author

Choose a reason for hiding this comment

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

thanks May! it's helpful to know you've seen this often. I was just looking closer and realized git is saying, "this content was removed from line 174 and added on line 175." oddly, that pattern is true of all of the content on this page below my change (since my change added a line), but it's only recognized on this (last) line

do you always see this kind of thing with the last line of a file, or does the location vary?

Copy link
Contributor

Choose a reason for hiding this comment

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

Ohh interesting, I never looked into it, but that kind of makes sense. I do always see it with the last line of a file.

Copy link
Author

Choose a reason for hiding this comment

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

ok, noted! thank you!

Loading