Setting the file. One moment.
Subchapter 152.5
references/search.mdMarkdown2 KBView on GitHub
The logs search accepts multiple tokens and quoted phrases to help you find the exact log lines you need.
! to exclude logs that contain that token. You can use multiple negative tokens to exclude several different termsType: bug frontend
Result: Shows logs that contain both the words bug and frontend anywhere in the line.
Type: error !timeout
Result: Shows logs that contain error but excludes any log that also contains timeout.
Type: api "server error" !403 !timeout
Result: Must contain api and the exact phrase server error, and must not contain 403 or timeout.
Type: "failed to connect"
Result: Matches logs that include the substring failed to connect exactly as written.
| Query | What it finds |
|---|---|
| login timeout | Logs that contain both login and timeout |
| login !debug | Logs that contain login and excludes logs that contain debug |
| “database error” | Logs with the exact phrase database error |
| “payment failed” !trace !debug | Logs that contain the exact phrase payment failed and excludes any that contain trace or debug |
! by itself is ignored — use ! followed by text to exclude that text!tokens (e.g., !debug !trace) to exclude logs that contain any of those tokensSearch works best when your logs are consistent and structured. Adding key-value context like user_id, endpoint, and status_code to every log line makes filtering faster and more precise. See our logging best practices guide (opens in a new tab) for patterns that make logs easier to search and query.
Ask a question
HelpfulCould be better