Low MTTR is the much-desired nirvana-state in IT Operations. One of the most painful parts of the incident management lifecycle, which prevents the achievement of this nirvana, is triage: the time it takes first incident responders to determine the next action when facing a barrage of IT incidents. Why?

In one of our recent webinars we discussed a substantial challenge IT Ops teams face in today’s complex IT environments: defining and clearly communicating incident/operational roles and processes, in an effort to create a well-coordinated incident management lifecycle. This lifecycle is essential for restoring service as quickly as possible when disruptions occur. Following are the highlights of that discussion, also recently published in an ApmDigest article.

There are many hidden costs in running sub-optimal IT operations, that most organizations don’t consider. Enterprises often look at service downtime as their only KPI, but that is really only the tip of the iceberg. Without a properly operating incident management lifecycle, enterprises tend to support poorly performing services instead of fixing them.

In one of our recent webinars we discussed a challenge in digital transformation that is top of mind for many IT Ops leaders: how to actually transform with the least amount of pain… No matter how tired people are of the term “digital transformation”, it still represents an imperative strategy for enterprises wishing to survive in today’s dynamic business environment, let alone see growth and increased market value.

Does the following sound familiar? You have a complex, hybrid and dynamic IT stack – with your cloud infrastructure changing by the minute and your container infrastructure changing by the second. Your monitoring and observability tools provide excellent visibility into your infrastructure, your applications and your services, but the dynamic environment in which they operate causes them to generate large volumes of heterogeneous machine data, with thousands of alerts a minute.

It’s on the agenda of almost every CIO, COO and CFO, and sounds like a great idea in general: tool rationalization, often trying to standardize on top of a single vendor. It can reduce costs and provide a streamlined IT Ops process through data consistency, a single pane of glass and a single source of action.

2020 is (finally) over, and it’s safe to say that this very challenging year taught us once again that (as the old Danish proverb says) it’s difficult making predictions, especially about the future. Who would have imagined in January 2020 that we would find ourselves where we are today… And yet, as Tim Harford once wrote in the Financial Times, predictions are like Pringles: nobody thinks that there’s any great virtue in them but we find them hard to resist.

Solarwinds is a 21-year old publicly traded monitoring and network management vendor with 300,000+ customers across the world. It’s familiar to IT operations and monitoring teams across enterprises big and small. And this week, it found itself in the news for all the wrong reasons.

In 2020, enterprises have meaningfully accelerated their digital transformation. The global financial advisory firm KPMG, notes that “For a majority of U.S. CEOs, the pandemic has meant an acceleration in digital transformation by months or even years. The move to digitization has accelerated, and the benefits will be permanent. There is no going back.” Software vendors are seeing this very clearly too.

Most enterprises today are in the stages of a hybrid cloud migration, and no matter how they view this migration or implement it, the challenges they face are fairly common across the board. Does that mean there are common best practices for a hybrid cloud migration, and if so – what are they? Join us in a CTO Perspective discussion with Scott Stradley, Field CTO at BigPanda. Lean back and watch the interview, or if you prefer reading, take a few minutes to read the transcript.