Alert channels
Add Slack or webhook channels from Alerts. Channels can be enabled, disabled, and tested before they are used for production issues.
- Slack: connect a workspace, choose the destination, and send a test alert before relying on it.
- Webhook: send issue notifications to an internal incident tool or automation endpoint.
- Batching: reduce alert noise by grouping related events before delivery.
Health rules
Create rules for high failure rates, stalled destinations, retry backlog, and missing lifecycle events. Keep rules focused so each alert maps to a clear owner and next action.
- Failed delivery count: alert when a destination has too many failed attempts in a window.
- Failure rate: alert when the percentage of failed deliveries crosses your threshold.
- No recent success: alert when a destination has not had a successful delivery for too long.
- Due retry backlog: alert when failed work is waiting longer than expected.
- Missing event issues: alert when Relin detects that an expected lifecycle event did not arrive.
Issue workflow
- An issue appears in the dashboard and optionally posts to your alert channel.
- Open the issue and follow the linked event, vendor reference, or destination.
- Fix the receiver, signing secret, vendor setup, or missing connection.
- Replay affected events when another delivery is needed.
- Leave the issue open until the related event flow is healthy again.
Recommended alert setup
- One channel for production delivery failures.
- One channel for missing-event or reconciliation issues.
- A lower-noise channel for test sources and development feeds.
- Rules scoped to important sources instead of one broad rule for everything.