Over the last few quarters a couple of interesting patterns have emerged amongst our larger customers who are looking to catalyze cross-team collaboration during a major incident spanning members from multiple teams.
“Well, that’s the job.” Have you ever heard that from your colleagues or bosses when it came to being on-call? Imagine you started a new job 3 months ago and were looking forward to it from the start. You are on-call one weekend a month and thought there wouldn’t be many incidents from Friday evening to Monday morning. But by now you’ve noticed how much being on-call duty actually stresses you out. You get restless as soon as your shift starts.
Companies moving their applications and services to the cloud is nothing new, but doing business there requires a solid cloud migration strategy. The list of things to consider is longer than you might think. Fortunately, xMatters has done it successfully and has helped its own customers move to the cloud too. In this article, Product Marketing Manager Erin Jones gives a checklist you can use to get your cloud migration right.
Companies go to extreme lengths to provide their customers the best possible experience—and every company’s concept of what makes a good experience is different. In our RESOLVE ’22 panel Customer experience in action we sat down with Translation.com Director of Strategic Initiatives Sridevi Matukumalli and Akamai Senior Director Harish Menon to talk about this notion.
This post highlights some of the features and improvements that we have released in the last 3 months. If you want to submit your own ideas or vote on existing feature requests, you can now use our new public roadmap at roadmap.ilert.com.
In our first session from RESOLVE ‘22, we were honored to have Darren Boyd and Satbir Sran from the Incubator podcast and ink8r think tank talk observability and AIOps with BigPanda’s Aaron Johnson. Both panelists are part of communities adopting open standards, and they regularly consult with organizations about how they can improve IT Operations and overall performance.
The why and what we learned from surveying 1,900 engineering teams around their best practices to build, scale, and maintain high availability.
Incident management is easily one of the most annoying things anyone has to ever deal with. There will always be only a handful of people who would ever want to walk into the building on fire to mitigate. That’s the same with most engineering teams. Only a handful are willing to get in, find the root cause, and mitigate the incident.
With distributed IT Operations becoming the norm, most enterprise teams struggle with communication and collaboration within and across the organization. Without the proper tools, staying on top of incidents can be challenging, quickly resulting in outages taking longer to resolve. The overall effect: increase in downtime-related costs and decrease in performance and availability of services making mean time to resolve (MTTR) worse.
Over the last couple of years, Spike.sh has largely been a Simple Incident Management Platform helping engineering teams across the world. Our focus on simplicity has been well received by all of you and we couldn't be more happy about it. After speaking with users earlier this year, we quickly realised there is a lot we can do to help our responders and help them better than we currently are.
