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 fieldsedit
Error-specific data for APM
view errorsedit
type: keyword
format: url
error id iconedit
type: keyword
format: url
error fieldsedit
Data captured by an agent representing an event occurring in a monitored service.
error.idedit
type: keyword
A UUID for the error.
error.culpritedit
type: text
Function call which was the primary perpetrator of this event.
error.grouping_keyedit
type: keyword
format: url
GroupingKey of the logged error for use in grouping.
exception fieldsedit
Information about the originally thrown error.
error.exception.codeedit
type: keyword
The error code set when the error happened, e.g. database error code.
error.exception.messageedit
type: text
The original error message.
error.exception.moduleedit
type: keyword
The module namespace of the original error.
error.exception.typeedit
type: keyword
error.exception.handlededit
type: boolean
Indicator whether the error was caught somewhere in the code or not.
log fieldsedit
Additional information added by logging the error.
error.log.leveledit
type: keyword
The severity of the record.
error.log.logger_nameedit
type: keyword
The name of the logger instance used.
error.log.messageedit
type: text
The additionally logged error message.
error.log.param_messageedit
type: 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.