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 #12628] Allow icinga2 agent (command execution bridge) to connect to multiple icinga2 masters/satellites #4626

Open
icinga-migration opened this issue Sep 2, 2016 · 4 comments
Labels
area/distributed Distributed monitoring (master, satellites, clients) enhancement New feature or request needs-sponsoring Not low on priority but also not scheduled soon without any incentive

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12628

Created by hvhaugwitz on 2016-09-02 07:37:25 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-11-18 13:59:59 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

I want to replace nrpe on the client hosts with icinga2 agent. Using nrpe it is possible to use one nrpe daemon for multiple masters (eg icinga2 prod and stage cluster). With icinga2 I need one daemon/port per cluster.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-11-18 13:59:59 +00:00

  • Category set to Cluster

@icinga-migration icinga-migration added enhancement New feature or request area/distributed Distributed monitoring (master, satellites, clients) labels Jan 17, 2017
@dnsmichi dnsmichi added the needs-sponsoring Not low on priority but also not scheduled soon without any incentive label Nov 9, 2017
@dnsmichi dnsmichi removed the wishlist label May 9, 2019
@htriem
Copy link
Contributor

htriem commented Jan 22, 2020

Related to #5108.

@Al2Klimov
Copy link
Member

@hvhaugwitz Just for the record, are you the OP?

@hvhaugwitz
Copy link

@hvhaugwitz Just for the record, are you the OP?

Yes, I'm the original poster.

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 needs-sponsoring Not low on priority but also not scheduled soon without any incentive
Projects
None yet
Development

No branches or pull requests

5 participants