You've just made it through a particularly tough incident. It was a short outage affecting a subset of customers, so not exactly the end of the world, but bad enough that it involved multiple people across a number of teams to resolve. Either way, the incident was well managed, and the dust has settled. Now what? Most guidance would say that putting together a post-mortem document is a good idea, given the severity of the incident. You've also done this, so what's next?

In today’s ever-evolving digital landscape, data is the new gold. And with the advent of generative AI in cloud services, businesses have a unique chance to transform their data in powerful new ways.

This release of the collection will feature a whole set of possibilities to deploy a complete Icinga 2 environment. Before diving deep into the collection, a quick recap of all roles which were available and which are included in the current release v0.3.0. New Roles in v0.3.0 To further enhance the Icinga 2 installation process via Ansible those roles are vital for a successful deployment. The Icinga DB is the future backend of Icinga 2, this can be handled with our icingadb and icingadb_redis roles.

Continuous integration (CI) is the process of integrating changes from multiple contributors to create a single software project. A key component for a smooth CI pipeline is testing. Tests prove that the code does exactly what it says on the tin and that it’s safe to merge the code into the central repository. Tests also anticipate edge cases and ensure that the code handles such cases in a deterministic manner.

The new law, SB 253, aims to bring more transparency and accountability to the public about how big businesses contribute to climate change. It also hopes to encourage companies to reduce their emissions and align with the state’s ambitious climate goals. By 2030, California plans to lower its greenhouse gas emissions by 40% below what they were in 1990.