April 1, 2024

Signals Webhooks Beta, Teams Targeting for Event Sources, Liquid in Status Templates, and more!

Signals Webhooks in Beta

Signals Webhooks

We love that our customers are finding value in Signals and want to continue expanding on custom workflows. So we released Signals Webhooks in beta - building on our existing Webhooks functionality, FireHydrant can now send Webhooks to external destinations on any Signals/Alert action. Find the documentation here.

Liquid in Status Templates

Liquid in Status Templates

FireHydrant now supports using Liquid templating when configuring Status Templates. Templates with dynamic incident data help reduce the cognitive load for your responders so they can quickly post updates and immediately return to the issue at hand.

Dynatrace Event Source

Dynatrace Event Source

FireHydrant now supports Dynatrace as an event source for Signals alerts. You can find it in the table on the Event Sources page. Click View on the right-most column of the table to see an example payload and how FireHydrant translates it into an event.

Other Fixes and Improvements

  • πŸ’… We've officially added SMS support for India and SMS + Voice support for Poland. The numbers for each have also been added to the vCard
  • πŸ’… You can now select FireHydrant Escalation Policies as targets when using the Assign a Role Runbook step.
  • πŸ’… We now show a more helpful error message when assigning a team fails in Slack
  • πŸ’… We removed the checkbox for Internal Status Page when running /fh update from Slack, and all updates posted to the incident will always post to Internal Status Pages
  • πŸ’… We made performance improvements to the login page and reduced the time to First Contentful Paint (FCP) and Largest Contentful Paint (LCP) by 66%. We also reduced the total blocking time from 10ms to 0ms
  • πŸ’… We adjusted the responsiveness of components in our web application, particularly around the ~1300px width
  • πŸ’… FireHydrant status pages received updates to some light mode styling and timestamps now all show in the user's local timezone, showing both UTC and local times when hovered over
  • πŸ’… FireHydrant status pages also now show ongoing incidents' current milestones as well as severities and priorities at the top of the main status page
  • πŸ’… We updated the names of several Runbook steps, namely Microsoft Teams and Slack steps, to be more explicit
  • πŸ’… We now support creating private Runbooks from our Terraform provider
  • πŸ› Fixed a bug where searching and filtering wasn’t working when attempting to link external PagerDuty services to FireHydrant components in Catalog
  • πŸ› Fixed an issue where users will still seeing error messages in Jira about our legacy capability to link Jira tickets to Tasks
  • πŸ› Fixed an issue where the original authorized user couldn’t re-authorize the Jira integration
  • πŸ› Fixed an issue where only the first of multiple linked external Jira incident tickets were updated when the incident was updated
  • πŸ› Fixed an issue where users could inadvertently click β€œDeclare” multiple times in Slack when there is a connectivity issue, resulting in duplicate incidents declared
  • πŸ› Fixed unclear documentation in API docs for metrics and regenerated the Go client
  • πŸ› Fixed an issue in Slack where /fh private was still using a deprecated modal. It now is aliased to /fh restrict and both will open the same, new modal
  • πŸ› Fixed an issue/inconsistency in Slack where some users were tagged and added to the channel while others were not when assigned tasks or roles

See FireHydrant in action

See how service catalog, incident management, and incident communications come together in a live demo.

Get a demo