filter out POST /api/graphql spam from sndev logs #1780
Merged
Conversation
This file contains 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
huumn
requested changes
Dec 30, 2024
|
Yes, that's intentional. I don't want to make the filter too broad to avoid the risk of filtering out legitimate logs. I'm focusing on filtering the graphql calls, as they are the primary source of pollution. I've changed the command to not use -P, can you try it now? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Since a Next.js update, the dev environment has started logging HTTP requests, which has caused the logs to become cluttered with logs of POST /api/graphql requests. This is an actual issue of Next.js, see the related discussion here: vercel/next.js#65992.
This PR adds a workaround to filter out these logs by using grep in the sndev logs command.
Screenshots
before / after