Maintenance Periods

From time to time, you will need to perform routine tasks on your infrastructure that will render it unreachable or cause it to operate outside of the norm - upgrades, maintenance, etc. For that reason, we provide Maintenance Periods - finite periods of time where you can instruct Panopta's monitoring of your infrastructure to behave and react in special ways.

Creating Custom Maintenance

Invoking the Create Maintenance Pane

Each of the options below will present you with the same Maintenance Period configuration pane.

From the Maintenance page

  1. In the navigation, select Monitoring, then select Maintenance
  2. In the top left corner, select Add Maintenance

From a specific instance

  1. Navigate to any instance in your account
  2. Towards the top right, there's a block for Maintenance. Click the Add Maintenance button
  3. Select Custom. The Immediate Maintenance options are discussed below.

From an instance group

  1. Navigate to an instance group in your account
  2. Towards the top right, there's a block for Maintenance. Click the Add Maintenance button
  3. Select Custom. The Immediate Maintenance options are discussed below.

Configuring Maintenance

When configuring Maintenance, you can control the general handling of the Maintenance Period, the timing, and the scope of your infrastructure which it covers.

General Configuration Options

Maintenance Period Name
The Maintenance Period name is displayed throughout the Panopta control panel and can be anything of your choosing

Start Time
The Start Time is the time at which the Maintenance Period should commence. If the Maintenance Period will be recurring (see Timing), it will always start at this specific time of day

Duration
Length of time, in minutes, that the Maintenance Period will last. If the Maintenance is recurring, it will last this long each time

Description
A helpful way to communicate what the Maintenance Period covers and why it's being used

Monitoring
The options under Monitoring dictate how Panopta monitors the specific infrastructure covered by the Maintenance

Option
Description

Pause monitoring

All monitoring for the instances covered by the Maintenance Period will be paused - meaning no incidents will be created and no alerts will be sent

Continue monitoring but don't create incidents

All monitoring for the instances covered by the Maintenance Period will continue - however, incidents will not be created, regardless of the monitoring data collected

Continue monitoring & creating incidents but don't send alerts

All monitoring for the instances covered by the Maintenance Period will continue and incidents will be created accordingly - however, no alerts will be sent for any detected incidents

Continue monitoring, creating incidents and sending alerts

Things will operate as normal - however, an Alert Timeline override must be selected to be used for alerting

Show maintenance indicator in public reports
If checked, we'll show a Maintenance badge in your Panopta Status pages if you're using them

End applicable outages when period begins
If checked, any active incidents that are present when maintenance begins will be force-closed

Timing

By default, Maintenance is a one-time event. However, if you have recurring maintenance, you can use the recurring event option. Select the recurring option will present a set of scheduling controls similar to what you'd see in Gmail or Outlook.

  • Every n days: beginning on the day of your Maintenance start date, Maintenance will occur every n days from that point
  • Every n weeks: beginning on the day of your Maintenance start date, Maintenance will occur on the selected days of the week, every n number of weeks. For example, use 1 for every week, 2 for every other week
  • Every n months on the nth day of the month: every n number of months, on the date of the month that coincides with the date of your Start Date. For example, entering a start date of May 1st ever 1 month will schedule Maintenance on the first day of every month
  • Every n months on the nth day of the week of the month: Every month, Maintenance will be created on the n day of the nth week. For example, setting a start date of May 1, 2018, which is the first Tuesday of May, will schedule Maintenance for the first Tuesday of ever month.

Scope

Impacted Instances
By Name
Utilizing the infrastructure tree, you can select the specific instances which will be part of the Maintenance Period

By Group
Utilizing the infrastructure tree, you can select the group(s) which will be part of the Maintenance Period. When the Maintenance Period begins, we'll check each selected group for contained instances; instances present at that time will be placed under maintenance

By Tag
Using the tag selector, enter the instance tags you'd like to select instances by. By default, all the tags you enter must be present on the instance at the time of maintenance creation. However, if you switch it to Match Any, only one of the tags must be present on the instance

If you edit an instance and add a tag which is being used as a maintenance selector for an active Maintenance Period, we'll put it under maintenance accordingly.

Immediate Maintenance

If you're in a hurry and do not need to customize your Maintenance Period, you can invoke immediate maintenance from any instance or group.

  1. On the right side of the page, locate the Maintenance bloc
  2. Click Add Maintenance
  3. Select your desired duration

Maintenance will begin immediately for your instance or group. Monitoring data will continue to report, but alerts will not be sent if an incident is identified