In a traditional model, the teams work in silos, managing servers, network storage, applications, etc. In this model of operations, a ticket is raised to resolve an issue, and it goes through a series of escalations, adding to downtime and affecting the end user. In the new model, Site Reliability Engineering (SRE) teams take ownership of resolving the issue proactively, instead of raising tickets. Understanding the state of the system through data becomes critical here. Applications should be designed to provide metrics that operations and development teams can use to jointly resolve issues. When a system is down, the goal is to stay within an established error budget. It is important to have a team that understands both costs and cloud complexity. Observability is crucial to understanding the Service Level Objective (SLO) of a product in the cloud to improve cloud reliability. There are several tools available on the market, such as product development and debugging tools that can help improve observability, but they are not comprehensive. If the engineering teams provide the tools with data, they can do their magic. However, not many of these tools are ready to provide extreme observability. The cloud industry is still catching up. The focus needs to be placed on improving the observability of these tools, and therefore, improving cloud reliability. Experts from the industry suggest that as customers migrate to cloud platforms and modernize from their monolithic type workloads, they need to rethink how they collect observability data across logs, metrics, and traces. Aiming to improve observability and evaluate the health of their own cloud applications. Making site reliability engineering a priority, Davos today is more focused on automating the operations part of the development cycle until a product gets to production. In SRE, the development and operations teams work together to help in product evolution and maintain reliability in production, a manifestation of development and operations coming together. As far as security is concerned, the cloud provider is responsible for the security of the cloud and ensuring infrastructure is secure and reliable. However, the customer is responsible for security in the cloud. The way these security features are implemented in your application is up to the development team or the consuming client. It is much like how a car comes with safety features such as a seatbelt and brakes. However, it is up to the occupants to use these features.