Error fields
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
These fields can represent errors of any kind.
Use them for errors that happen while fetching events or in cases where the event itself contains an error.
| Field | Description | Level |
|---|---|---|
| error.code | Error code describing the error. type: keyword |
core |
| error.id | Unique identifier for the error. type: keyword |
core |
| error.message | Error message. type: match_only_text   exception.message |
core |
| error.stack_trace | The stack trace of this error in plain text. type: wildcard Multi-fields: * error.stack_trace.text (type: match_only_text) exception.stacktrace |
extended |
| error.type | The type of the error, for example the class name of the exception. type: keyword example: java.lang.NullPointerException  error.type |
extended |