Nagios/icinga/... Monitoring Support · Issue #5012 - GitHub

Skip to content Dismiss alert {{ message }} vatesfr / xen-orchestra Public

• Notifications You must be signed in to change notification settings
• Fork 265
• Star 793

• Code
• Issues 256
• Pull requests 103
• Actions
• Projects
• Wiki
• Security
• Insights

Additional navigation options

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.

Sign up for GitHub

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

Jump to bottom nagios/icinga/... monitoring support #5012 Closed nagilum99 opened this issue May 21, 2020 · 6 comments Closed nagios/icinga/... monitoring support #5012 nagilum99 opened this issue May 21, 2020 · 6 comments Labels Priority 3: can wait/workaround 🟡

Comments

Copy link

nagilum99 commented May 21, 2020

If I didn't notice that XO already includes it, please close it. I'm not sure which way it would be better: Implemement in XO or XCP-ng itself, but what it's lacking is: Support for external monitoring like being used in larger companies. Very common is here the "nagios-standard", means something that could be triggered by nagios-based systems: nagios, icinga, check_mk... It could e.g. be implemented via https://github.com/bootc/nrpe-ng Would need to get a config-file that (somehow) collects data of the included servers: disk free mem usage Dom0-load iops on storage X, Y, Z... (more ideas?) Could be based on a table, a bit like SNMP/OID does it. Citrix never had any interest to support external monitoring. I don't know which way would be better: Trigger XCP-ng itself or XO, IMHO that decision is better placed on developer-side. XO is not super big and probably could be used as an 'adapter' everywhere.

All reactions Copy link Member

olivierlambert commented May 21, 2020

Hi, Netdata is currently support and even packaged in XCP-ng. I think you can already install alternative monitoring agent solutions in the dom0 without too many deps. So I'm not sure what is the request here?

All reactions Copy link Author

nagilum99 commented May 21, 2020

Modifying Dom0 is always tricky in case you need support, so the best way should be including in default image or at least have an entry in the wiki how to do it in a 'supported way'. (I know support is always tricky if people do something that wasn't meant to be, but that way it would at least be more common and easier to follow up for supporters - and an easy way for everyone to get it working). Never touched netdata, but when I see CLOUD at first and things like "Starting with v1.12, Netdata collects anonymous usage information by default and sends it to Google Analytics" I'm not very motivated to 'go deeper'. Nagios (and the forks) are quite common/wide spread and common on-site monitoring solutions, that, IMHO, fit good to XCP-ng.

All reactions Copy link Member

olivierlambert commented May 21, 2020 • edited Loading

Again, if there's not many modifications, it's fine to do that on your side. We are doing pro support for people just have basic agents in their dom0. Regarding Netdata, you can configure anything (or disable some stuff) and even stream to a central server.

All reactions Copy link Author

nagilum99 commented May 21, 2020

"We are doing pro support for people just have basic agents in their dom0." What does that mean? Is it okay for someone to add e.g. nagios agents if he wants to use pro support or not? Adding a 2nd monitoring solution to the current environment is not an option for me (and a bunch of other admins I know). Migrations are also... you know "never touch..." these things can go big and complex and aren't easy to migrate if you have hundrets or thousands of hosts, running multiple services each.

All reactions Copy link Member

olivierlambert commented May 21, 2020

It is OK, as long there's not too many deps pulled to install it. In general, it's available in base repo, so at worst you got another yum install after an ISO upgrade. I mean, it's your responsibility, and a broken Nagios agent won't be "supported", but the host will be still under support for all other stuff.

All reactions marcungeschikts added the Priority 3: can wait/workaround 🟡 label Jul 28, 2023 Copy link Member

olivierlambert commented Sep 14, 2023

Not directly related to XO, closing. Feel free to argue if I'm wrong :)

All reactions olivierlambert closed this as completed Sep 14, 2023 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Assignees No one assigned Labels Priority 3: can wait/workaround 🟡 Projects None yet Milestone No milestone Development

No branches or pull requests

3 participants You can’t perform that action at this time.