The Monitor Message object will
watch the OpenView Operations server for new or updated messages
and will trigger your Policies based on conditions and filters that
you specify.
The Monitor Message object can be
used to trigger a diagnostic and corrective action Policy that will
respond to critical events on your network.
To configure the Monitor Message
object you need to know the OpenView Operations server that you are
connecting to and what type of messages will trigger the
Policy.
Condition
|
Select the condition that will
trigger the Monitor Message object:
•
|
New
messages – Trigger the Policy when a new message is created
that matches the filter. You cannot use this option with a custom
message attribute. Instead, use one of the “modified” options below
with a custom message attribute.
|
•
|
Modified severity or message text –
Trigger the Policy when a message that matches the filter has its
severity or message text modified.
|
•
|
Acknowledge messages – Trigger the
Policy when a message that matches the filter is
acknowledged.
|
•
|
Unacknowledge messages – Trigger the
Policy when a message that matches the filter is
unacknowledged.
|
•
|
Owned messages – Trigger the Policy
when a message that matches the filter is owned.
|
•
|
Disowned messages – Trigger the Policy
when a message that matches the filter is disowned.
|
•
|
Annotations modified – Trigger the
Policy when an annotation has been added or modified to a message
that matches the filter. This will also trigger when any
annotation, except the last one, has been deleted.
|
•
|
All
annotations removed – Trigger the Policy when the last
annotation is removed from a message that matches the filter.
|
•
|
Message escalated - Trigger the Policy
when a message that matches the filter is escalated.
|
•
|
Message escalated from another server -
Trigger the Policy when a message that matches the filter is
escalated from a different server than the OpenView Operations
server.
|
•
|
Automatic action started - Trigger the
Policy when an automatic action is started for a message that
matches the filter.
|
•
|
Automatic action finished - Trigger the
Policy when an automatic action has finished for a message that
matches the filter.
|
•
|
Operator initiated action started -
Trigger the Policy when an action is started by an Operator for a
message that matches the filter.
|
•
|
Operator initiated action finished -
Trigger the Policy when an action started by an Operator has
completed for a message that matches the filter.
|
|
Filters
|
The list shows all the OpenView
Operations message filters that you have configured. To edit or
remove a filter, select the item and click Edit or Remove respectively. To add a filter,
see the instructions below.
|
Custom Message Attributes
|
You can add custom message
attributes to the Monitor Message object, and to HP OpenView
Operations. In HP OpenView Operations, each custom message
attribute that you add becomes a Published Data item and takes the
name that you assign to that attribute.
1.
|
Click the Custom Message Attributes button. The
Custom Message Attributes
dialog appears.
|
2.
|
Click Add. The Custom Message Attribute dialog
appears.
|
3.
|
In the Name field, type the name for the
custom message attribute.
|
4.
|
Click OK. The Custom Message Attributes dialog
appears.
|
5.
|
Click OK. The Monitor Message Properties dialog
appears.
|
6.
|
Create a filter according to the
instructions below. The attribute that you created appears in the
Field drop-down list.
|
Note: You can remove the custom message
attribute from the Monitor Message object, but you cannot remove it
from HP OpenView Operations.
|
Name
|
Description
|
Message Id
|
The Id of the message that was
detected.
|
Message severity
|
The severity of the message
that was detected.
|
Number of annotations
|
The number of annotations
assigned to the message that was detected.
|
Application
|
The application where the
message originated.
|
Message group
|
The OpenView Operations Message
Group that the message belongs to.
|
Message key
|
The key of the message.
|
Number of duplicate
messages
|
The number of copies of the
message that was detected.
|
Node
|
The managed node where the
message originated.
|
Owned by
|
The owner of the message.
|
Service name
|
The name of the service.
|
Object
|
The object within the
application that generated the message.
|
Creation time
|
The time and date that the
message was created.
|
Receive time
|
The time and date that the
management server received the message.
|
Automatic action status
|
The status of the automatic
action running against the message retrieved.
|
Operator action status
|
The status of the Operator
initiated action running against the message retrieved.
|
Message source type
|
The source type of the message
retrieved.
|
Time owned
|
The time that an Operator took
ownership of the message retrieved.
|
Message status
|
The status of the message
retrieved.
|
Acknowledge time
|
The date and time that the
message was acknowledged.
|
Message text
|
The description text of the
message.
|
Message source
|
The source of the
message.
|
Original message
|
The text of the message when it
was created.
|
Message type
|
The type of the message.
|
Acknowledged by
|
The name of the Operator that
acknowledged the message.
|
Escalated by
|
The name of the Operator that
escalated the message.
|
Time last received
|
The date and time that the last
duplicate message was received.
|
Automatic action auto
acknowledge
|
The setting that determines
whether the message will be automatically acknowledged after the
automatic action has been run.
|
Automatic action
annotations
|
The setting that determines
whether annotations will be added to the message when the automatic
action has started and finished.
|
Operator action auto
acknowledge
|
The setting that determines
whether the message will be automatically acknowledged after an
Operator initiated action has been run.
|
Operator action
annotations
|
The setting that determines
whether annotations will be added to the message when the Operator
initiated action has started and finished.
|
Escalated
|
Indicates whether the message
has been escalated.
|
Escalation server
|
The name of the server where
the message was escalated.
|
Notification
|
The notification status of the
message.
|
Trouble ticket forwarding
|
The setting that determines
whether a trouble ticket should be opened on the associated trouble
ticket system for the message.
|
Trouble ticket
acknowledge
|
The setting that determines if
the message should be acknowledged when it is sent to the trouble
ticket system.
|
Forwarded
|
The management server where the
message was forwarded.
|
Node generated
|
The name of the node where the
event occurred that generated the message.
|
Original message Id
|
The ID of the message when it
was created.
|