LoginSign Up
← Back to all sparks
F

FireHydrant

INFRA · APIS
Velocity0.0

Incident response and reliability platform with on-call and status pages

firehydrant.com ↗

FireHydrant stops paging people at night for alerts that can wait until morning.

on-callalert-fatiguesupport-hoursincident-responseopsgenie-migration
◆Current state
Support hours now do something during off-hours. Alerts arriving outside a team's window and at or below a new Off-hours Priority Threshold are snoozed, then re-enter the escalation policy from the top when the next window opens. Higher-priority alerts still notify immediately, and a Slack, Teams or webhook destination can report what is queued. The change is opt-in per team until January 2027, when remaining teams are moved over.
◆Where it's heading
The year's table-stakes work for switchers is giving way to on-call quality of life. Schedule overrides made changes safe, and snoozing now reduces unnecessary pages, with visibility built in through a Snoozed filter and alert timelines. The January date makes this the default for everyone, and FireHydrant says it waited until after the holidays so the change does not land in customers' busiest weeks.
◆Prediction
Expect guidance and prompts pushing teams to set thresholds before the January 2027 switch. API and Terraform coverage for these settings is plausible, but the entry does not mention it.

◆Recent moves

  1. 1mo ago

    Support Hours Now Snoozes Alerts

    Support hours move from a label to real routing, snoozing low-priority off-hours alerts until the next window. After overrides, it is the second on-call change aimed at everyday trust rather than migration.

    View source ↗
  2. 2mo ago

    Introducing: Preserved OnCall Schedule Overrides

    Overrides now survive schedule edits and take precedence over generated shifts, with stacking, an explicit Gap type, and cancellation that restores the original shift. Because reassignment and coverage requests now route through overrides too, schedule changes became reversible rather than destructive. Rotations not regenerated since 24 July 2026 need a one-time regeneration before any of it applies, and pre-existing overrides do not carry over.

    View source ↗
  3. 4mo ago

    ICYMI: The New In-App Signals Migrator

    ⚡ SPARK

    The Signals Migrator is the sharpest statement of FireHydrant's current strategy: import teams, schedules, escalation policies, and support hours out of PagerDuty or Opsgenie into a staged state you review before activation, while the existing setup keeps running. The scheduling work since then, overrides included, is about making the product teams land in trustworthy.

    View source ↗
  4. 4mo ago

    A Better View of Your Team, Right From the Start

    A clearer team on-call view from the first screen, part of the same effort to make the product legible to teams arriving from an incumbent tool.

    View source ↗
  5. 5mo ago

    May Recap: Deeper Analytics, Smarter On-Call Filters & More

    The monthly recap format: deeper analytics and smarter on-call filters, incremental work spread across several surfaces rather than one headline change.

    View source ↗
  6. 6mo ago

    April Recap: EU Instance, MS Teams Scribe, and more!

    An EU instance and an MS Teams Scribe, removing two of the most common blockers — data residency and chat platform — for prospective switchers.

    View source ↗