impr: tidy noisy event groups and improve prometheus management #600
+208
−113
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
Removes some particularly spammy event groups from prometheus counts, such that excessive logging does not cause issues on busy nodes. Additionally, if the memory of the prometheus logging server exceeds a standardized bound (1 GiB for now), the Erlang process is killed and rebooted by the next caller. This loses the logs therein, but is preferable over causing the server to significantly disfunction.
samcamwilliams
force-pushed
the
chore/tidy-events
branch
from
d67a64d to
ab35acf
Compare
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.
Removes some particularly spammy event groups from prometheus counts, such that excessive logging does not cause issues on busy nodes.
Additionally, if the memory of the prometheus logging server exceeds a standardized bound (1 GiB for now), the Erlang process is killed and rebooted by the next caller. This loses the logs therein, but is preferable over causing the server to significantly disfunction.