Opsview 6.9.x End of Support

Opsview versions 6.9.x reached their End of Support (EOS) status at the end of January 2026, in accordance with our Support policy. As of this date, these versions no longer receive code fixes, security updates, maintenance releases, or backported changes.

The documentation for version 6.9.7 and earlier releases will remain accessible for reference, but it will no longer be updated or maintained. We strongly recommend upgrading to the latest supported version of Opsview to ensure continued support and access to the latest features and security enhancements.

Downtime

In the IT industry, it is common to have “maintenance windows” or “maintenance periods” during which the engineers may configure additional pieces of infrastructure, upgrade, reconfigure of remove others.

In Opsview Monitor, this would naturally trigger host failures. Therefore, Opsview users can set up a ‘Downtime’ which is a defined period of time applied to a range of objects such as Service Checks or Hosts during which failures are not notified but rather automatically converted to a ‘handled’ state. Users who usually get alerted in case of errors for the given monitored environment do not get such notifications during this particular scheduled period of time as errors are actually expected.

Note

The scheduled checks will still be executed for the host in downtime however no notifications will be sent out.

In order to have the ability to schedule downtime, your User within Opsview Monitor must be in a Role which has the ‘DOWNTIMESOME’ access control option checked.

Downtime can be configured for:

• Host Groups.
• Hosts.
• Service Checks.
• Hashtags.
• Business Services & Components.