Operations | Monitoring | ITSM | DevOps | Cloud

Everyone has heard about the 3 AM wakeup call, but what about those troublesome issues that dig at your team and eat away at your SLA hours? Hard-to-diagnose issues can strike at any time. They leach from your team, hurt morale, impede the customer experience… it’s just a whole mess. These kinds of incidents are ones that test what “response” really means to your organization, as fixing them is not always a simple task. Something has gone wrong.

It’s official! Gartner just published the latest Magic Quadrant for ITSM Tools and once again, we’re proud to have been named a Leader. This is no flash in the pan, but rather more validation for Ivanti’s completeness of vision and our ability to execute. At Ivanti, we’re committed to enabling the Everywhere Workplace so that teams around the globe can focus on what they do best.

Infrastructure as code and automating deployment and scale-up/down in Azure is becoming the new normal. Solution architects and system administrators are becoming coders and scripting is becoming part of their day-to-day job, whilst in parallel a raft of vendors is providing products to try and help avoid this need to script and address the shortage of staff with those skills to script and code this now necessary functionality.

On Tuesday August 31, users across large parts of the West coast (US-West-2 region) were impacted by major spikes in response time. Some of AWS’ most critical services were affected, including Lambda and Kinesis. SRE teams care about Service Level Indicators (SLIs) and Service Level Objectives (SLOs), and this practice is a must for SRE teams.

GitOps is one method used by teams to deploy microservices, but challenges usually arise when deploying applications across multiple clusters and environments. For your GitOps initiative to be successful, you should consider implementing an application operating model. In this second workshop we covered.