This documentation applies to the 8.1 version of Service Level Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Collection process

The Collection Points and the Collection Nodes (plug-ins) work together to construct service targets, calculate service target performance, and to provide data source status information. This functionality includes the following transactions:

  • Configure data sources – The plug-in API provides methods to configure Collection Nodes. The Collection Node configuration information typically includes data source, user name, password, communication protocol, and port.
  • Supply KPI landscape information – Upon request from the plug-in API, the Collection Node returns the Key Performance Indicator (KPI) landscape from the data source. The landscape is the tree history of all the potential KPIs from the Collection Node that could be used and monitored by the service target. The landscape view can be dynamic or static . A dynamic view requests communication between the Collection Node and its data source and usually through data source API calls. A static view involves a configuration file that contains landscape information.
  • Collect data – The Collection Node returns a list of data samples for the specified KPI and time interval. If no data is found, an empty list is returned. Depending on the data source, the Collection Node might retain history data samples for a certain period. The data returned must be in numeric form. If the KPI in the data source contains status information, such as OK, warning, error, and so on, a status map must be used to convert the status code to numeric values.
  • Check data source status – The plug-in API contains methods to check the data source connectivity. The Collection Point recognizes and indicates whether landscape discovery or data collection failed.

Note

When you define a service target, you can define how often the Collector evaluates data from the Collection Points. The default is 5 minutes.This processing frequency can be less or more frequent than the Collection Node frequency, but it cannot be more frequent than the data source can generate a value. If it is, the missing data rule applies.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments