Operations | Monitoring | ITSM | DevOps | Cloud

Inflation is running rampant, the world stage is unpredictable, and what’s happening in the U.S. markets has been dubbed the “tech wreck.” A common theme I’m hearing come up in conversations across industries right now is value — we’re all looking to maximize every dollar spent, every hire made, every hour logged. For a lot of companies, this means looking at processes and tools with a critical eye for not only cost savings but also cost avoidance.

Incident management is a practice that seeks to resolve business-impacting events in the most efficient manner possible. But not every problem that arises requires an incident response, and it’s crucial that teams know the difference between a problem and an incident. Responding to problems may be part of daily routines, or small ad hoc projects that don’t require more than one resource or a significant time commitment.

Welcome to a special Monthly Moo - Product Edition. We have so much to share that we needed to create a special edition of the Monthly Moo to cover all the latest features that are now available. And to see these in action, sign up for our webinar that's coming on Tuesday. More details below. With many new features recently rolled out we need to group them in logical order to cover each of the following categories.

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.

Chicago, IL – May 17, 2022 AlertOps, a major incident response management platform, announced today a new technology integration partnership with Cisco AppDynamics, the leading Application Performance Monitoring (APM) and full-stack, business-centric observability solution. This new relationship empowers AlertOps and AppDynamics, joint users, with intelligent alerting, escalation policies, workflows, and scheduling to rapidly remediate major incidents.

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.