List of Tooltip Parameters

The following table lists the tooltip parameters and their descriptions:

Parameter

Description

The percentage of available transactions.
The measurements which influenced the HI.
The full description of the alert.
The number of application exceptions monitored by Diagnostics.
The number of instances with At risk status.
In EUM, the weighted average availability based on the total number of users accessing a page.
The availability of a Business Process Monitor or Real User Monitor transaction.
The average status of the CI.
The duration of the completed transactions minus the duration of the failed transactions divided by the total number of transactions.
The time period for which the average response time/average availability was calculated. This time period is defined in the file for the CI.
The average net time (total time minus user time) of a transaction monitored by Real User Monitor.
The average response time for a transaction.
The average latency of all of the server requests on the Virtual Machine monitored by the Probe over the last five minute period.
The percentage of successful runs for the parent transaction during a time period up to the last received update.
The average backend duration for successful, completed transactions.
The maximum backend duration for successful, completed transactions.
The minimum backend duration for successful, completed transactions.
The number of backlogged (in-process) transactions.
The number of bytes that represents the traffic between the Real User Monitor application server and clients.
The number of instances with Blocked status.
The financial loss calculated for the CI.
The name of the rule that calculates the KPI status or value.
The value of logic rule parameter.
Status is calculated based on the samples received during the specified duration.
The last calculation time on the Business Logic Engine machine.
The calendar used for calculating PNR.
The number of calls per minute to the selected Web services or Operations.
The name of the KPIs that caused unavailability.
The name of the CI.
The CI's CI Type.
The availability of the Real User Monitor (for a monitor CI) or the status of the monitor with the worst status (for a group CI).
The number of instances that completed the monitored step or group of steps in the most recent collection interval for the tooltip.
The number of instances with Critical status.
The number of samples with Critical status.
The percentage of failed in-process transactions out of the total completed transactions. Delays Value    The total value of failed in-process transactions.
The total value of failed in-process transactions.
A description of the CI (the first one represents UDX and the second one represents EMS). Only the value relevant to the context is displayed.
The date and time that downtime is due to finish for a CI.
The average end user duration for successful, completed transactions.
The maximum end user duration for successful, completed transactions.
The minimum end user duration for successful, completed transactions.
The average duration for successful, completed transactions.
The maximum duration for successful, completed transactions.
The minimum duration for successful, completed transactions.
The samples description. The samples are separated from each other by a horizontal line.
The error message that appears in the sample.
The amount of exceptions generated over the last five minute period.
The percentage of transactions that did not follow the expected flow path on the target machine, out of the total in-process transactions.
The total value of transactions that did not follow the expected flow path on the target machine.
The number of transactions that failed.
The financial loss (in $) due to transactions that failed.
The percentage of failed completed transactions out of the total number of completed transactions.
The formula that is used to calculate the KPI status and value.
List the number of tickets with the specified status.
The number of instances with Healthy status.
Child CIs not currently displayed.
The average status for the CI over a period of time.
The worst status for the CI over a period of time.
The history calculation type to be used when calculating history status. Values can be: Worst, Average, or None (no history status displayed). The value of the parameter is assigned to the HistoryType rule global parameter. If the value is none, the historical information is not displayed.
The name of the machine associated with the monitor.
One of the thresholds used when defining status for the CI. The CI changes to Informational (green) status when the CI's score is equal to or smaller than this value. 
The number of instances with status Informational.
All of the child CIs belonging to other views, which are connected to this CI but do not belong to this view.
The number of child CIs of the selected CI, that exist in the RTSM, are hidden in the current view, and have at least one KPI assigned to them. This parameter is displayed as: Hidden child CIs (with attached KPIs) in the tooltip itself. For details on Invisible Children, see Find visible and hidden child CIs.
The date and time of the last status (color) change of the CI.
The date and time that the last update for the CI was received by Service Health.
The financial loss (in $) due to transactions that were late.
The average round trip time for a packet. (The time it takes for a packet to go from the client to the server and back from the server to the client). The latency information is provided by the Real User Monitor sample.
The location of the CI if a location has been specified.
One of the thresholds used when defining status for the CI. The CI changes to Major (orange) status when the CI's score is equal to or smaller than this value.
The number of instances with Major status.
The number of samples with Major status.
The maximum response time for a transaction.
The maximal time a Diagnostics transaction has run in seconds.
The maximum time that the item may be unavailable, according to the SLA.
The maximum value of the instances that passed through the monitored step or group of steps, during the last collection interval.
The name of the measurement from SiteScope.
One or more values returned by the monitor the last time it ran, as displayed in SiteScope. This may simply be the retrieval time and file size or it may include specific parameters for a server component.
The minimum response time as provided by the Deep Transaction Tracing sample.
The value of the PassedStatus rule parameter.
The minimum duration of the instances that passed through the monitored step or group of steps, during the last collection interval
One of the thresholds used when defining status for the CI. The CI changes to Minor (yellow) status when the CI's score is equal to or smaller than this value.
The number of instances with Minor status.
The number of samples with Minor status.
The monitor type that the CI represents.
The percentage of successful connections.
The number of actions on the application.
The number of connections monitored by Real User Monitor.
The number of error-type events monitored by Real User Monitor.
The number of informational events monitored by Real User Monitor.
The number of instances that completed the monitored step or group of steps.
The number of open sessions on the application, EUG subgroup, or location.
The number of performance-type events monitored by Real User Monitor.
The number of current ticket that have the specified initial and final state.
The number of times a transaction was completed successfully.
The total number of successful, completed transactions.
The number of successful, completed transactions monitored by TransactionVision.
One of the thresholds used when defining status for the CI. The CI changes to OK (green) status when the CI's score is equal to or smaller than this value.
The number of instances with OK status.
The number of samples with OK status.
The date and time when the alert was issued.
The owner of the CI in OpenView (the first one represents UDX and the second one represents EMS). Only the value relevant to the context is displayed.
The average download time, for a Real User Monitor CI.
The percentage of Real User Monitor sessions without performance events.
Indicates the platform (J2EE or .NET) on which the monitored application is running.
The item's SLA availability percentage the last time data was polled.
The amount of time left for that measurement before the SLA is in breach of contract.
The threshold of the response time as provided by the Deep Transaction Tracing sample.
The percentage of green and yellow child CIs. This is a weighted percentage if any of the child CIs have a weight > 1 (check this by viewing the tooltips for the child CIs).
Note that Service Health is calculating status using the refined percentage method if a percentage is displayed for Score and the group or subgroup status is yellow.
If Service Health is calculating status for the group/subgroup using the dominant child method, the message n/a (Using dominant child) is displayed.
(BPM Transaction tooltips only.) The amount of server requests over the last five minute period.
(BPM Transaction tooltips only.) The average time taken for the server to process the transaction.
The severity of the SiteScope measurement (the first one represents UDX and the second one represents EMS). Only the value relevant to the context is displayed.
The name of the SAP CCMS measurement where the alert occurred.
The name of the SLA attached to this CI
The SAP state of the alert: Active.
CI or indicator status (calculated according to one of the status calculation methods).
It may also display:
Not up to date for decayed CIs, indicating that the CI has passed its timeout period. (For a SiteScope CI, this status is displayed after a SiteScope monitor is disabled.)
Stopped when a Business Process is stopped.
Can be defined as OK, Warning or Critical.
The value of the rule's duration parameter.
The percentage of time that the item must be available to match the `Exceeded' threshold, according to the SLA.
The amount of timeouts that occurred during the last five minute period.
The total number of hits/transactions for Real User Monitor.
The total number of incidents.
The total of the number of transactions that failed and the number of late transactions.
The financial loss (in $) due to transactions that failed added to the transactions that were late.
The tracking period used to calculate the PNR.
The name of the parent transaction for the CI.
The number of transactions monitored by Diagnostics.
The average server time of a transaction monitored by Real User Monitor.
The average total time of a transaction monitored by Real User Monitor.
The number of completed transactions.
The trend of the KPI's status.
The number of calls that are under the threshold defined for the Availability KPI.
The value of the field in the sample.
The sum of the values of the fields in the sample.
The collection interval for which the HI is calculated.
The number of hits in Real User Monitor.
One of the thresholds used when defining status for the CI. The CI changes to Warning (light green) status when the CI's score is equal to or smaller than this value.
The number of instances with Warning status.
The number of samples with Warning status.
The value of the weighted average duration calculated by the rule.