Allow status code 0 to be added in FilterSettingsPage #133
Conversation
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
Author
|
It might also be a good idea to exclude log entries with status code 0 from the response time calculation. This is because a long lasting web socket connection is not an indication of poor performance. A long duration is to be expected. I can create a pull request to fix this if you agree. |
Owner
|
please-commit to dev-dashboard branch. |
Author
|
Closing this PR in favor of a new PR with a clean history. |
This was referenced Nov 30, 2025
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.
Status code filtering does not currently allow filtering by status code 0 (N/A). This is relevant, for example, if you want to filter WebSockets connections.