Devices

Scheduled Down Time (SDT) Tab

Configuring scheduled downtime allows for alert notifications to be supressed during periods where alerts are expected, upgrades are scheduled, or other maintenance is occurring.  Alerts for the groups, devices, or instances in SDT will still appear in your account, but no alert notifications will be generated.

Entities that are in SDT will still be subject to Active Discovery.

Scheduled down time can be applied to a group, a specific datasource across a group, a device, a device datasource, or a specific instance.


Adding an SDT

 Select the Add button on the SDT Tab for the item you'd like to schedule down time for (i.e. group, device, datasource or instance):




Once you click "Add," the following lightbox will appear: 


The Add SDT dialog is identical for devices, datasources and instances.  For groups, there is an additional Datasource field (pictured above), that allows you to put one or all datasources across the group into SDT.  When an SDT is applied at the device level it automatically applies to all datasources.  

Datasource (Group SDT only)

Select all datasources to put all datasources for all devices in the group into SDT.  Select a single datasource to apply the SDT to one datasource across all member devices (e.g. you are upgrading your website so you expect the Apache datasource across all web servers to trigger alerts, but CPU, disks, and interfaces metrics for those web servers should be fine).

One time SDT

Select the duration for a singular SDT.

Repeat SDT

Select the repeat interval for the SDT and the duration.  The next SDT to be applied will display in the Upcoming SDTs section.

Notes

Notes will display in the manage SDTs tables, providing context for the SDT reason.

Viewing Existing SDTs

Entities in SDT will be displayed with an SDT-specific icon at every level of the device tree. Additionally, you can use the SDT tab for a group, device, datasource or instance to see a table of all active and upcoming SDTs that apply to the entity.  For example:

At a Group, you will see any SDT for sub groups, member devices, or member datasources.  These are SDTs that will result in part of the group not generating alert notifications.

At an instance level, you will see any SDT for a parent device or group.  These are SDTs that will result in the instance not generating alert notifications.  


The font size and columns displayed in the SDT tables can be adjusted by selecting Settings.  

Manage

Manage


Selecting the manage gear icon will display the SDT configuration window.  This allows you to update SDT time, date, or schedule.

Repeats

If the SDT is scheduled to recur, the repeats column will indicate if it is daily, weekly, or monthly.

Next Start and Next End

The start and end time for the next scheduled down time.  This will be removed when the SDT begins if it is a one time event.  If it is a repeat event, the next start time will update accordingly.

Duration

The length of the SDT.

Type

Indicates if the SDT is a device group, device, datasource, or instance SDT.

Applied At

The applied at field indicates where the SDT was applied.  This is the name of the group, device, datasource or instance.

Created By

The user name of the user who created the SDT.

Viewing SDT History

You can view a history of SDTs at the node-level to which the SDT was set. For instance, if an SDT was set for an instance, the historical record for that SDT will only be available in that instance's SDT tab, not at the device/device group level in which that instance lives.

Viewing SDT History

Can I change or stop an active SDT?

Can I change or stop an active SDT?

If you have a SDT scheduled but you no longer need it, you can stop an active SDT.  Navigate to the SDT tab for the appropriate Group, Device, or Instance. Click the dropdown to expand the Active SDT row.  Select Stop SDT.  This will effectively set the end time to the time Stop was selected.

If you need to extend the SDT, selecting the gear icon to manage will provide you the option to change the end time.