Do not log tidewave requests - #76
Merged
Merged
Conversation
jonatanklosko
force-pushed
the
jk-quiet-tidewave-requests
branch
2 times, most recently
from
August 13, 2025 07:23
f7e339b to
0040f13
Compare
jonatanklosko
force-pushed
the
jk-quiet-tidewave-requests
branch
from
August 13, 2025 07:23
0040f13 to
24e7910
Compare
josevalim
reviewed
Aug 13, 2025
Co-authored-by: José Valim <jose.valim@dashbit.co>
Contributor
|
💚 💙 💜 💛 ❤️ |
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.
This prevents /tidewave requests from being logged. One of the MCP tools is
get_logsand including tidewave logs is unnecessary noise. This is particularly relevant for ping requests, which are currently logged every 5 seconds.