-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[DOCS-12675] CNM Glossary #33123
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.
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
[DOCS-12675] CNM Glossary #33123
Conversation
Preview links (active after the
|
|
Added DOCS-12826 for editorial review. |
| @@ -0,0 +1,77 @@ | |||
| --- | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should either have either
1/ one glossary page per product CNM, Network Path, NDM
or 2/ a single glossary for all network product, but then, we need to move the glossary at the Network Monitoring level.
What do you think?
I'm learning toward 1/ , but 2/ would work too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes good callout, I thought about that too, I think Network Path should have it's own glossary so I'll move the Network path section there, thank you!
maycmlee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small suggestion and a question. Otherwise, looks great! Approving, but let me know if you would like anything re-reviewed.
content/en/network_monitoring/cloud_network_monitoring/glossary.md
Outdated
Show resolved
Hide resolved
content/en/network_monitoring/cloud_network_monitoring/glossary.md
Outdated
Show resolved
Hide resolved
Co-authored-by: May Lee <[email protected]>
What does this PR do? What is the motivation?
Adds a glossary to the CNM docs
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes