Hi,
We are using the Community NXlog to forward our domain controller security events into Graylog and all was going well until the Microsoft May Security rollup and we now see 100% CPU when Graylog is running.
Is anyone aware of a bug / something else that is causing this?
Thanks
Peter.