Operations | Monitoring | ITSM | DevOps | Cloud

After many weeks of work, we're delighted to announce the latest feature of the incident.io platform: Workflows. Configure your processes once, and we'll make sure you follow them, every time ✨ A little while ago, I was asked the question: “what makes a good incident response?”. Whilst there’s infinite nuance in the answer, mine was pretty straightforward. The best incidents are founded on principles of communication, coordination, and clear roles and responsibilities.

Systems and platforms continue to grow more complex and distributed. The march towards distributed microservices has been accelerated with Kubernetes; arm yourself with a Kubernetes manifest and up your replica count and like magic, you have more than one endpoint for your workload. In the Kubernetes ecosystem, there has been a lot of investment on the infrastructure side of the house for example in making sure clusters are performant and have the ability to scale.

Technology is one of the main success factors for any organisation. A few decades ago, when technology (and life) were not as fast-paced as today, IT was more about keeping the lights on and maintaining business as usual operations. Today, the game has massively changed. On the roads that are ever-changing, innovation is what keeps the wheel spinning. If you think that the world is doing enough innovation today, then it would be very interesting to check the recent Growth & Innovation McKinsey report.

How many times have you been aware of an error or performance issue, but lacked the ability to quickly uncover the root cause and determine why it happened in the first place? One of the most powerful ways to do this is by surfacing code-level insights right where you need them, alongside the context needed to take action. By using our latest integration with Azure Repos, you’ll be able to get to the ‘why’ of issues, faster – all directly within Raygun.

Netdata excels in collecting, storing, and organizing metrics in out-of-the-box dashboards for powerful troubleshooting. We are now doubling down on this by transforming data into even more effective visualizations, helping you make the most sense out of all your metrics for increased observability. The new Netdata Charts provide a ton of useful information and we invite you to further explore our new charts from a design and development perspective.

With all the focus on public cloud infrastructures, it’s easy to believe that there is no room for on-premises deployments of infrastructure. However, on-prem deployments are not likely to completely go away because often it’s just the right thing to do.

SaaS is exploding and so it should; it takes commoditized work and infrastructure away from tech teams so that they can focus on differentiating features. But what happens when it goes wrong? How do SaaS platforms make sure they aren't letting their customers down and in turn, letting their customers down? Observability, bolstered with AI gives all the partners the best chance to optimize availability and customer experience. Here's how.

As Kubernetes becomes the key target environment across many organizations, it automatically becomes an essential topic for developers. However, Kubernetes was created for operations and, unless you spend a considerable amount of time learning and specializing yourself, it is still challenging to use. Developers should rather focus on delivering applications instead, and a developer or application-focused platform is needed to enable that.