Part 4 – Authoring the Management Pack – classes, discoveries and relationships

This is a summary of what we will walk through:

  • Create a Management Pack Solution and Project
  • Create a class for application server based on application component –> so health doesn’t roll up to windows computer. We want our infrastructure teams to support the computer and our application teams to support their applications.
  • Create a relationship that the application component is hosted by windows computer. The monitoring will be done by the agent on the computer (it is hosted by the computer) but without the dependency roll up there will be no health rollup to windows computer
  • Discover the application servers based on a registry key
  • Create Groups
    • Create a group of application servers
    • Create a computer group of application servers
    • Create a group of operating system objects from the application servers
    • Create a group of logical disks from the application servers
    • Create a group of websites
    • Create a group of application pools
    • Create a group of databases
    • Create a group of Health Service Watcher Objects
    • Create a group that contains all the other groups (this will provide us with the health state of the application)
  • We want our groups to have a health state based on the health state of the objects within the group. I have therefore created a dependency rollup monitor for each of the groups.
Previous articles in series

Part 1 – Background

Part 2 – Visualisations with Squared Up

Part 3 – Application Monitoring Overview

Later articles in the series

Part 5 – Create the Management Pack Solution and Project

Part 6 – Create the Management Pack components

Part 7 – Create the Squared Up Dashboard

Leave a Reply

Your email address will not be published. Required fields are marked *