Operations | Monitoring | ITSM | DevOps | Cloud

Back in my mid to late 20s, my most prized possession was my Yamaha R1 motorcycle. Living and working in the city of Milwaukee meant I didn’t need to worry about finding parking, gas was cheap, and it was fast, one of the fastest sport bikes on the market at the time. But with that speed and power comes great responsibility, and I took that responsibility seriously. If I was going to go out and meet friends, I promised myself, not one sip of alcohol.

IT service management (ITSM) is a critical corporate capability, but what are the key ITSM trends to watch out for in 2023? Thanks to the general evolution of technology-enabled businesses and the digital transformation acceleration caused by the global pandemic, the suitability of your organization’s current ITSM capabilities needs to be questioned – especially in light of the ten ITSM trends we’re about to share. We consulted ten IT leaders to reflect on the road ahead.

Bitbucket or GitHub? These hosting platforms are popular because they offer software development teams the ability to create, manage, track, and review code repositories. They are essential tools for developers in various industries and can be used for numerous applications and projects. So, if your team is growing out of local repositories, then it may be time to level up to a more robust coding repository platform.

Over the last few years, many customers have asked us to update our current public dashboards with new features so they can more effectively communicate what is happening with their checks to external customers or internal users. We’ve taken that input to heart, and we’re pleased to announce the availability of redesigned dashboards for Checkly.

Bugs can remain dormant in a system for a long time, until they suddenly manifest themselves in weird and unexpected ways. The deeper in the stack they are, the more surprising they tend to be. One such bug reared its head within our columnar datastore in May this year, but had been present for more than two years before detection.

When we look at the calls our help desk receives, we see many of the same issues repeatedly. Some of the most common calls help desk agents receive involve issues like password resets, new hardware requests, and generating standard reports. And when we examine our IT environments as a whole over the last decade or so, there has been a huge emphasis on automation. Why? We have learned that automation reduces risk, streamlines workflows, and makes everyone more productive.

As Grafana has grown from a visualization platform to an observability solution, we’ve added many tools along the way. These tools are dedicated to help you throughout the software development life cycle, whether you are trying to prevent incidents, you are monitoring your application or infrastructure, or if you are in the middle of an incident.

When you’re facing a cyberattack, waiting even just minutes to respond could be the difference between business as usual and a calamity. It may only take that long for threat actors to exfiltrate sensitive data or disrupt critical systems. That’s one reason why automating remediation is an essential ingredient in an effective cybersecurity strategy.

Observability is the ability to see and understand the internal state of a system from its external outputs. Logs, Metrics, and Traces, collectively called observability data, are external outputs widely considered to be three pillars of observability.

In this post, we’ll dig into the difference between a bug and an incident, why alignment on how they are defined matters, and how to ensure you’re still learning from the issue, even if it’s “just a bug.”