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

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

Log Alert event class

The Log Alert (or LOGALERT_EV) event class represents slots for log alert events. To add custom slots, see Event management endpoints in the REST API.

Important

The hidden slots are internal slots and cannot be changed.

For the event slots that have the string or list of string data types, the character limit of the slot value is 32766. If the value goes above this limit, the value is trimmed, which results in data loss.


Slot nameSlot display nameTypeDescriptionHidden?
source_addressHost AddressString

IP address of the event source.

No
source_portSource PortIntegerPort of the event provider.No
locationLocationStringSource of the event.No
detailsDetailed MessageString

Detailed information about the event.

Expands the information in the msg slot.

No
aliasAliasList of string

Will be used for event association with the CI.

Default value:

[BMC_ComputerSystem:: <source_hostname>]

You can change the default value using the events API endpoint. For more information, see the "Managing event data" section on the Event management endpoints in the REST API page.

No
tagsTagsList of stringRepresents a logical value to identify a group of events of a particular type.No
user_assignedOwnerStringCurrent user assigned to the event.No
incident_idIncident IDStringIncident ID generated/associated with event.No
incident_companyIncident CompanyString

Incident company, or the tenant name.

Example

"incident_company": "Calbro Services"

No
componentaliasComponent AliasString

The component alias that is used for incident generation.

Example

componentalias = Oracle Database Server:<hostname>:<domain>:<instancename>

No
modelnameModel NameString

The model name that is used for incident generation.

Example

modelname = Oracle Database server

No
instancenameCMDB Instance NameString

The Configuration Management Database (CMDB) instance name that is used for incident generation.

Example

instancename = DB instance name

No
priorityPriority

Enum (Priority)

Default=PRIORITY_5

Records the original priority of the event upon insertion. Also, records current priority of the event.

Values:

  • PRIORITY_5 (lowest priority)
  • PRIORITY_4

  • PRIORITY_3

  • PRIORITY_2

  • PRIORITY_1 (highest priority)

No
categoryCategory

Enum (Category)

Default: OPERATIONS_MANAGEMENT

High-level normalized category of the object that the event represents. This is based on appropriate Information and Technology Infrastructure Library (ITIL) core process.

Possible categories are:

  • SLA_MANAGEMENT
  • CAPACITY_MANAGEMENT
  • SERVICE_CONTINUITY_MANAGEMENT
  • AVAILABILITY_MANAGEMENT
  • INCIDENT_MANAGEMENT
  • CONFIGURATION_MANAGEMENT
  • RELEASE_MANAGEMENT
  • PROBLEM_MANAGEMENT
  • CHANGE_MANAGEMENT
  • OPERATIONS_MANAGEMENT
  • SECURITY_MANAGEMENT
  • FINANCIAL_MANAGEMENT
  • SERVICE_DESK_MANAGEMENT

No
sub_categoryMonitor CategorySub_category

Subcategory of the object the event represents based on the appropriate Information Technology Infrastructure Library (ITIL) core process.

Possible values are:

  • OTHER
  • APPLICATION
  • DATABASE
  • NETWORK
  • SYSTEM
  • USER_TRANSACTIONS

No
significanceSignificanceInteger
No

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

Comments