Our NOC team is transitioning into managing Liongard and needs to fully operate within ConnectWise Manage. However, the current setup makes this challenging because ticket creation from Roar Inspectors is tied to the environment where the Roar Inspector lives (e.g., our top-level "Ntiva, Inc." account), not the individual client environments where the issues occur.

For example, if 10 SonicWall inspectors are failing across 10 different clients, we want 10 separate tickets—each tied to the correct client. Right now, a Roar metric that surfaces these failures results in a single ticket under our parent account, not per-client, which breaks the workflow for our NOC and ticket handling.

This limitation impacts staffing planning, daily operations, and how we build out alerting strategies within Liongard. We need a scalable way to alert and create tickets per client without deploying hundreds of Roar Inspectors or building complex external workflows.

I would expect that:

Metrics and actionable alerts could support ticket creation per client environment even when surfaced via a centralized inspector like Roar.

Roar (or future child Roar Inspectors) could be extended to create tickets directly under the client environments that the surfaced issues relate to.

Alternatively, inspector status (e.g., “failing for X days”) could be accessible in the Data Print, enabling global alerting logic and per-client ticket routing.

All of this should remain compatible with Liongard’s ConnectWise Manage integration, so status changes in Manage reflect properly in Liongard, and vice versa.