Monitoring Azure IaaS, Azure PaaS and On-Premise IT: Case Study

Back to news

Corporate IT is increasingly heterogeneous with both internal (legacy) and external components hosted by third-party vendors (Cloud). Monitoring of these different elements is a must as we have already mentioned several times in past blogs. Let’s use a real case to show how to set up a monitoring infrastructure  where IaaS and PaaS are hosted in Azure while some IT infrastructure is still housed internally.

Overview

Our example is a car park management company, who have a connected system to indicate to users of the car park, the available spaces. In this way it maximizes the occupancy of the car park, while de-stressing their customers, by reducing the time needed to find a space.

Our parking manager has a system based on 3 elements:

PaaS in Azure :

  • an IoT Hub for real-time sensor status feedback
  • Azure BDD, database for storing real-time data
  • Many WebApps for exposing APIs and a management web interface
  • a “notification hub” to send notifications to support as necessary

IaaS in Azure:

  • a Windows machine with a SQL Server (“BI” database)
  • a Windows machine with PowerBI for the management and production of various reports

Internal for:

  • Information retrieval
  • Manage the information display signs
  • Manage the local network

Implementing monitoring with ServiceNav:

Stage 1 : Monitor the elements

For PaaS : Use the ‘MS-Azure-PaaS-Metrics’ service template to monitor key metrics and compare to thresholds.

For IaaS : Two options were possible: Set up a ServiceNav Box on the Azure platform as a VM, in the same VLAN as the machines to be monitored or, monitor using the Azure APIs using host templates and associated service templates; with the ServiceNav Box set up in the companies Internal IT. We finally opted for a ServiceNav Box as a VM in the Azure cloud.

For Internal systems: “Classic” monitoring with the installation of a ServiceNav Box as close as possible (network-wise) to the hosts  to be monitored. The ServiceNav Box is connected to the ServiceNav SaaS platform. It queries the devices (server, windows services, network devices, signage …) via SNMP and WMI.

Stage 2 : Create a MAP

Using a PowerPoint image, displaying the customers infrastructure, and by overlaying the different monitored elements over this image ( hosts, services, user services), we can build a very visual representation of the infrastructure, showing its status in real time along with important metrics.

Stage 3: Create IT Weather User Service

By aggregating all the checks, it is also possible to build a hierarchical IT Weather service showing the complete health of the parking space management system. It is then possible From this, we can calculate an SLA on the complete availability of this service.

 

Conclusion

Thanks to ServiceNav and its integrated service and host templates, it is possible to monitor a mixed infrastructure of Azure Cloud and internal “Legacy” IT. From technical monitoring to functional operation, the real-time view of the complete infrastructure and the calculation of SLAs, ServiceNav responds to the needs of all customer teams involved in the project.

UK ServiceNav Product Development Manager; my priority is to be needful of the particular requirements of all ‘English-speaking’ markets where ServiceNav is sold. I have over 20 years experience of the IT monitoring field - covering a wide variety of products and technologies.

More recent posts from the Servicenav team

27/6/19

ServiceNav 4.3 – Dashlink, Timeframe improvement, Azure PaaS objects Plugins

Summary Dashlink – a new way to collaborate with Dataviz dashboards Would you like to be able to share part of the management console with… Read more

20/6/19

Monitoring: A Suggested Roadmap for Choosing the Right Tool – Part 2

We saw in the previous article the issues and methodology surrounding selection of monitoring tools.  Now let’s see how to implement this using a real… Read more

20/6/19

Monitoring: A Suggested Roadmap for Choosing the Right Tool – Part 1

The Problem The primary purpose of a monitoring solution is to collect data over a wide area, to correlate, analyze, alert and to produce information… Read more