[DOCS-14326] Update path notation content and add shortcode#36554
Open
[DOCS-14326] Update path notation content and add shortcode#36554
Conversation
Contributor
git-thuerk-done
approved these changes
May 8, 2026
clementd-dd
reviewed
May 11, 2026
| @@ -0,0 +1 @@ | |||
| To specify a nested field with a literal `.` in the attribute key, wrap the key in escaped quotes in the search query. For example, the search query `"service.status":disabled` matches the event `{"service.status": "disabled"}`. | |||
There was a problem hiding this comment.
nit: could this be merged with layouts/shortcodes/observability_pipelines/path_notation.en.md? are those ever displayed separately?
Contributor
Author
There was a problem hiding this comment.
Hey @clementd-dd! I originally had this dot content in layouts/shortcodes/observability_pipelines/path_notation.en.md so there was only one shortcode. But then I realized the wording doesn't quite work for the log search syntax page, so I broke it out into a separate shortcode.
are those ever displayed separately?
If I'm understanding your question correctly, the answer is that it's not possible to split up the content within a shortcode, unfortunately.
clementd-dd
approved these changes
May 11, 2026
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
3 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?
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.
AI assistance
Additional notes