Use case
Review cron jobs and backup results in one inbox
Scheduled work often succeeds quietly until the one result you need to inspect. A dedicated inbox preserves every reported outcome and makes failures easy to separate from routine success.
Updated 5 min read
Report success, failure and missed execution distinctly
Send a completion event
Include the schedule window, duration and verification result after the job finishes.
Send a failure event
Use a higher severity, a concise failure stage and a link to the relevant run or log view.
Detect absence separately
Let a supervisor emit a missed-run event when the expected completion signal does not arrive.
Preserve enough structure to compare runs
- Filter by the backup source and error severity during an incident.
- Use tags to separate production, staging and different backup classes.
- Keep size, duration and scheduled window as bounded metadata values.
Frequently asked questions
- Does the producer need a special integration?
- No. The examples use an authenticated HTTPS request, so any script, service or visual workflow that can send HTTP can use the same contract.
- Should credentials be included in notification data?
- No. Keep credentials in the producer's secret store and send only the context needed to understand or locate the event.
Keep exploring
Put the pattern to work
Existing accounts can open the inbox and send their next event.