Verify a saved alert policy before trusting its grouping, escalation, and quiet hours. This is a reporter, not an alerting service: it never sends a message, resolves a recipient, opens a socket, or reads a live provider. It evaluates a deliberately narrow JSON scenario using an explicit virtual UTC cutoff.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
npm run check
node bin/alert-routing-simulator.mjs --root . --scenario examples/scenario-pass.json --at 2026-09-20T10:00:30.000Z
node bin/alert-routing-simulator.mjs --root . --scenario examples/scenario-fail.json --at 2026-09-20T10:00:30.000Z --jsonRead the result
The first command exits 0. The failing example exits 1 with unrouted-alert. Both print one machine-readable JSON report to stdout. Without --json, a fixed human summary goes to stderr; --json suppresses that summary, not configuration diagnostics. --help displays the CLI flags without reading or writing a scenario.
Where this check stops
This is not an Alertmanager parser, notification sender, retry engine, provider adapter, recipient validator, browser driver, or auto-fixer. It does not infer missing alerts or fetch a live policy. The scenario profile is independent and intentionally small.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.