Today’s post is an excerpt from “5 Steps to Improve Security and Incident Response in AWS”, which was co-authored by OpsGenie and Evident.io, a Palo Alto Company. You can download the complete white paper here.
As part of the series promoting our newest White Paper: Creating Actionable Alerts to Maximize Resolution Speed, we’d like to introduce another automated task that can be implemented during alert enrichment. Check out our previous post Creating Actionable Alerts Series #1: Gathering Investigative Information to learn more about our first alert enrichment automation practice.
Creating Actionable Alerts is a continuous process that can enhance your workflows so that not only are the correct people notified at the right time, but they can take immediate action to reduce potential business-impact. This post is the first in a three-part series about alert enrichment. Without actionable alerts, your responders may be alerted to an issue, but cannot necessarily take immediate action, which has the potential to increase downtime and slow down the remediation process. Actionable alerts set your responders up for success from the start of an Incident, and empowers them to immediately start repairing damaged services. There are many ways to create Actionable Alerts, so as an introduction to our newest White Paper, Creating Actionable Alerts to Maximize Resolution Speed, we want to share our first method.
One of the most impressive books on DevOps, “The DevOps Handbook”, emphasis three fundamental principles underpinning DevOps: systems thinking, amplify feedback loops, and continual experimentation & learning.
Amplifying feedback loops is described as creating the right to left feedback loops, which helps corrections to be made continually, by Gene Kim in his blog post. But, let’s start with why we should do this in the first place.
Over the last few years, teams have realized the benefits of sharing and distributing knowledge in chat applications such as Slack. Today, teams are extending the use of these applications beyond collaboration by embracing ChatOps. ChatOps empowers teams by bringing complex day-to-day operational work into shared chat channels. If done correctly, it drastically reduces context switching and increases the speed at which teams can tackle tough challenges.
We love Slack like you do because it is where we get things done at work. Slack applications are the gateway for our favorite tools like Intercom, Jira, Google Drive and many more. There are also ChatOps tools like OpsGenie’s Slack application focusing on improving collaboration and automation by bringing day to day to operational challenges into shared chat channels.
DevOps is not just about developers and operations people working together or creating a culture of collaboration. It is about tightening the feedback flow. It is about working for the common good of your systems and applications. It is about learning from mistakes. These are all enabled by people and the tools that people use. Continuous delivery is a key enabler for DevOps because it helps you deploy and release your code with confidence.
StatusCake is a website uptime and performance monitoring solution. You can gain invaluable insights into your website's performance and get alerted when things aren’t right. StatusCake is capable of sending email or SMS notifications. These are great.
Speed of execution is the greatest strength of the agile companies. When we look at the Agile and DevOps mindset, we can see that the sole purpose of all these movements is to make things faster without sacrificing quality.