This documentation supports an earlier version of BMC Helix Operations Management.

To view the documentation for the latest version, select 23.1 from the Product version picker.

Patrol Event event class

The Patrol Event (or PATROL_EV) event class is a subclass of the EVENT base event class.

This class represents slots for PATROL events.

Hidden slots

The hidden slots are internal slots that must not be changed.

To understand the list of slots that are used to determine duplicate events, see Slot facets.

SlotSlot display nameTypeDescriptionHidden?
p_agent_addressAgent AddressStringNetwork address of the PATROL Agent host.No
p_agent_namePatrol Agent NameStringHost name of the PATROL Agent.No
p_agent_portAgent PortIntegerPort number of the PATROL Agent.No
p_agent_versionAgent VersionStringVersion of the PATROL Agent (for example, 11.0.00).No
p_applicationApplicationStringName of the application class (for example, NT_HEALTH).No
p_catalogCatalogStringEvent catalog name of originating event (for example, 0).
No
p_classPatrol ClassStringEvent class name of originating event (for example, 11)No
p_handlerHandlerString

Indicates the value, 'Patrol'.

No
p_host_classHost ClassStringType of OS, (example, NT6.2)

This field is important to implement generic actions, such as rebooting a computer on which a problem has occurred. In the background, a generic action can be translated into a specific action based on this field.
No
p_instanceInstanceString

Name of the Monitored instance (for example, PROD1).

No
p_nodeNodeString

Used to display the host name in virtual or remote monitored
environments, where PATROL Event is generated. The host name
returned by this slot depends on MetaFQDN value (which can be obtained by running the AQT commands). If the MetaFQDN value is not set, the host name of managed system is returned.

No
p_originPatrol OriginString

Origin of the PATROL event. Based on the origin, the value can be the application class name, instance name, and the parameter name.

The value will be in the format, <p_application.p_instance.p_parameter>.

For example, p_origin='NT_HEALTH.NT_HEALTH.ResourceContention'

No
p_origin_keyOrigin KeyStringUnique key or ID used by the originating tool to enumerate the event.No
p_origin_sevOrigin SeverityEnum (Severity)

Event severity of originating event.

No
p_ownerPatrol OwnerStringDefault account used to install PATROL agent.No
p_parameterMetricStringName of the metric or parameter.No
p_parameter_unitParameter UnitStringUnit description of the metric or parameter.No
p_parameter_valueMetric ValueStringActual value of the metric or parameter.No
p_publish_hostnameAgentStringPublished host name of the PATROL Agent.No
p_source_idSource IDString

Event id for the event.

No
p_statusPatrol StatusString

Status value of the PATROL event.

Possible values are:

  • OPEN
  • ACK
  • ASSIGNED
  • CLOSED

  • BLACKOUT

No
p_typeTypeString

Type of event (for example, ALARM).


No
source_addressHost AddressStringAddress of the host where the adapter that sent the event is running.No
objectObjectString

Subcomponent of the host with which the event is related.
For example, it could be the name of the disk on which the event is reporting the problem.

No
object_classObject ClassString

Identifies the class of an object.
If the object class cannot be derived from the original event, it must be filled in during the enrichment.

No
object_idObject IDStringIt is a combination of Agent guid, Monitor type, and Instance name.No

Was this page helpful? Yes No Submitting... Thank you

Comments