Scheduled work
Schedule a period in which your monitors aren't checked and don't alert, without disabling them or affecting their availability.
On this page
Scheduled work is a period with a start and an end in which ARGUNIS deliberately stops checking some monitors: maintenance, an update, or a DNS propagation. It works for servers, WebServices, TCP, UX tests, databases, IBM i systems, cloud services, and entire inventory groups. A group includes everything inside it, including its subgroups.
While it lasts:
What happens | Detail |
|---|---|
Not checked | ARGUNIS doesn't check those monitors; whatever agents and probes report during that time is discarded |
No alerts | It doesn't open incidents or send notifications; incidents that were already open are put on hold and don't escalate |
Shown separately | The monitor appears in blue-violet as Scheduled work, not as down or disabled |
Doesn't count toward availability | That time neither adds nor subtracts in the details pages or in reports |
When it ends, the monitors come back on their own and are checked immediately. A server with an agent has 3 minutes to reconnect before it's marked down.
Scheduled work isn't the same as Disable. A disabled monitor stops being checked until you enable it again; scheduled work has an end and comes back on its own.
On the screen
In Core → Help Desk → Scheduled work you see three tabs: Upcoming, In progress, and Finished. Each row shows the Title, the Monitors and groups it covers, the Start, the End, the Status, and who created it.
Each monitor's details page also shows whether it's in scheduled work, any upcoming work, and the Schedule work button.