Skip to main content

Fleet-Wide Questions

A ticket is one device. The question that saves the week is whether the same thing is happening on thirty others.

Once agents are on the fleet, ask across a client or across everything you manage.

  • "Which endpoints at this client need attention right now, and why?"
  • "That same Veeam failure, did it hit other machines in the same window?"
  • "We just closed a print spooler ticket on one box. Who else is showing the early signs?"
  • "Which devices stopped reporting this week?"

Ask when you want the count or the list. Run an investigation when you want the cited write-up for one host, then take the fleet question back to chat.

Automate it​

A daily pass over yesterday's tickets, then a hunt for the same shape across the fleet, is L3 work nobody has time to do by hand. Put that pass in your automation: an MCP client that already talks to the PSA can query SparkLogs in the same run. See Connect MCP.

Surprises can still reach a user first. The gain is that you hunt the fleet from evidence already recorded, instead of waiting to instrument the next occurrence.

What to watch in the product​

Configure > Agents is the operator view of the same health data: connectivity, collection, skip notices, and stop reasons (upgrade, shutdown, or silent). Home dashboard notices about agents needing attention or offline open that list with the matching filter already applied.

Scope​

  • macOS and Linux agents are on the roadmap.
  • At launch, off-endpoint systems (a SaaS EDR console, a NAS with no agent) stay in the outside-visibility list until you connect those sources another way.

Connect: plugin or MCP.