We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am using ELK and make a tcp connection to my logstash.
Today my ELK is crash down and I found my server will slowly by this code.
When logrus try to do this:
fmt.Fprintf(os.Stderr, "Failed to fire hook: %v\n", err)
My linux file is open too much.
I know I can rewrite fire and levels function make it return nil.
I just 4-5 log / second.
The text was updated successfully, but these errors were encountered:
We need more context to understand what your problem is. Which hooks are you using, a code sample, etc ...
Sorry, something went wrong.
The code is in the entry.go 259 line (version tag v1.7.0).
My scenario is when elk is disconnected, this code will cause my operating system to open the file repeatedly.
Because ELK log is very huge. The file will open to many and let server crash down.
I think no one thought that the log server would be disconnected.
My suggestion is to use rate limit algorithm to solve.
We have changed the locking system in v1.8.1
No branches or pull requests
I am using ELK and make a tcp connection to my logstash.
Today my ELK is crash down and I found my server will slowly by this code.
When logrus try to do this:
My linux file is open too much.
I know I can rewrite fire and levels function make it return nil.
I just 4-5 log / second.
The text was updated successfully, but these errors were encountered: