THE MONITORING WALKTHROUGH
From a device signal
to a clear next step.
See what IronAgents can demonstrate today: visibility, investigation and deliberate monitoring changes.
Illustrative sample data. The panels below explain implemented workflows. They are not live devices, product screenshots or controls connected to your fleet.
Start the walkthrough1 / DEVICE VISIBILITY
Start with the last check-in.
Open Fleet to see which devices are reporting. A recent check-in tells you the collector reached the application; it does not prove every service is healthy.
A device that has never reported stays Waiting for first check-in. A previously reporting device becomes Offline after the three-minute grace period and evaluation.
Learn how to confirm a first check-inBuild server is connected and still needs attention. Investigate the two observations separately.
2 / HISTORY & ALERTS
A spike, or a sustained problem?
Open a device for resource history and basic inventory. Compare an incident with fresh CPU, memory and system-disk readings, then inspect the effective alert rule.
On Windows and Ubuntu, selected-service observations can show a sustained stop while the device still reports. Offline means lost check-ins; it does not identify a stopped service.
Distinguish offline from stopped- Trigger
- ≥90% for 5 minutes
- Recovery
- ≤80% for 2 minutes
- Inventory
- Ubuntu · 8 logical CPUs · 16 GB RAM
CPU alerts are disabled by default. This example assumes the rule has been enabled.
3 / PATCH & REBOOT VISIBILITY
Read the report before deciding.
Updates shows offered OS updates, reboot signals, their source and freshness. Unknown and stale results are different from a current zero count.
Use your existing OS maintenance process to install patches. IronAgents does not deploy OS updates or initiate reboots. Mac's current reboot state remains Unknown.
Understand each platform's report- Source
- Existing APT package lists
- Report age
- 12 minutes
- Catalog age
- 1 day
- Reboot
- No reboot flagged
The agent reads existing catalogs. It does not refresh package lists or install the offered updates.
4 / POLICIES & MAINTENANCE
Share rules. Keep exceptions visible.
Set organization defaults, site policies and deliberate machine overrides. Review the affected-device preview before saving changes.
Start a bounded maintenance window before planned work. Notifications pause while check-ins, real status and observations continue. Maintenance starts immediately; recurring schedules are unavailable.
Read policy inheritance · Set a maintenance window- CPU rule
- Inherited from organization
- Offline timing
- Machine override · 30 minutes
- Maintenance
- Active · 42 minutes remaining
Observations continue. An offline device remains visibly offline during maintenance.
5 / IronAgents AGENT UPDATES
Confirm the new version reported.
After one local helper setup, an owner or operator can request an agent update from the application. Follow the request through installation and a confirming check-in.
This workflow has passed on the tested Ubuntu, Mac and Windows devices. Helper startup after reboot and broader lifecycle checks remain separate. It updates IronAgents's software only.
Read setup, progress and local controls- QueuedWaiting for the dedicated helper
- InstallingVerified IronAgents release
- Waiting for check-inInstallation reported; confirmation pending
- SucceededRequested version confirmed by check-in
This is an illustrated sequence, not an active update request.
YOUR NEXT STEP
Choose a supported setup path.
Existing development users can follow their platform guide, enroll one device and verify its first report. Installers remain development releases with signing limitations.
Choose your platformRead current scope and future direction · Pilot availability