Automatically Create Incidents from Alerts with Alert Routing

Shouldn’t your alerts be doing more of the work for you? A noisy channel with every alert from hundreds of monitors and microservices is a chaotic place to actually find the incidents that are impacting your customers. And it still requires a heck of a lot of human intervention. We think it’s time for something better.

Today we’re releasing Alert Routing: the next phase of worry-free automation from FireHydrant. Just like Runbooks quell incident process anxiety through automation, Alert Routing transforms how your team works with alerts, allowing you to automatically declare incidents from high severity alerts and routing others to the places your team needs them. 

Put Alert Routing to Work

With Alert Routing, you can not only automatically declare incidents from your highest severity alerts, but you can also push team-specific alerts to your teams’ channels, create a log message in FireHydrant or simply ignore an alert. You and your team can leverage powerful conditional logic based on the data from your alerts to automate the routing of any alert from your system. 

Do you know that certain alerts mean that your customers are impacted? You can automatically open an incident, pulling in the right team based on your service catalog. Do you have specific escalation policies or infrastructure tied to Slack channels? Use an alert routing rule to send them to the right place. Do you know that a whole class of alerts don’t matter? Ignore them or log a message in FireHydrant.

Alert Routing is available today as part of your already-installed integrations with PagerDuty, OpsGenie, and VictorOps. Stay tuned for some exciting updates about new integrations that will take advantage of all the configurable power of Alert Routes.

Get started today by configuring new Alert Routes in the Integration page of your alerting provider in FireHydrant. You can also check out our documentation on using alert routes.