Outages

In the Outages screen you can:

• Schedule and manage global outages.

  Global outages occur when all processes, probes and jobs are stopped for a period of time, for example for a deployment, upgrade, or system repair or maintenance. In the Outages screen you can see the:

  • Descriptive name for the outage.
  • Date and time from which the outage is effective.
  • Date and time to which the global outage is effective.
  • Whether the status has not started yet or is in progress .

  To schedule a global outage, you need to configure the following:

  • A start date and time for the global outage.
  • The date and time the outage ends.
  • A meaningful descriptive name for the outage.
  • Set post-outage actions for any affected jobs, probes, or daemons. For example, you can choose whether a job should be run immediately after the outage, or when next scheduled.

• View individual outages

  Individual outages are configured as part of a schedule and refer to individual probes, processes or jobs that are stopped for a period of time. For example, you may want to stop certain jobs and probes over weekends or Bank holidays. You cannot create individual outages in the Outages screen; they are created when you create a schedule. However, they are listed in this screen and you can see the:

  • Name of the schedule that includes the outage
  • Type of item to which the outage applies: a process, job, or probe In the Administration Console architecture, a mechanism which allows for the execution of predefined queries and for the comparison of the results of those queries against pre-configured targets. Probes can be reviewed and managed via the Admin Console..
  • Name of the process, job, or probe affected by the outage.
  • Date and time from which the outage is effective.
  • Date and time to which the global outage is effective.

Related Topics