Conversation
Add regexp flag for log search.
Add `instance` and `regexp` input fields and the `error` output field for the logs query endpoint.
Add a regexp toggle for log search with dedicated placeholder and helper text, display backend query errors in an inline notification, and show a results summary line with line count and time interval. Rework the start/end date-time layout into a responsive flex group and remove the now-unused collapse/expand filters toggle.
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
1 participant
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.
Adds a "Regular expression" toggle to the System Logs search bar. When enabled, the filter is applied with the LogQL
|~operator instead of the substring|=.Backslashes are now escaped along with quotes for both operators, so a filter carrying either no longer produces an unparsable query and a misleading "No log found".
Invalid patterns are rejected client-side, and again server-side with Go regexp (RE2, the engine Loki runs). logcli failures now reach the UI as an error notification: until now a broken query was indistinguishable from an empty result.
Also from the Figma mockup:
Refs NethServer/dev#8032
Design: NethServer/dev#7974
Testing
redis: results unchangedredis|traefikand^2026-05[unclosed: error notification, no empty stateapi-server-logs logs -s 'err(or)?' -r -m dump -l 50