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
[dev.icinga.com #9730] Split replay logs on Zone / Endpoint #3179
Comments
Updated by mfriedrich on 2015-08-06 20:25:23 +00:00
|
Updated by mfrosch on 2015-08-24 08:13:20 +00:00
|
Updated by mfrosch on 2015-08-24 08:49:17 +00:00
|
Updated by mfrosch on 2015-08-24 08:53:44 +00:00 So gunnar and I discussed this and plan to do this with 2.4, since the change should be fairly minimal. For instances that does not have any logs (pending) there won't be a log. Pro:
Con:
|
Updated by mfrosch on 2015-08-25 12:16:55 +00:00
|
Updated by mfrosch on 2015-08-25 12:17:50 +00:00
|
Updated by mfriedrich on 2015-09-05 14:45:27 +00:00 Feedback from a discussion with Tom: Multiple log files also mean many open file handles. Consider that when having 10000 clients and zones. |
Updated by mfriedrich on 2016-02-24 23:54:01 +00:00
|
Updated by mfriedrich on 2016-09-07 12:24:54 +00:00
We've fixed that in an older version. Please consider upgrading to 2.5.x. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9730
Created by aledermueller on 2015-07-24 08:32:23 +00:00
Assignee: (none)
Status: Closed (closed on 2016-09-07 12:24:54 +00:00)
Target Version: (none)
Last Update: 2016-09-07 12:24:54 +00:00 (in Redmine)
Hi,
I have a master zone and several agent zones. If one agent zone is not connected, all replay logs are saved. In huge environments the logs grow pretty fast, which could be a problem. May be it is possible to filter the logs before saving. If not please add a hint in your documentation.
Regards, Achim
.
Relations:
The text was updated successfully, but these errors were encountered: