Monitoring
Once an application is onboarded, monitoring is the daily work. Engage arranges it from the widest scope inward: the Dashboard counts every application, an application's own page shows its records view by view, and each record opens into a trace or a timeline. Two organisation-wide lists sit beside that path for the things that went wrong: Delivery Failures for messages Engage could not deliver, and Global Fallout for failed executions across every application.
Every screen here is filtered by the environment selected in the header, Development or Production, and by a date range. When a screen looks empty, those two filters are the first thing to check.
Screens
The Dashboard
Run, success, and error totals for the organisation, and a row per application to open.
Read the totalsApplication details
One application's page: the Overview table, Logs, Fallouts, Configuration, and Documentation tabs.
Open an applicationExecution details
Trace, drilldown, and Timeline View for a single record in the Overview table.
Follow a recordDelivery Failures
The dead-letter queue: messages Engage could not deliver, and how to retry a whole range.
Retry messagesGlobal Fallout
Every fallout in the organisation, with retry, restart, and resolve actions on each.
Work the listChoose a task
| Goal | Guide |
|---|---|
| See whether anything failed today, anywhere | The Dashboard |
| Find a specific record and see its data | Application details |
| Understand why one record failed | Execution details |
| Retry every message that dead-lettered in a window | Delivery Failures |
| Retry or resolve a failed execution | Global Fallout |
| Change what happens to a fallout automatically | Managing fallouts |
| Be told when something fails | Alerting |
Where to start
Start on The Dashboard. Its per-application rows open the application page, and everything else on this section is one or two selections from there.