Avoid error logs flooding when connecting to a database is failed#4
Open
envzhu wants to merge 1 commit into
Open
Avoid error logs flooding when connecting to a database is failed#4envzhu wants to merge 1 commit into
envzhu wants to merge 1 commit into
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
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.
Problem
When connecting to a database is failed in write_tsdb plugin , error logs floods on the collectd client like below:
Modification
To avoid this, I changed logging code in write_tsdb.c based on
write_graphite.c.Test
Configure collectd.conf to connect to unexist database intendedly.
Before this patch
Error logs flooded.
After this patch
You can see the error interval increases by two times every time the connecting error is logged