A managed object is an entity in your system or business process landscape; in technical monitoring it is also a container for metrics, events, and alerts. For each displayed managed object (see Navigating in the Directory Browser), the following attributes are displayed in the Directory Browser in six tab pages:
Metrics
A metric is a measurable entity that through a value and other attributes, such as threshold values, has a valuation or a status - for example, a response time is a metric. The following attributes are displayed for the metrics of the selected managed object:
Attribute | Description |
---|---|
| The |
| The |
| A Example The average response time per transaction is a metric group; a metric type that belongs to this group is the average response time in transaction SE80. End of the example. |
| The |
| The Note The End of the note. |
| The change status is only displayed if you activate the Note Since the determination of the MEA change status is time-consuming and does not always function reliably, we recommend that you do not activate the corresponding indicator. End of the note. |
If you select a metric, its details are shown in 5 tabs, under the metric table:
Tab | Description |
---|---|
| |
| This tab shows technical details about collecting the metric, i.e. which data providor determines the value of the metric, using which technology, how often. The collection parameters which the data providor needs to determine the value, are also output. |
| This tab shows which components (
|
| This tab shows how the delivered values of the metric are rated (status |
| This tab contains technical information, particularly IDs, for the metric. This information can be used, for example, for troubleshooting (see Monitoring and Alerting Infrastructure Analysis Tools)- |
Events
An event is a relevant status change of a managed object. It is based on a measured value, or the valuation of one or more metrics or another event. Events can therefore occur in hierarchies and forward their status to the superordinate event in each case.
Attribute | Description |
---|---|
| The name of the event type is a short text that describes the event. |
| These attributes specify the managed object type (such as technical system) and the managed object itself (such as the technical system PRD) to which the selected event belongs. |
| This attribute contains a technical classification of the event. |
| The valuation specifies how the status of the event is calculated from the status of the metrics or events that contribute to this event. Possible valuation rules are:
|
| This indicator specifies whether an alert is immediately generated when this event occurs. |
| These technical attributes specify whether, in the event hierarchy, an event is received from underlying events ( |
| These attributes correspond to the attributes with the same names on the |
If you select an event, its details are shown in 5 tabs, under the event table. This is analogous information to the metric (see above).
Alerts
An alert represents a situation in which the user has to react. It is always triggered by precisely one event.
Attribute | Description |
---|---|
| The name of the alert type is a short text that describes the alert. |
| The severity of the alert is a number between zero and nine that specifies how much of a problem the alert indicates (the larger the number, the more critical the alert). |
| These attributes correspond to the attributes with the same names on the |
If you select an alert, its details are shown in 7 tabs, under the alert table:
Tab | Description |
---|---|
| This tab shows basic alert type information and a short alert description. |
| This tab shows which metric and event types are assigned to this alert type. |
| This tab specifies whether messages which are created automatically when an alert occurs, are assigned to the alert type. You specify this in the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), in the following steps:
The help text for this step describes the settings. |
| This tab specifies whether notifications, which are sent automatically when an alert occurs, are assigned to the alert type. Specify this in the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), as specified above. |
| This tab specifies whether third-party tools are assigned to the alert type. Specify this in the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), as specified above. |
| This tab specifies whether auto-responses, which run automatically when an alert occurs, are assigned to the alert type. Specify this in the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), as specified above. |
| This tab contains technical information, particularly IDs, for the alert type. This information can be used, for example, for troubleshooting (see Monitoring and Alerting Infrastructure Analysis Tools)- |
Templates Used
A template combines types for metrics, events, and alerts and their attributes. SAP delivers templates of this type that you can copy or change yourself.
For every monitoring application case there is usually exactly one used template (templates for different application cases do not overlap in terms of content). The only exception to this is if you have made changes to the general template yourself for a specifc managed object. In this case, there can be two used templates for one application case, one of which will have the name of the managed object. This template contains the values that have been specifically assigned to the managed object itself; these values are then used in preference to the values from the general template.
Attribute | Description |
---|---|
| The name of the template is a short text that describes the template. |
| There can be different versions of a template, but only one of these is active. The number of the active version is specified here. |
| These attributes specify when and by which user the template was assigned to the selected managed object. |
| These attributes correspond to the attributes with the same names on the |
Managed Objects: Tags
There are tag, whose values characterize various types of managed objects. These tags are given values in SAP Solution Manager configuration. The Monitoring and Alerting Infrastructure uses the values of this tag to display values for the object in user interfaces.
Example
The object type Technical Instance
has the following three tags:
Tag Name | Description |
---|---|
| System ID (e.g. |
| Technical Instance (e.g. |
| Technical system type (e.g. |
Collector Parameter Variables
Data is captured in the monitoring and alerting infrastructure, by data collectors, which either report new values independently, or are queried by the infrastructure at regular intervals. Parameter values give the collectors the information about the managed objects required to collect data from them.
This tag shows the names and values of these collector parameters, grouped by monitoring use cases.