IT Operations Management (ITOM)

OMi Monitoring Automation: what’s new to make your monitoring easier?

OMi Monitoring Automation: what’s new to make your monitoring easier?


Guest post by Norbert Andres, Ops Bridge


In today’s IT environment, the configuration of IT monitoring has become difficult. There is an increasing number of components that need to be monitored. This leaves the average organization with dozens of monitoring tools

That is why we developed Monitoring Automation (MA) as an add-on product to Operations Manager i (OMi) that was made available with version 9.22.


It brings the capability to configure the Operations Agent and SiteScope to OMi, but compared to the way you work with e.g. Operations Manager for Windows or Linux it brings some changes and enhancements.


One of the design goals of Monitoring Automation was to have dedicated work flows to simplify the life of application administrators, monitoring developers and subject matter experts.


Let’s take a look at how you can use MA together with the Oracle Management Pack to monitor your Oracle system.

MA brings introduces a new artifact called the “Management Template”. It contains the monitoring capabilities for the complete application stack, in this case, the Oracle database plus the underlying operating system.

Assuming the Oracle Database Instance has already been discovered and populated in the RTSM, there are just a few steps needed to configure your monitoring:


  1. Select an appropriate “Management Template” and deploy it to an “Oracle CI”.


On selecting the deploy option, only appropriate CIs are displayed, in this case Oracle instances.



2. When you assign/deploy the Management Template to my Oracle CI, you need to fill in some parameters, like a username and password…



… and you have the option to change some monitoring parameters like frequencies or thresholds.


  1. Click finish and voila our monitoring is in place.


With this not only the Oracle database is being monitored but also the system it runs on, including agentless and agent-based monitoring.


Based on the topology MA will figure out what are the agent policies to deploy, and where and how many systems are involved. Also it will determine which SiteScope server to use for monitoring the CI agentless and which monitors to instantiate.


From that point on MA will also handle changes in the topology to cover use case like: a node gets added or removed from a cluster, the CI gets moved from one system to another. MA will automatically adapt the monitoring based on the knowledge of the topology that is part of the Management Template (more about this in a future blog post).

To adapt the monitoring we can always go back to the Management Template assignment of this CI and change the parameters. But we will also find “Aspect” assignments on all monitored CIs.


First on the Oracle CI:



… but also on the server it runs on:



Aspects group policy templates used to monitor a certain “aspect” of the CI, e.g. “Oracle Table Space”, “Oracle Discovery”, “Oracle RAC Health”, “CPU Performance”, “System Infrastructure Discovery”. They are self-contained units so they can be assigned independently of other Aspects to the CI they are meant for. An Oracle aspect cannot be deployed to e.g. a SQL Server one. The aspect also encapsulates the underlying OS and the technology used. This way when it is deployed you don’t need to worry whether the software you want to monitor actually runs on Linux or Windows and whether it is monitored with SiteScope or an agent.


So the aspect contains the actual monitoring implementation while the Management Templates attaches it to the topology of the application and enables the topology based automation of monitoring.



Inside the Aspect you’ll find SiteScope solution templates and policies like in OM.

OM policies got enhanced to support external parameters so you are now able to use the same policy with different thresholds/severities or frequencies without having to actually edit the policy.


So to wrap up lets summarize the features of “Monitoring Automation” (MA):

New concepts:

-              Simplified initiation of monitoring

-              Simplified adaption of monitoring

-              Deal with more coarse-graining objects e.g. “Node Performance” instead of single policies

-              Abstraction of the underlying OS

Topology based automation:

-              Automatic assignment of monitoring configuration based on topology

-              Reconfigure the monitoring based on changes in the topology

-              Handling of dynamic and virtual environments

Universal approach to Universal approach to monitoring configuration:

-              Integration with SiteScope

-              Integration with the Operations Agent

-              Integration with ArcSight Logger

Support for different personas and workflows:

-              Support for different role/personas: monitoring developer, application administrator, SME


For more information and trials visit http:/


  • operations bridge
0 Kudos
About the Author


This account is for guest bloggers. The blog post will identify the blogger.


Good one.....