Reading and Mapping Ticket Templates
Using Out-of-Box Templates
4-3
The mapping in
Table 4–3
is specific to an update of an Incident caused by a change of
the event status.
IncidentDescri
ption
EMUser
— Notification rule owner
when the ticket is created through
auto-ticketing, and is the Enterprise
Manager log-in user when the ticket is
created through manual-ticketing.
Target Type
: <TargetType>
Target Name
:<TargetName>
MetricColumn
— Name of the metric;
for example, CPU Utilization(%).
MetricName
— Category of the metric.
For the CPU Utilization(%) metric, this
would be ’Load.
KeyColumn
** — For metrics that
monitor a set of objects, KeyColumn
indicates the type of object monitored.
For example, for the Tablespace Space
Used (%) metric that monitors
tablespace objects, the KeyColumn is
’Tablespace Name’.
KeyValues
** — For metrics that monitor
a set of objects, the KeyValues indicate
the specific object that triggered the
severity. For example, for the Tablespace
Space Used (%) metric that monitors
tablespace objects, the KeyValues is
’USERS’ if the USERS tablespace
triggered a warning or critical severity.
SeverityCollectionTimeTargetHost
URL
— URL of the metric details page
in the context of the alert. This points to
the Service Manager Incident in the
Service Manager Web Console.
Values from the Alert
Context
BriefDescri
ption (Title)
<Message>
Note:
The Brief Description field is
displayed as the Incident title in Service
Manager
Values from the Alert
Context
JournalUpd
ates
Incident created by Oracle Enterprise
Manager Connector for the HP Service
Manager based on an alert with
<severity> severity. Message:
<message>.
Values from the Alert
Context
AlertStatus
Service Manager sets to Open by default
on Create Operation
“Open”
Table 4–2 (Cont.) Ticket Creation (Service_Manager_Default_Incident_AutoClose.xsl
Conditiona
l Branch
Service
Manager
Ticket
Attributes
Enterprise Manager Alert Attributes
Value
