clean log messages #2309
Merged
clean log messages #2309
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
ccostino
approved these changes
Jan 30, 2025
There was a problem hiding this comment.
Thank you, @terrazoon!
Noting that I see the ex parameters for the expiry/ttl too, excellent. 🙂
heyitsmebev
approved these changes
Jan 30, 2025
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
UI components are requesting various counts and statuses from the backend multiple times per second, resulting in about half of the lines in the API logs being totally useless and making the logs hard to read and filter through.
Use redis on the UI side to store these values for 30 seconds, so the calls to get fresh data only hit the back end every thirty seconds (i.e. reduce calling volume by 99.9%).
Security Considerations
N/A