These guides target IR v2.3.1 and were checked on . They are worked examples, not production defaults or promises of delivery time.
Choose the problem, then the configuration
Measure the change before estimating the return
These are model scenarios, not customer success stories. Compare a pilot with a baseline covering similar alert sources and staffed hours. Track time to acknowledgement, unowned alerts and manual rerouting; report sample sizes as well as percentages. Check business outcomes in the relevant commerce, support or backup systems. Faster acknowledgement alone is not proof of restored revenue or availability.
What every pilot must prove
A successful HTTP request is only the start. Check the selected route, service, assignee and delivery on a real device. Then test a missing responder, duplicate event, recovery and provider outage. Keep a rollback path before moving a production sender.
IR receives signals from monitoring systems; it does not replace their detection logic. Self-hosting also leaves availability, backups, upgrades and provider credentials with your team. Choose one narrow workflow first and expand only after its acceptance checks pass.