DevOps is about accelerating delivery of new products and services at scale, reliably and affordably. Doing this requires IT operations automation...
You are here
Opsview Monitor 6.2 is here!
Released this week, Opsview Monitor 6.2 marks -- in several respects -- a subtle but important stepping-off point for the platform: a moment in which several long-term parallel R&D efforts start delivering concrete benefits.
With AutoMonitor - Windows Express Scan, Opsview now delivers increasingly ‘hands-free’ automation options, helping users get large numbers of hosts monitored quickly and predictably, with near-zero manual toil and probability of human error -- no special skills required.
Working through the Opsview Monitor WebUI, Express Scan lets an operator automatically interrogate Windows Active Directory, obtaining IP addresses for physical and virtual hosts, determining which of a range of standard services are running on them, adding the hosts to Opsview Monitor, and assigning appropriate host templates.
Only minimal additional manual work (e.g., providing credentials for MS SQL databases to enable detailed performance analysis) is required to enable monitoring of these resources. Windows Express Scan auto-applies templates to monitor network, the Windows server host OS, and Microsoft services and applications including Hyper-V (enabling automonitoring of virtualization hosts), IIS (Microsoft webservers), MS SQL, DNS, and Exchange.
Meanwhile, several pragmatic improvements make Opsview Monitor 6.2 easier to use and more harmonious with modern infrastructures. Chief among these: Opsview Monitor 6.2 can now be deployed on Ubuntu 18.04+ -- the latest Long-Term-Support (LTS) version of Ubuntu Linux. Additionally, 6.2 also now provides version 7.1 of JasperReports, enabling improved support for later versions of Chrome and Firefox in Opsview reporting.
Opsview Monitor 6.2 ships with a host of new and updated Opspacks as well -- led off by the new Exchange agentless Opspack developed for release with AutoMonitor - Windows Express Scan. Other updates include a new Opspack for monitoring resources on Google Cloud Platform (GCP), a completely revised Opspack for monitoring VMWare vSphere, and the Beta release of a new Opspack for monitoring Azure SQL services.
Elastic Stack Integration
Concurrent with the 6.2 release, Opsview is also providing a complete recipe and tutorial detailing several ways of exporting Opsview Monitor event data to Elastic Stack via Results Exporter -- enabling standardized log storage (on LogStash), search (via ElasticSearch), and analytics/visualization (via Kibana). This tutorial will also work with Opsview Monitor 6.1, provided Results Exporter is installed.
Simple Upgrade Paths
Users of Opsview Monitor 6.0, 6.0.1, or 6.1 should upgrade to 6.2 using an in-place upgrade process or a manual migration. 6.0 EA users should upgrade to 6.0 first.
In-place and manual upgrade options are also provided for users of Opsview Monitor 5.4.2. Users of earlier versions should upgrade to 5.4.2 first.
Plan Your Trial or Upgrade Soon!
It’s a good time to try out Opsview Monitor, or proceed with a pending upgrade. This is especially true for Microsoft-centric IT organizations, for whom AutoMonitor - Windows Express Scan will enable more complete, best-practice coverage of Windows resources, and simplified daily operations.
More like this
So, last Friday night, I decided to turn my infrastructure into code by learning Ansible, and capture the entire demo configuration.
A full guide on using InfluxDB as a time series provider in the recently released Opsview Monitor 5.3.