Some critical events may be familiar to organizations, they may happen repeatedly or even on a set schedule. Others may present new challenges that responders haven’t seen or experienced before. In a worst-case scenario, events could even happen concurrently, forcing responders to split their attention while trying to anticipate and account for the combined effects.

To protect the availability of the services your customers rely on, AIOps adoption is an imperative for large enterprises. Interlink Software’s AIOps platform applies machine learning to automate ITOps; reducing alert noise, performing event correlation, anomaly detection and root cause determination. As the world emerges from the Covid-19 pandemic, organizations are increasingly embracing the flexibility of home and hybrid working.

We are well into 2022 and are busy bringing new exciting features to market. Our customers continue to provide input into our product roadmap and many new features are based on this collaborative effort. A big thank you to our valued customers. Throughout the year we will continue to drive innovation and allow our customers, of all sizes, to implement the most advanced AIOps solution in the shortest time possible.

We've launched a feature that will help you fix errors and performance issues as a team! 🎉 With Logbook you get the full incident history. Read and leave team comments, see which notifications were sent at what time, and see team activity for changes in incident states. It's now easier than ever to see what the current state of an incident is.

When FireHydrant originally launched our Jira Cloud and Jira Server integrations, we did not support custom fields. This prevented customers who rely on Jira epic ticket types or other custom required fields from getting full value from our Jira integrations. That has changed with the launch of Jira custom field support. We now support the most common type of Jira epic tickets and field-level mapping of Jira custom fields with FireHydrant incident data.

When an incident happens, most organizations have a way of identifying all affected services. The trouble is, it’s often a human-centered process that depends on the knowledge of key individuals or manually updated documentation. There might be a version in your alerting tool, a version in your corporate Wiki, and a different version still in your team’s head.

When it comes to learning from incidents, your tools should adapt to the way your organization works. Many of you conduct your retrospectives in rich-text document editing tools, like Google Docs. That’s why we’ve introduced the option to export your retrospectives to Google Docs. Retrospective export to Google Docs can be automated as part of your incident management process with a Runbook step.

All companies are going through some form of cloud adoption - whether cloud migration for the first time, hybrid cloud adoption, or extending cloud-native with newer microservice architecture. But, according to a recent survey by Aptum*, only 39% of companies are completely satisfied with their current rate of digital transformation. Cloud adoption projects create a continuous state of change for engineering teams juggling to keep things up and running while limiting the impact on customers.

We’re building incident.io as the single place you turn to when things go wrong. When an issue is disrupting your business-as-usual, the last thing you want is to start opening ten different tools to diagnose and fix it! As your central incident hub, we need to give you two powers: Workflows cover the former. Workflows are like a mini incident.io Zapier.

With the rising complexity of our digital ecosystems, incidents are occurring at an unprecedented rate. To combat the additional strain, incident responders are looking to software to help them establish a scalable, repeatable incident response process that reduces toil and noise and gets the right people on the scene at the right time. The best incident response software addresses the entire lifecycle of an incident.

BigPanda’s recent coronation as a Unicorn has prompted its leaders to look to the future of IT Operations and how it relates to artificial intelligence (AI) and machine lifiearning (ML). What is BigPanda’s role in improving IT Ops? How can AIOps contribute to greater achievement in global enterprises? These are questions a VP of Product Marketing like BigPanda’s Mohan Kompella, who has spent 15+ years in IT Operations, has been asking.

At incident.io, we pride ourselves on providing a great product to our customers. We’re also a small team, so we move fast and (whisper it not) occasionally break things. To mitigate the impact on our customers, we have our app set up so that every time our application raises an error (via Sentry), we get paged.

BigPanda offers a diverse set of APIs to enterprises looking to move faster and scale incident response workflows seamlessly. APIs are core to automating repeated incident response workflows that enable IT Ops to keep up with the pace of change and innovation agile teams need to thrive. In Q4 of 2021, BigPanda announced the general availability of new self-service APIs including an updated Incidents API.

Effective major incident management depends on many things, including planning, precise execution, effective communication, and applying learnings from previous incidents to update those plans. Traditional major incident management wisdom addresses the importance of the remediation process, but it doesn’t speak on the issue of configuring your IT infrastructure.

For this episode we’re continuing to “Build Things on Purpose” with JJ Tang, co-founder of Rootly, who joins us to talk about incident response, the tool he’s built, and his many lessons learned from incidents. Rootly is aiming to automate some of the more tedious work around incidents, and keeping that consistency. JJ chats about why he and his co-founder built Rootly, and the problems they’re trying to fix and eliminate when it comes to reliability.

Forget the latest tech gadgets and the newest products. One of the most talked about trends in observability right now? “SLOs have really become a buzzword, and everyone wants them,” said Grafana Labs principal software engineer Björn “Beorn” Rabenstein on a recent episode of “Grafana’s Big Tent,” our new podcast about people, community, tech, and tools around observability.

Your IT team just finished resolving a complex incident, customer service finished their last call about the issue, and your business is back to being fully operational. Now that the storm has passed, you should be planning a postmortem to determine the cause of the incident and lessons learned. Postmortems require specific data that can highlight where your team is succeeding and where they can improve.

As the Regional VP of Customer Success for the West and Central Region at BigPanda, Chris LaPierre gets a unique opportunity to see first-hand how BigPanda customers use their AIOps platform. Charged with ensuring every BigPanda customer derives high value and return on investment from the solution, BigPanda’s customer success teams make certain customers leverage the AIOps platform to increase their bottom line.

By now it’s no secret that system outages and website downtime are more widespread and frequent than ever. In fact, the frequency of outages jumped 9% in just the first week of 2022. This can be attributed to a rapid increase in traffic and reliance on tech infrastructures – resulting in connectivity, server, and other technical issues that are alternately unforeseen and unavoidable.

Modern DevOps teams that run dynamic, ephemeral environments (e.g., serverless) often struggle to keep up with the ever-increasing volume of logs, making it even more difficult to ensure that engineers can effectively troubleshoot incidents. During an incident, the trial-and-error process of finding and confirming which logs are relevant to your investigation can be time consuming and laborious. This results in employee frustration, degraded performance for customers, and lost revenue.

FireHydrant captures your incident, from declaration through remediation, and gives you a framework to run your retrospectives. But retrospectives are only as effective as their inputs. Now we're delivering a better way to learn from and analyze retrospectives by guaranteeing consistent, structured, and sufficient data from your team.

Being on call is challenging. It’s signing up to be operating complex services in a totally interruptible manner, at all hours of the day or night, with limited context. It’s therefore critical to have proper on-call on-boarding procedures, offer continuous training sessions, and continuously improve documentation. We also need to make sure people feel safe by providing ways to reduce their stress, and make room for questions to surface all sorts of uncertainties around our operations.

To embed or not to embed: That is the question. At least, that’s one of the questions that companies have to answer as they decide how to implement Site Reliability Engineering. They can either embed SREs into existing teams, or they can build a new, separate SRE team. Both approaches have their pros and cons. The right strategy for your company or team depends, of course, on your needs and priorities.

Worldwide businesses and their technical resources use G2, the leading business solution review platform, to analyze software, gather user feedback, and make informed decisions about technology. Although we value all the recognition we’ve earned on G2 over the years, there’s one that always stands out and makes us feel extra proud of what we’ve accomplished so far.

Shoreline is an incident response automation service that enables DevOps engineers and site reliability engineers (SREs) to quickly debug and remediate issues at scale and develop automated routines for incident management. Using Shoreline’s proprietary Op language, customers can run debug commands across all their hosts simultaneously and then deploy custom scripts via Actions to trigger automated remediations.

Welcome to our final post in our EI Architecture Series on Intelligent Alert Grouping. I hope you’ve enjoyed this series, and if you’d like to take a look at any of our prior posts, please use the ei-architecture-series tag. Let’s take a moment and recap everything we’ve learned.

Episode 4, Mooving to… Successful Engineering in the Remote World offers a unique perspective on work-life balance and expectations.

Here at incident.io, we provide a Slack-based incident response tool. The product is powered by a monolithic Go backend service, serving an API that powers Slack interactions, serves an API for our web dashboard, and runs background jobs that help run our customers incidents. Incidents are high-stakes, and we want to know when something has gone wrong. One of the tools we use is Sentry, which is where our Go backend send its errors.

The cloud is easy and powerful—until it’s not. Once companies have customers, commitments, and compliance concerns, they often have to create cloud operations teams to manage the cloud on behalf of their fellow employees. Often, organizations that migrate to the cloud find themselves hampered by inefficient cloud operations if they haven’t standardized their IT procedures for operability.

During major incidents, it’s crucial that all stakeholders are provided with the status updates they need. Those communications however need to be tailored to what the stakeholder actually needs, and provided in a streamlined format that works best for them. Just like alert fatigue, communication fatigue can be detrimental during an outage or other service reliability issue.

The effects of BigPanda’s most recent round of funding—amounting to $190 million—will be reverberating throughout the company for years to come. And it’s not just BigPanda employees who have experienced a surge of enthusiasm in the wake of our Unicorn status. Our customers are thrilled at the prospect of more innovation from our team and new products that help them automate and evolve.

When incidents inevitably occur in your software stack, managing them well could be the difference between losing customers and building trust with them. In this article, we’ll give you and your team some best practices on how to prepare for managing incidents. It’s crucial to define service ownership, a declaration process, and practice all of it. With a little planning now, you'll be able to cut your incident response time drastically.

With our April update, we ship some great improvements for Signl categories, category-based alerting and duty scheduling. All details are available in this blog article.

Let’s face it. Incidents can be expensive—really expensive. But the high cost of incidents within a production environment isn’t always due to a compromised service or negative customer experience.