The Acknowledge Event object will
mark the events that you specify as acknowledged. Since PATROL does
not use unique event identifiers, you must use a combination of an
event ID with filters to specify the events that you want to
acknowledge.
The Acknowledge Event object can be
used to track which events have been viewed.
To configure the Acknowledge Event
object you need to know which system stores the events that you
want to acknowledge, the event ID and the filter associated with
the event.
Name
|
Description
|
Event identifier
|
The ID of the event assigned by
the PATROL agent.
|
Managed system
|
The name of the managed system
where the event was created. The managed system is a combination of
the computer name and the port delimited with an underscore
(_).
|
Computer name
|
The name of the computer where
the managed system is located.
|
Port
|
The name of the port that is
used to communicate with the managed system.
|
User name
|
The user name used to log into
the managed system.
|
Catalog name
|
The name of the catalog that
this event belongs to.
|
Class name
|
The name of the event
class.
|
Event origin
|
The name of the monitored
object that caused the event.
|
Application class name
|
The name of the application
class that created this event. This value will only be valid if the
event originated from an application instance or parameter.
|
Application instance name
|
The name of the application
instance that created this event. This value will only be valid if
the event originated from an application instance or
parameter.
|
Event severity
|
The severity of the
event.
|
Event timestamp
|
The date and time when this
event was created.
|
Status description
|
The full text of the current
status of this event. The possible values are OPEN, ACKNOWLEDGED,
CLOSED, ESCALATED, DELETED.
|
Status value
|
The current status of the
event. The possible values are 1, 2, 3, 4, or 5 and correspond with
the respective status descriptions above.
|
Previous status
description
|
The full text of the previous
status of this event. The possible values are OPEN or
ACKNOWLEDGED.
|
Previous status value
|
The previous status of the
event. The possible values are 1 or 2 and correspond with the
respective Previous status descriptions above.
|
Type description
|
The description of the event
type. The possible values are INFORMATION, STATE CHANGE, ERROR,
WARNING, ALARM, and RESPONSE.
|
Event description
|
The description of the
event.
|
Type value
|
The numeric value of the type
associated with this event. The possible values are 1, 2, 3, 4, 5,
and 6. The values 1-6 correspond with the respective values of the
Type description code.
|
Parameters list
|
The list of parameters entered
for this event.
|
Life expectancy
|
A value describing when the
event will be stored in the Event Repository. Possible values are:
STORED, DEL_IF_CLOSED, DEL_IF_INFO, DO_NOT_STORE.
|
User identifier of event
handler
|
The ID of the user that last
modified the event diary or performed an acknowledge, close, or
delete action on this event.
|
User identifier that owns
event
|
The ID of the user that has
been assigned as the owner of this event.
|
Event diary
|
The text of the event
diary.
|
Events count
|
The number of events that were
acknowledged by the Acknowledge Event object.
|