Skip to content

Migrate from OpsGenie to Spike and never miss a critical alert.Get 20% off your first year 

← All emails

No. 7 · May 21, 2026 · Routing

Let routing rules handle the obvious

So your team can focus on what actually isn't

When an incident triggers, someone on your team decides what happens next.

They change the severity. They reassign it to the right team. And that works.

But for some incidents, it is the same decision every time.

So the question is: why make it manually?

If your team keeps making the same call for the same kind of incident, that call should probably live in an alert routing rule.

Then the system instantly changes the severity and reassigns the incident, instead of waiting for someone to spot the pattern again.

Our guide walks through four sources, where you can find these patterns and turn them into routing rules.

See all 4 sources →

Get the next one in your inbox

A weekly email for engineers who carry the pager.

Enter to open, arrows to move, Esc to close

Browse everything on spike.sh