Skip to main content

Fleet Operations & RMM+

The Fleet Operations module brings remote monitoring and management (RMM) directly into AtlasOS through integration with Level.io. This gives MSPs a unified view of customer endpoints alongside service tickets, SLA tracking, and billing — eliminating the need to context-switch between PSA and RMM tools.

Connecting Level.io​

  1. Navigate to Administration > Integrations > RMM+.
  2. Enter your Level.io API credentials (API key and organisation ID).
  3. AtlasOS will sync your endpoint inventory, alert policies, and device groups.
  4. Map Level.io customers to AtlasOS customer records for unified reporting.

Once connected, endpoint data flows into AtlasOS in near real-time.

Endpoint Fleet Management​

Fleet View​

The Fleet Operations sidebar section provides a consolidated view of all managed endpoints:

  • Device inventory — hardware, OS, agent version, last check-in time.
  • Health status — online, offline, degraded, or alerting.
  • Customer grouping — endpoints organised by customer for quick navigation.
  • Search and filter — find devices by name, customer, OS, status, or tag.

Device Detail​

Click any device to view:

  • Hardware and software inventory
  • Patch status and pending updates
  • Active alerts and alert history
  • Recent remote sessions
  • SLA context (which customer SLA applies to this device)

Alert Queue and Triage​

Level.io alerts are ingested into the AtlasOS alert queue within Fleet Operations:

  • Alerts are categorised by severity (Critical, Warning, Informational).
  • Each alert links to the originating device and customer record.
  • Technicians can acknowledge, escalate, or resolve alerts directly from the queue.
  • Unresolved alerts beyond the configured threshold trigger SLA deadline tracking.

SLA-Linked Ticket Creation​

When an alert requires hands-on work:

  1. Click Create Ticket from the alert detail.
  2. AtlasOS pre-fills the ticket with device context, customer, and SLA tier.
  3. The SLA clock starts automatically based on the customer's response time target.
  4. The ticket appears in the Delivery section alongside manually created tasks.

Automated Remediation​

Configure automated responses to common alert types:

  • Script execution — run predefined remediation scripts on the endpoint via Level.io.
  • Restart services — automatically restart failed services when specific alerts fire.
  • Patch deployment — trigger patch installation for critical security updates.
  • Notification only — send an alert notification without automated action.

Automation rules are managed under Fleet Operations > Automations.

Fleet Reports​

Generate fleet-level reports covering:

  • Device health summary — uptime, offline frequency, alert volume per device.
  • Patch compliance — percentage of endpoints with current patches.
  • Alert trends — alert volume over time, most common alert types, mean time to resolution.
  • Per-customer fleet health — device counts, health scores, and SLA impact per customer.

Reports can be exported and shared via the Client Portal.

Security Monitoring​

The Fleet Operations module surfaces security-relevant data:

  • Antivirus status and definition currency across the fleet.
  • Failed login attempts and suspicious activity alerts.
  • Devices with outdated operating systems or missing critical patches.
  • Endpoints that have not checked in within a configurable threshold.

This data feeds into the Dashboard for practice-wide security posture visibility.