-
Notifications
You must be signed in to change notification settings - Fork 19
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
Not able to retrieve Sysmon logs #75
Comments
When I stop the service:
One time, with |
Does it work with only |
It doesn't work when only I filtered the Sysmon subscription to have a very low EPS rate and I rate limited at 500 per 2 seconds. Here's what I do for a clean test:
Added -vv to the service fluentdopt.
And it goes on writing and enqueuing chunks with the same last sequences of logs. As soon as I change the config with security channels (one or more) and a rate_limit at 10000 / 2 seconds, everything runs smooth. |
I have multiple custom channels where Security and Sysmon logs are forwarded.
At first I was only receiving Security logs and the systems worked like a charm.
As soon as I add sysmon logs in the configuration, I see this behaviour:
The ruby process flushes correctly the first pass of the first security logs, and after that, the memory keeps on increasing without releasing the logs.
Sometimes, when I stop the service, it flushes the Sysmon logs and at other times it does not.
I can correctly query that sysmon channel through winevt and receive XML logs.
The message part is empty and the xml one contains line returns (in do |xml, message, string_inserts|).
I tried to mimic the plugin by editing the log handling with the purest form and removing the parser helper (I only need XML output).
The sysmon logs are correctly written as debug messages to the td-agent.log file but they don't go anywhere after that.
I tried to use different workers, different sources, different output plugins, it just doesn't get to the match part, keeps stuck in the source part, keeping the logs in memory. If I remove the sysmon logs channel and add other ones, it all works fine.
The WEC servers are beasts and the quantity of security logs is higher than the sysmon ones, there is no system or network bottleneck.
Tried with td-agent version 4.1.1 and also 4.1.0 because I saw some memory leak issues.
Any suggestion?
The text was updated successfully, but these errors were encountered: