Standard event attributes in Entuity
To view values of the standard attributes
To define an incident that triggers an email when raised:
Introduction:
In Entuity, event attributes are useful in the following cases:
- when you define actions that set the value of an attribute, e.g. the supplied flapping unify rules include a set event type action.
- when you define conditions based on the testing of an attribute.
- when you add additional information to the event (enrich the event) and store it within the database.
- when you include event details in emails.
Standard event attributes in Entuity:
Please find below the standard event and incident attributes in Entuity. Events and incidents share the same standard set of attributes. You can also enrich events with additional attributes - please see this article for help and information on how to add additional attributes to events in Entuity.
Event Attribute | Description |
---|---|
type | identifier of the event type or incident type. |
name | name of the event or incident. |
severity | severity level of the event or incident. |
reason | reason the event was raised, e.g. for an SNMP failure, it may be 100% of 4 SNMP requests failed in the past 40 seconds. |
context | textual information for the event. It may include a description of the state that the object was in before raising the event, or another environment description that is helpfuil in understanding the cause of the event. This field is not always present. |
reportId | identification of the process that has sent the event. This field is not always present. |
source |
source of the incidence within Entuity, e.g. com.entuity.events.engine.groovy.InventoryObjectProxy@3c5 |
sourcecompleteIdString |
internal identifier of the object within Entuity. Each component may have two identifiers; the separate identifier is the StormWorks identifier. |
sourceExternalId |
additional textual identification for the object, which may be useful in identifying objects which may not be represented by StormWorks. Values may be an IP address of the object, but may be any text. |
SourceName |
name of the source object - it may be a resolved name or an IP address. |
To view values of the standard attributes:
When developing events and incidents, or familiarising yourself with the Entuity event management system (EMS), you may want to see values of the standard attributes associated with an event or incident. The following example demonstrates how to send an email containing event attributes. This example uses the following techniques:
- variables to set the email recipient, and to control when the email is sent.
- variable test condition.
- send email action.
- set the email throttle action. This allows the server to combine emails to the same recipient when they are raised within a defined period.
- assign the email action to an incident.
Please see this article for help and information on how to add a variable to Entuity.
To define an incident that triggers an email when raised:
Please see this article for further help and information on defining an incident that triggers an email when raised.
Comments
0 comments
Please sign in to leave a comment.