Mobile Onboarding and DataDog Event Source changes

Mobile Onboarding

We're thrilled to introduce our new step-by-step onboarding process for both iOS and Android apps. This user-friendly guide helps you unlock the full potential of FireHydrant right from the start. As a new user, you'll be guided through setting up essential features, including:

• Enabling notifications to stay in the loop
• Activating critical alerts for timely updates
• Adding FireHydrant as a contact for seamless communication

We're excited for you to experience the full capabilities of FireHydrant on your mobile device!

DataDog Event Source Changes

Starting August 12, 2024, we will treat any payload from DataDog as having an OPEN status, except for those marked as "Resolved."

Currently, we ignore payloads unless the status is Triggered or Resolved. This means that Warn/Re-Warn webhooks from DataDog are ignored by FireHydrant.

What we're changing

We will begin treating Warn/Re-Warn the same as Triggered.

Why we're changing it

This change is to align with the rest of our product behavior: any payload coming to FireHydrant is associated to either OPEN or CLOSE  alert.

What you need to do

If you would like for FireHydrant to only listen on "Triggered", please update your DataDog monitor to be explicit on when DataDog will send a payload to us:

{#is_alert} @webhook-FireHydrant-Signals {/is_alert}
{#is_recovery} @webhook-FireHydrant-Signals {/is_recovery}

Other Improvements and Bug Fixes

• 💅 Android app maximum volume reduced from 100 to 75
• 💅 Microsoft Teams now displays milestones in notification cards
• 💅 Assigned teams is now available in CSV export
• 💅 Added a runbook condition for re-running steps whenever a status update is made
• 💅 Added the ability to disable announcing new incidents back to the channel when created via /fh new in Slack
• 🐛 We no longer announce private incidents in their originating channels
• 🐛 Fixed an issue where saving content on the Lessons Learned tab would sometimes return stale data.
• 🐛 We fixed an issue that may have caused us not to cache Slack channels properly in Enterprise Grid
• 🐛 Fixed a UI bug that prevented related services from being associated to a functionality in our Catalog
• 🐛We added back the ability to unsubscribe from weekly summary emails for non-Signals users