Description of the Performance Management Libary. More...
Description of the Performance Management Libary.
Description of PM MSO.
The physical or logical resources's attributes which needs to be monitored are modeled as PM attributes which will be part of PM MSO in COR. It can have one reset attribute which will be used to reset the PM attributes' values from north bound. The PM MSO should be associated with one Primary Object Implementer (POI).
IDE provides the way to select PM attributes from the list of available attributes. It facilitates to define the threshold values for each PM attribute and associate alarms. These associations can be found in $ASP_CONFIG/clPMConfig.xml file.
PM MSO can contain two types of attributes.
Each PM attribute has the following characteristics:
There can be only one reset attribute configured for a PM MSO. In the reset attribute callback provided, the user has to reset the PM attributes.
The PM MSO life cycle includes
Please refer OpenClovis IDE User's Guide to get know how to configure.
In the IDE, PM attributes can be selected from the list of available attributes. Each PM attribute can be configured cached/non-cached, persisted/non-persisted.
IDE provides the way to configure PM reset attribute for the list of PM attributes selected. We can select one attribute as the PM reset attribute from list of 'writable' attributes available.
Threshold Crossing Alarms or TCA is the unique feature of PM. The PM attributes can be associated with the alarms available with the configured lower and upper threshold values along with the alarm severity. So that when the PM attributes' value falls within the boundary, the configured alarm will be raised.
There can be many levels of thresholds configured and alarms associated. When the PM attributes' value goes from one threshold boundary to another, the alarm associated with the first boundary is cleared and the alarm for the next boundary will be raised. So that the user can configure less severity alarms for low thresholds and higher severity alarms for the high thresholds.
The PM interval configuration is specified in milli seconds. In this interval, the PM library will fetch the registered PM resources's attributes from the POI and process the data, which is called as PM operation. This PM operation also includes updating the cached attributes values into COR and processing the TCA's registered with the threshold boundaries and raise/clear the alarms.
For the PM operation to happen, the user has to register the resource with the PM library. Following are the apis used for PM registration and deregistration which will accept the list of MoIds.
In the IDE each PM MSO can be associated with a Primary OI. During PM operation the PM library will fetch the values from Primary OI and process it, and also when the non-cached PM attributes are read from north bound, the PM library will fetch it from the primary OI. If the PM attribute is cached, then the value in COR is returned.
The Primary OI needs to implement two callbacks.
The first callback will get called when the non-cached PM attributes' are read from northbound and the user is supposed to provide the values. It is also called by the PM library for the PM operation in the configured interval.
The second callback will get called when the PM reset attribute is SET from north bound and the user is supposed to reset all the PM attributes.