Alerts
The fields and tags in the Alerts data model describe the alerts produced by alerting systems, such as Nagios or NetCool, for use in Splunk correlation searches or dashboards. They are not to be used to describe Splunk Alerts or Notable Events, which are already modeled in other contexts.
Note: A dataset is a component of a data model. In versions of the Splunk platform prior to version 6.5.0, these were referred to as data model objects.
Tags used with the Alerts event dataset
The following tag acts as constraint to identify your events as being relevant to this data model. For more information, see How to use these reference tables.
Dataset name | Tag name |
---|---|
Alerts | alert |
Fields for the Alerts event dataset
The following table lists the extracted and calculated fields for the event dataset in the model. The table does not include any inherited fields. For more information, see How to use these reference tables.
Dataset name | Field name | Data type | Description | Abbreviated list of example values |
---|---|---|---|---|
Alerts | app
|
string | The application involved in the event, such as win:app:trendmicro , vmware , nagios .
|
|
Alerts | body
|
string | The body of a message. | |
Alerts | dest
|
string | The destination of the alert message, such as an email address or SNMP trap. You can alias this from more specific fields, such as dest_host , dest_ip , or dest_name .
|
|
Alerts | dest_bunit
|
string | The business unit associated with the destination. This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. |
|
Alerts | dest_category
|
string | The category of the destination. This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. |
|
Alerts | dest_priority
|
string | The priority of the destination. This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. |
|
Alerts | id
|
string | The unique identifier of a message. | |
Alerts | severity
|
string | The severity of a message. Note: This field is a string. Please use a severity_id field for severity ID fields that are integer data types. Specific values are required. Please use vendor_severity for the vendor's own human-readable strings (such as Good , Bad , Really Bad , and so on).
|
critical , high , medium , low , informational
|
Alerts | severity_id
|
string | A numeric severity indicator for a message. | |
Alerts | src
|
string | The source of the message. You can alias this from more specific fields, such as src_host , src_ip , or src_name .
|
|
Alerts | src_bunit
|
string | The business unit associated with the source. This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. |
|
Alerts | src_category
|
string | The category of the source. This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. |
|
Alerts | src_priority
|
string | The priority of the source. This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. |
|
Alerts | subject
|
string | The message subject. | |
Alerts | tag
|
string | This automatically generated field is used to access tags from within data models. Do not define extractions for this field when writing add-ons. | |
Alerts | type
|
string | The message type. | alarm , alert , event , task
|
How to use these reference tables | Application State |
This documentation applies to the following versions of Splunk® Common Information Model Add-on: 4.1.0, 4.1.1, 4.2.0, 4.3.0, 4.3.1, 4.4.0, 4.5.0, 4.6.0, 4.7.0, 4.8.0, 4.9.0, 4.9.1, 4.10.0, 4.11.0, 4.12.0, 4.13.0, 4.14.0, 4.15.0
Feedback submitted, thanks!