Trigger Error Handler Logs
On this page
Atlas Device Sync, Atlas Edge Server, Data API, and HTTPS Endpoints are deprecated. Refer to the deprecation page for details.
Overview
Trigger error handler logs are created whenever Atlas executes a custom error handler via an AWS EventBridge Trigger that failed and could not be successfully retried.
Note
Only Supported for Database EventBridge Triggers
Currently, custom error handling is only supported for database-type EventBridge triggers.
Log Format
Trigger error handler log entries have the following form:
Logs: [ <log line>, <log line>, ... ] See Function. See Trigger. See Original Logs. Compute Used: <number> bytes•ms
Fields
Field | Description |
|---|---|
Compute Used | The computational load of the operation. |
Logs | A list of console.log outputs. App Services saves the first 512 bytes of the first 25 console.log() calls. |
See Function. See Trigger. See Original Logs. | Links to the custom error handler Function that was run by this event, the EventBridge Trigger whose failure launched this event, and the error logs created by the original Trigger failure event. |
Error Fields
Log entries created by unsuccessful operations may feature additional fields for debugging purposes. These include the following:
Field | Description |
|---|---|
Error | A brief description of an error. |