[DOCS-13570] Remove = from log search special characters list#38059
Merged
Conversation
Verified in-app that = does not require escaping in log search queries, reverting an unverified addition and aligning with the previously tested character list.
Contributor
Preview links (active after the
|
buraizu
approved these changes
Jul 9, 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
2 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?
Fixes DOCS-13570
Removes
=from the list of special characters requiring escaping in log search queries. Testing against Logs Explorer confirmed=does not need escaping — an unquoted, unescaped query for a value containing=returned the same results as the quoted and escaped versions.=was added back to this list in #34990 to align with an internal wiki page, but that page turned out to be a stale copy of this doc's pre-#31006 text. #31006 had already removed=(along with a few other characters) after an engineer manually tested against the live app, so this PR reverts to that previously tested and verified version.The internal wiki page is also being updated to match, so both sources stay in sync.
Merge readiness
For Datadog employees:
<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./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Used Claude Code to investigate the discrepancy (git history, prior PRs) and draft the fix; verification testing in Logs Explorer was done manually.
Additional notes