Major incidents are inevitable, and fixing them is the top priority for any ops or DevOps team. But what happens after service is restored? Do teams take the time to fully understand what went wrong, then follow up to prevent it happening again?
Downtime happens. That’s a fact, and it’s nearly impossible to predict. But there are some days when the chances of downtime are higher. Maybe it’s higher-than-normal website traffic, or increased app sign-ups. When planned high-traffic days are on the horizon, it’s a good idea to spend some extra time preparing for the worst.
The ITOps world is a harsh working environment where ITOps personnel are expected to minimize the business impact of incidents at all hours of the day—regardless of the impact to themselves or their families. As more companies undergo digital transformation, the number of alerts and interruptions flowing to IT first responders will continue to increase.
As you may expect from a company founded by former Amazon employees, PagerDuty has been helping AWS users automatically turn any signal into the right insight and action for years. Our Amazon CloudWatch integration enables teams to proactively mitigate customer-impacting issues, which in turn allows organizations to innovate and scale both their AWS and hybrid environments with confidence.
In the United States, it’s almost that time of year again where we count our blessings and give thanks. For retail workers, it’s also that time of year where they prepare for the onslaught of eager shoppers who waited hours in line to run into stores to get their hands on doorbuster deals (sometimes knocking down the employees in the process).
It’s an exciting time here at Opsgenie. We recently joined the Atlassian family, updated our logo, released new pricing, and now we’re headed to AWS re:Invent 2018! So much has changed since last year’s event and we can’t wait to talk about it in person.
