SOLUTION //
XCP-ng and Xen Orchestra Operators
On XCP-ng the load you see may be the control layer's, not the host's. How 2501 finds the guest behind a busy host and leaves changes to running guests to a person.
TICKETS FROM
ServiceNow or another ITSM
SAFEGUARDS
Your rules, confirmation and blacklists
AUTONOMY
Investigate only, with a person, or on its own
DEPLOYMENT
On-prem, cloud or hybrid
█
SOLUTION_BRIEFING
// HOW 2501 HANDLES IT
When an XCP-ng host is reported busy, restarting the heaviest guest is the quick fix, but the load you see on logging in describes only the host's control layer, and the guest really to blame may not show in it. 2501 works out which layer is loaded and which guest is responsible, all within limits you set.
An alert says the host is saturated. Whoever takes it logs in, reads a load figure and restarts the biggest guest, interrupting a service that may not be the cause, for a spike that may already be over.
The XCP-ng CLI Operator works from the host's control layer, which sees only its own slice of the host, and says which layer each figure describes: the control layer, the physical host or a guest. It names the guest behind the load, its share of the host, and whether the load is a spike or sustained. If a stray process in the control layer is the cause, it can end that process where you allow it. If the cause is inside a guest, it names the guest and the evidence.
Why does the host look calm while a guest is maxed out? The control layer's own figures cover only its slice of the host, so a saturated guest does not show in them. 2501 reads each guest's own figures instead.
Does it work through Xen Orchestra? Yes. The Xen Orchestra API Operator reads the same figures through Xen Orchestra, without logging in to the hypervisor, and reports what its account cannot see.
> READY_TO_DEPLOY
Book a technical demo and walk through your own environment with the 2501 team.
