1
response

We currently have an issue where we pass log4net data into logstash it stops writing events after a period of time. We deployed Nxlogs to pull IIS logs into logstash where logstash stopped processing new events after 20 minutes using the Udp appender.

Unfortunately using tcp isn't an option due to the protential risk of it slowing our production environment down. Has anyone got any suggestions on how we can use NXlogs and stop logstash from stopping (we use the community edition) or is the only way to parse it into a messaging queue like Redis first then logstash?

AskedJune 4, 2018 - 3:17pm

Answer (1)

Based on the description it seems like logstash is stopping, not NXLog. I'm not sure what solution you're looking for? Perhaps it would be more appropriate to ask in the elastic.co forums.