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

Trang chủ » Check_mk Xen » Nagios/icinga/... Monitoring Support · Issue #5012 - GitHub

Có thể bạn quan tâm

Skip to content Dismiss alert {{ message }} / xen-orchestra Public
  • Notifications You must be signed in to change notification settings
  • Fork 292
  • Star 913
  • Code
  • Issues 302
  • Pull requests 117
  • Actions
  • Projects
  • Wiki
  • Security

    Uh oh!

    There was an error while loading. Please reload this page.

  • Insights
Additional navigation options nagios/icinga/... monitoring support #5012New issueNew issueClosedClosednagios/icinga/... monitoring support#5012LabelsPriority 3: can wait/workaround 🟡@nagilum99

Description

@nagilum99nagilum99opened on 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.

Metadata

Metadata

Assignees

No one assigned

Labels

Priority 3: can wait/workaround 🟡

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

You can’t perform that action at this time.

Từ khóa » Check_mk Xen