> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/use-cases/for-platform-engineers/unified-observability-and-alerting.md). # Unified Observability and Alerting {% hint style="info" %} As a platform engineer, gain visibility into K8s events, metrics & logs across any cluster that is synced to Ozone from a single dashboard Receive critical alerts with respect to Kubernetes resources and cluster metrics broken down to the level of a pod. {% endhint %} ### Problems * Kubernetes events have a short time to live on clouds; making it difficult for a post-mortem analysis * Monitoring systems supplied by the cloud are vendor specific; integrations are not straight out of the box. Moreover, this needs to be consolidated and federated across clusters from any cloud * As the application and infra complexity grows, there is a need for these standard alerting templates which gets difficult to manage across different cloud contexts and solutions ### Solutions * Ozone automatically saves your K8s events from any linked cluster to its own store, there by allowing you to retain cross cloud cluster events for as long as you wish to store them * Ozone's event, metric and log collection and aggregation is federated by default. Just link your cluster and within a few clicks you are ready for superior monitoring and alerting * Manage metric alerts as a template and re-distribute them across teams for better governance --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ozone.one/ozone-end-user-guide/use-cases/for-platform-engineers/unified-observability-and-alerting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.