WARNING: Version 6.2 of APM Server has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
APM Error fields
editAPM Error fields
editError-specific data for APM
view errors
edittype: keyword
format: url
error id icon
edittype: keyword
format: url
error fields
editData captured by an agent representing an event occurring in a monitored service.
error.id
edittype: keyword
A UUID for the error.
error.culprit
edittype: text
Function call which was the primary perpetrator of this event.
error.grouping_key
edittype: keyword
format: url
GroupingKey of the logged error for use in grouping.
exception fields
editInformation about the originally thrown error.
error.exception.code
edittype: keyword
The error code set when the error happened, e.g. database error code.
error.exception.message
edittype: text
The original error message.
error.exception.module
edittype: keyword
The module namespace of the original error.
error.exception.type
edittype: keyword
error.exception.handled
edittype: boolean
Indicator whether the error was caught somewhere in the code or not.
log fields
editAdditional information added by logging the error.
error.log.level
edittype: keyword
The severity of the record.
error.log.logger_name
edittype: keyword
The name of the logger instance used.
error.log.message
edittype: text
The additionally logged error message.
error.log.param_message
edittype: keyword
A parametrized message. E.g. Could not connect to %s. The property message is still required, and should be equal to the param_message, but with placeholders replaced. In some situations the param_message is used to group errors together.