Operations | Monitoring | ITSM | DevOps | Cloud

In the first part of this blog journey (I’d call it a post, but it’s actually two posts) we explored what operational excellence looks like in public cloud deployments. And while I do not want to spoil it for you, the main takeaway was that it is not easy and can become resource-intensive. With this in mind, you might should be wondering what you can do to achieve excellence without focusing all your resources on operations.

Whenever a new customer joins incident.io, we make notes on what made them chose to buy our product and, if we were in a competitive process, why they chose us over other providers they were evaluating. It’s a lot of messy data and raw notes, but contained within is a veritable treasure trove of customer feedback. Summarising large amounts of data? Sounds like the perfect job for an LLM.

Businesses are constantly on the lookout for ways to optimize operations, reduce costs, and stay ahead of the competition. One of the most effective strategies for achieving these goals is adopting open-source software (OSS). Open-source tools offer a myriad of benefits, from cost savings to enhanced flexibility and innovation. However, transitioning to an open-source environment can be daunting without a clear roadmap.

Building a standardized open-source resource across instrumentation, query, and alerting pipelines to start your monitoring journey with Prometheus.

Containerization has deeply changed the way applications are built, deployed, and managed. Containers include both an application and its dependencies, enabling consistent and efficient deployment across diverse environments. However, as applications scale and become more complex, managing numerous containers manually becomes increasingly challenging. Container orchestration streamlines the deployment, scaling, and management of containerized applications.

There’s a reason why observability and incident response practices have become standard across modern software development. Anyone wanting to minimize downtime and deliver reliable, available applications needs to have fully instrumented systems and playbooks so they can respond quickly and effectively to outages or incidents. But there’s another piece to the reliability puzzle: resilience testing.