-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
Timed out #4
Comments
Hi @mweel1! I am not up to speed on the internals of this package, so apologies if this isn't useful info, but just in case you're stuck, Seq also accepts events in the GELF format via its Seq.Input.Gelf plug-in, and I think GELF transports are just about always non-blocking. There are a couple of GELF hooks/formatters for Logrus out there. HTH! |
@nblumhardt Hi, Thanks for getting back to me, yeah it looked like it was blocking/sync on the http requests. I implemented this, if you ever need it. It basically uses a message queue and worker processes, and drops messages if the queue size reaches 5000. We saw a huge performance boost in doing this.
|
Awesome! Unless you plan to use message templates with named holes in your Logrus messages, you might get slightly better handling on the Seq side by using the Thanks for sharing your solution! 😎 |
Hey @mweel1 thanks for raising this. It looks like we need an option for a timeout on the http client, it's probably a good idea to use a dedicated client instead of the built in one too. |
I had to bring down the log server, and my go app stopped responding.
Any idea why this would happen? Should my go log calls be wrapped in a go routine?
Thank you
The text was updated successfully, but these errors were encountered: