If you’re just starting out in the world of incident response, then you’ve probably come across the phrase “post-mortem” at least once or twice. And if you’re a seasoned incident responder, the phrase probably invokes mixed feelings. Just to clarify, here, we’re talking about post-mortem documents, not meetings. It’s a distinction we have to make since lots of teams use the phrase to refer to the meeting they have after an incident.

Observability and security are converging, benefiting dev and security teams. Runtime observability is the missing component to this important endeavor, providing much-needed data and insights to DevSecOps and AppSec teams.

Success in the cloud continues to be elusive for many organizations. A recent Forbes article describes how financial services firms are struggling to succeed in the cloud, citing Accenture Research that found that only 40% of banks and less than half of insurers fully achieved their expected outcomes from migrating to cloud. Similarly, a 2022 KPMG Technology Survey found that 67% of organizations said they had failed to receive a return on investment in the cloud.

We recently covered some of the complex decisions and architecture behind Cycle’s brand new interface. In this final installment, we’ll peer into our crystal ball and glimpse into the future of the Cycle portal. Cycle already is a production-ready DevOps platform capable of running even the most demanding websites and applications. But, that doesn’t mean we can’t make the platform even more functional, and make DevOps even simpler to manage.

In this blog, we will walk you through the basics of getting Netdata, Prometheus and Grafana all working together and monitoring your application servers. This article will be using docker on your local workstation. We will be working with docker in an ad-hoc way, launching containers that run /bin/bash and attaching a TTY to them. We use docker here in a purely academic fashion and do not condone running Netdata in a container.