OP5 Monitor ["OP5 Monitor"]["Release Notes"]

This page contains the list of all highlights that have recently been introduced in OP5 Monitor.
For detailed release notes for all versions of OP5 Monitor, see ITRS OP5 Monitor 9.x Release Notes.

Release Notes

Hybrid IT environments

Many of our customers have started to incorporate cloud into their IT estate. This is a natural evolution, and OP5 Monitor shall continue to be a best-in-class monitoring tool for networks and on-premise environments, while evolving to support dynamic environments. We call the mix between traditional IT and dynamic environments the Hybrid IT. We have already started the work of supporting Hybrid IT environments with these new items:

  • We have created the Slim Poller, a containerised lightweight version of OP5 Monitor poller configuration. This was especially designed to enable the OP5 Monitor poller to run as a container in environments such as OpenShift and Kubernetes. Slim Poller supports autoscaling in Kubernetes, can be set up automatically with environment variables, and can auto-register with the cluster.
  • We have created a plugin specifically for monitoring Amazon Web Services (AWS) resources. The plugin allows for this by accessing the AWS native cloud monitoring called CloudWatch.
  • We have created a plugin for monitoring of Kubernetes cluster components such as deployments (replicas), nodes, and pods.
  • We have the latest version of OP5 Monitor available in AWS and Azure Marketplace for easy deployment in the cloud.
  • The check_vmware_v2 plugin replaces the check_vmware_api plugin to bring extended capabilities for monitoring VMware networks.

Security hardening

IT security is imperative for most organisations today, and with OP5 Monitor we take security seriously. We have been working on a number of items that will make OP5 Monitor even more secure.

  • Communications between masters, peers, and pollers through the Merlin protocol can now be secured with public key encryption.
  • We have introduced ModSecurity, which is a web application firewall. The main reason is to prevent potential cross-scripting attacks in OP5 Monitor.
  • We have removed the need for root user privileges. You can now use sudo to run mon commands such as start, stop, restart, and node status.
  • We continuously scan our components for potential vulnerabilities.


Integrations between best-in-class tools are especially important in today's business landscape. We have developed integrations between OP5 Monitor and Log Analytics. Log Analytics is based on the ELK stack and provides collection and analytics based on logs. With this integration, it is possible to create alerts OP5 Monitor based on events in logs that are collected with Log Analytics.

There are several integrations possible with OP5 Monitor through the API. We have expanded this API with an endpoint for management of Scheduled Downtimes.

Enhanced Autodiscovery

Autodiscovery has been enhanced to make it even easier to find new hosts in your OP5 Monitor network:

  • Schedule your Autodiscovery jobs to run on specific days and times.
  • Assign host groups or templates immediately to discovered hosts from the View discoveries tab, before you import them.
  • See discovered hosts from the main OP5 Monitor page via a notification banner.
  • Add hosts to an exclusion list to keep them from reappearing in your discovery results.