November 2007 - Posts
Today I received what I later considered an interesting request for help. Customer wanted to use the time of event causing alert to be used inside of this alert description. He realized that it would be the time of the first event triggering such alert
Read More...
This post explains main data types which are involved in monitoring of application log files. Depending on the monitor used, following data types are initially created by data source modules. Following is a sample of the data type created by System.ApplicationLog.GenericLogReader
Read More...
I started series describing some of the data items floating thru the workflows of Operations Manager 2007. I will try to cover most commonly used ones as well as those more complex ones in order to help with the creation of XPath which is later to be
Read More...
This data type is created by consolidator condition module, which is one of the modules that creates new data item for its output. Luckily consolidator also appends its input into this newly created DT and it can be find inside of context. $Data/…$ context
Read More...
This data type is used as input for recovery task. Recovery can be executed on diagnostic or it can be executed on the state change where later is always present because diagnostic is always associated with state change of monitor. Because this is input
Read More...
This post is to continue Parameter replacements series . So far I talked about all but Data replacements so now I will try to describe it little more. This context replacement is unfortunately most hard to use one of all … Data Context Parameters Some
Read More...
To continue Parameter replacements series , let’s remind ourselves that context parameters can be used and will be replaced by the runtime with the actual parameter value. So far I talked about Config and MPElement replacements before and now I will try
Read More...
As started in Parameter replacements (part1) , context parameters can be used in any part of a text and replaced by the runtime with the actual parameter value before the module is instantiated. Management Pack Element Context Parameters Some monitoring
Read More...
Management packs contain definitions of rules, monitors or composite module types where those monitoring objects need to be configured. In the configuration of the module type, in addition to providing constant values, you can also provide variable context
Read More...
Many of you know already that alert’s description can contain value of any of the properties of the data type causing the alert to be raised in the first place. What is little cryptic though, is how to write XPath query to receive the value from input
Read More...
Rolling upgrade of OpsMgr2007 is performed the way that server bits are upgraded, new management packs are requested and delivered and those are later pushed down to agents. Operations Manager 2007 SP1 Release Candidate contains an issue when monitoring
Read More...
Agent proxying needs to be enabled when health service discovers instance of some managed entity type for which management context doesn’t provide information that this exact health service will also monitor this instance. For example proxying must be
Read More...
Unfortunately there is no way to troubleshoot if alert suppression works as expected, especially in the case when dynamic value to suppress against was used. By dynamic value I mean replacement that runtime must try to do in the case of using $Data/<xpath
Read More...
Alert suppression is feature that allows for greater flexibility of alerts raised. So how was alert suppression feature designed? First we need to distinguish between types of alert that could be raised in Operations Manager 2007. Monitor state change
Read More...
