You're not missing anything: Edge Rules don't have a dedicated log or metrics view that shows which rule matched a request.

Requests that a rule blocks, redirects, or challenges still show up in your service's HTTP logs (in the dashboard or via railway logs --http) with their status code, path, host, and timing, but those entries don't say which rule handled them. Block rules let you choose any status from 400 through 499, so giving a rule its own status code makes its hits easy to filter in the HTTP logs, for example with railway logs --http --status 429.