Blog
When using cloud-native services, you will undoubtedly have cloud incidents that disrupt the normal operation of your systems. No SRE team believes they can achieve 100% uptime. Instead, they plan ahead, trying to anticipate what could go wrong (or has in the past) and create runbooks (sometimes called pipelines or workflows) to get things back to normal as quickly as possible.
SRE was coined by the Google engineering team, when they realized that the duties and responsibilities required had deviated significantly from traditional IT/DevOps. One of the key differences is the use of code to help solve problems within cloud-native systems and infrastructure.
I’ll start in 1811 England. There was a new invention called a loom, allowing lower skilled laborers to operate and produce lower quality products that ruined the artisans’ reputation for quality. The name Luddites was coined, and this group of people went on to physically smash looms eventually causing Parliament to make frame-breaking a hanging offense.
Gone are those chill days, when an on-call person would take hours to fix a problem and restore the service for their customers. According to Statista, more than 50% of the enterprises reported they lost $500K or more per hour due to server downtime.
If you found your way to this post, it’s likely because you’re trying to determine what the difference is between incident response and incident management. You may be a new SRE, or switched companies and things aren’t being treated in the same way.
At a high level an SRE is responsible for ensuring the systems run 24/7 and can handle scale as needed. To achieve this requires a lot of tools and expertise, not to mention often times having to “carry the pager” and handle incidents any time of the day or night.
Facebook going down isn’t surprising and we have seen mishaps in the past. Just last month we noticed a similar DNS issue with Slack. The power of BGP is well known and it’s even surprising that this outage lasted so long and how widespread it really was.
As cloud computing is increasingly getting adopted all over, automation is taking a prime stage these days in the cloud-native space to streamline and manage various IT-related tasks. In this article, we will discuss cloud automation and various aspects related in brief.
Today’s SaaS applications are constantly changing and require real-time observability. Instana is an automated Application Performance Management (APM) solution designed specifically for the challenges of managing microservices and cloud-native applications. Once you have observability, you want to act on the insights. You want to trigger a specific workflow based on what you find. In this article, you will learn how to do this by Fylamynt’s triggers built for Instana.
