Skip to content
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

Closed
icinga-migration opened this issue Jul 24, 2015 · 9 comments
Closed

[dev.icinga.com #9730] Split replay logs on Zone / Endpoint #3179

icinga-migration opened this issue Jul 24, 2015 · 9 comments
Labels
area/distributed Distributed monitoring (master, satellites, clients) enhancement New feature or request

Comments

@icinga-migration
Copy link

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)

Backport?: Not yet backported
Include in Changelog: 1

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:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-08-06 20:25:23 +00:00

  • Category set to Cluster
  • Target Version set to Backlog

@icinga-migration
Copy link
Author

Updated by mfrosch on 2015-08-24 08:13:20 +00:00

  • Subject changed from All replay logs are saved until every zone is connected to Split replay logs on Zone / Endpoint

@icinga-migration
Copy link
Author

Updated by mfrosch on 2015-08-24 08:49:17 +00:00

  • Relates set to 9986

@icinga-migration
Copy link
Author

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:

  • A log per Zone/Endpoint
  • Faster evaluation of what has to be sent

Con:

  • More log files

@icinga-migration
Copy link
Author

Updated by mfrosch on 2015-08-25 12:16:55 +00:00

  • Relates set to 9983

@icinga-migration
Copy link
Author

Updated by mfrosch on 2015-08-25 12:17:50 +00:00

  • Relates set to 9976

@icinga-migration
Copy link
Author

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.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-02-24 23:54:01 +00:00

  • Relates set to 10994

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-09-07 12:24:54 +00:00

  • Status changed from New to Closed
  • Target Version deleted Backlog

We've fixed that in an older version. Please consider upgrading to 2.5.x.

@icinga-migration icinga-migration added enhancement New feature or request area/distributed Distributed monitoring (master, satellites, clients) labels Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/distributed Distributed monitoring (master, satellites, clients) enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant