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.

Overview of performance-monitoring service targets

Performance-monitoring service targets are evaluated on system metrics coming from infrastructure items such as servers and applications. They compare the measurements to the goals defined in the service target to determine if the service target is met or missed.

For example, the data sources could be transaction management or network management products that produce high-volume, high-frequency data about availability and performance of machines, services, and applications. This type of service target is usually processed outside BMC Remedy AR System in the Collector. For more information about configuring the Collector, see Configuring the Collector Configuration Console.

Performance-monitoring goals are defined when you select the key performance indicator, goal, and cost details for a service target. The goals are made up of single values, arithmetic expressions, or Boolean expressions containing key performance indicators. When a value is received, the processor compares the value against the service target's goal.

When you define a performance-monitoring service target, you can set a numeric value for the goal; for example, the response time for an application must be less than or equal to 4 seconds. When the data is processed, this goal is compared with the metrics received from the monitoring agent and then translated into one of four states:

  • OK
  • At Risk
  • Missed
  • Unknown

The goal types for performance-monitoring service targets can also be displayed with any label, as shown in the following examples:

  • Disk space usage
    With this goal type, the service target commits to maintaining at least a certain amount of free disk space on the server's disk drive as specified in the goals of the service target.
  • Application response time
    With this goal type, the service target commits to maintaining application response time at a certain level as specified in the goals of the service target.
    For example, a sales person in your company needs to submit several sales orders within a certain time period. You can define a performance-monitoring service target that states that the application he uses to submit sales orders has to respond or successfully submit the order within four seconds or less. The monitoring agent records the application response time and sends data to the processor. The processor compares the data to these goals specified in the service target.

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.