When logrus fires the hooks in one environment where only Logstash hook is enable, the flow gets stuck there from time to time.
We know it is the hook firing after some golang debugging (go-delve).
Isn't there any way to add a timeout for the hooks? I believe it is because in that environment logstash is not very stable (connection) and seems the hook doesn't continue if there is any issue.
I was thinking maybe when creating the connection to logstash? But I believe logrus should have a mechanism to protect itself from the hooks....
Hi,
When logrus fires the hooks in one environment where only Logstash hook is enable, the flow gets stuck there from time to time.
We know it is the hook firing after some golang debugging (go-delve).
Isn't there any way to add a timeout for the hooks? I believe it is because in that environment logstash is not very stable (connection) and seems the hook doesn't continue if there is any issue.
I was thinking maybe when creating the connection to logstash? But I believe logrus should have a mechanism to protect itself from the hooks....