Previously, FireHydrant supported video collaboration tool integrations for Zoom and Google Meet. In response to customer asks, today we are pleased to introduce our new Cisco Webex Meetings integration for all paid plans. With the new integration, teams can automate Webex bridge creation as part of incident response.

With the Cloud Bridge introduction, I started reaching out to our customer base to make sure people are aware of what this feature can do, Usually, I try to keep our customers up to date through blogs or the occasional webinar but with the Cloud Bridge, I went for a more personal approach. Reaching out to our customers individually, presented a unique opportunity to educate them on our Cloud Bridge and by extension what SIGNL4 can bring to the table.

Responding to and managing incidents feels fairly straightforward when you’re in a small team. As your team grows, it becomes harder to figure out the ownership of your services, especially during critical times. In those moments, you need everyone to know exactly what their role is in order to recover fast. Moving to incident.io as the 7th engineer, from a scaleup of around 70 engineers, has given me a new perspective on what it means to own your code.

Not all status updates are published because of an incident or scheduled maintenance event. Sometimes, IT teams simply want to cast an informational status update without affecting the overall status.

What happens when the tools and services you depend on to drive Site Reliability Engineering turn out to be susceptible to reliability failures of their own? That’s the question that teams at about 400 businesses have presumably had to ask themselves this month in the wake of a major outage in Atlassian Cloud.