-
Notifications
You must be signed in to change notification settings - Fork 17
[enhancement] Kind of logs sent to the broker #110
Comments
Hello, We are exactly in this case, we have a passive infrastructure, and we receive more than 3 million events per hour! Our Centreon that deals with all these events is the bottleneck. These logs are processed by the broker and that is what makes us the most load! |
I am going to take a look at this enhancement. |
Oh thanks you :) |
Hello @bouda1, |
We have made experiments on this improvement but it needs more tests as it can break many things. It should arrive pretty soon, at less I hope. |
No problem, Thank you for taking into account the problem :) |
Hi,
On some big installations, central broker use a lot of resources and is very busy.
In order to reduce its load, it would be nice to be able to choose, with a broker module startup option, kind of logs that will be sent to the broker.
For example, disable the "system logs" (those visible in the Monitoring > Event Logs > System Logs) on pollers's engine could significantly lighten the the load for the broker.
Now, if we disable the BROKER_LOGGED_DATA (1<<5), not only the system logs are not transmitted, but also the monitoring logs. But we would like to keep monitoring logs.
Regards.
The text was updated successfully, but these errors were encountered: