This repository was archived by the owner on Oct 23, 2026. It is now read-only.
Repository navigation
fix(logs): Correct severity query examples - #1328
Merged
Merged
Conversation
Contributor
|
jamieQ
marked this pull request as ready for review
July 31, 2026 21:32
5 tasks
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
level:errorexamples withseverity:errorfor Logs queriesWhy
The Logs API uses
severityfor the canonical log severity.levelis treated as an independent custom attribute, not an alias, so the existing examples commonly return no matches.