What’s new in FireHydrant


Easier Filtering for Services, Simpler Runbooks in Test Incidents, and Incident Stats in Liquid Templates

Sep 26 2022

Filtering UI Updates

  • Users can now instantly see their filters updated when filtering services in the main service catalog view. Selecting a team, tier, or connected functionality now immediately updates the list view. Keep an eye out for this pattern rolling out across the application!

Test runbook without other default runbooks attaching

  • Previously, customers had no way to test a runbook in isolation; hitting the "Test" button from a runbook would declare a new incident and specify that runbook for attachment, but any other runbooks that attach automatically would also start running for that incident. We introduced the ability to test a single runbook and only that single runbook.

Add participation statistics to template variables

  • We took our participation statistics to the next level by adding incident stats to the IncidentEntity in our liquid templates. This exposes it to both the public API and for liquid rendering in Runbook steps.

    *Incident Stats* {% assign stats = incident.participation_stats %} Total Messages: {{ stats.chat_messages }} Starred Messages: {{ stats.starred_messages }} Tasks Completed: {{ stats.tasks_completed }} Actions Taken: {{ stats.actions_taken }} {% for user in incident.participation_stats.user_stats %} *{{ }}*: * {{user.chat_messages}} messages * {{user.starred_messages}} starred messages * {{user.tasks_completed}} tasks completed * {{user.actions_taken}} actions taken * {{user.time_in_incident}} in incident {% endfor %}

These new template variables make it easy to share stats in Slack messages, emails, and even via webhooks for custom integrations.

🐛 Bug Fixes

  • Fixed an issue with incorrect system data on Status Pages
  • Fixed issue with users receiving emails after they are removed from org
Joel Smith

New Liquid Variables, Saved Views, and Coming Soon: Local Time Display

Sep 19 2022

Add common fields as top level liquid variable throughout runbooks

  • Users now have access to ticket, number, severity, and priority, and some other fields at the top level. Prior to this change those fields were nested and required users to dig through the incident's data in Runbooks. This means instead of typing {{ incident.incident_tickets.first.attachments.first.display_text }} the field is available as {{ incident.ticket }} for example.

Local time display to launch 22 Sep 2022

  • Many of you have expressed a preference for displaying times in your local timezone to prevent having to mentally convert to UTC. In response, on Thursday 22 September at 7:30am Pacific Time, FireHydrant will be changing the default timezone display to match a user’s machine time. This will not impact how datetime stamps are stored, which will remain in UTC. Enterprise customer organizations who prefer to remain on UTC should reach out to their CSMs to opt out.

Saved Views for Service Catalog

  • Users now have the ability to save views based on filter conditions for their Service Catalog Overview. This allows for users to efficiently view and get to the services they care about most with one click. We have also introduced multi-select filtering capabilities and the ability to filter based on Functionalities and Responding Teams.

Auto-Add Responding Team to Incident Channel - Beta As part of this beta, any time a Service or Functionality is added to an incident, we will automatically add the Responding Team Members to the slack Incident Channel if members have slack enabled. To be added to the beta program, reach out to your CSM for access.

Joel Smith

Brand new Services & Functionalities Import Flow and @-Mentions in Runbooks Steps

Sep 12 2022

Improved Service & Functionalities Import Flow

  • We built a more seamless experience to showcase all integrations that allow imports, explicit prerequisites on how to get started, and better selection capabilities. Now when you setup an integration and start the import process, you have the ability to quickly import all third party services as new FireHydrant services in one click. Additionally, this will automatically link FireHydrant services to those third party services on import. To get started visit the Services page, click ,Add Service, and select Import from third party.

Ability to mention users in Runbook steps

  • Now, you can manually @ users or use the field slack_user_id as liquid code while configuring a Runbook step. For example, using Hi, @slack_handle in a Runstep that posts to a custom message to a Slack channel would behave similar to if a user had directly posted to Slack. Another example would be to run Hi, <@{{incident.role_assignments.first.user.slack_user_id}}> to auto populate the handle with the user of the first role assignment.
Joel Smith