> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/devx/6.1/user-guide/monitoring-and-alerting.md).

# Monitoring & Alerting

This section describes the monitoring and alerting features of Lenses.

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Infrastructure</strong></td><td>Lenses allows for monitoring of your infrastructure, providing visibility into the key services of your Kafka deployments.</td><td><a href="https://880527424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNwC1VSrH2RhBa4WJMBdQ%2Fuploads%2Fgit-blob-ca3157d742f96c6e0da182a5e6b61e4ffb682eb1%2FMonitoring%20--%20Infra.jpg?alt=media">Monitoring -- Infra.jpg</a></td><td><a href="/latest/devx/6.1/user-guide/monitoring-and-alerting/infrastructure-health.md">Infrastructure Health</a></td></tr><tr><td><strong>Consumers</strong></td><td>Lenses allows for the monitoring and alerting of consumer lag. Additionally, you can perform corrective actions on consumer groups by resetting offsets.</td><td><a href="https://880527424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNwC1VSrH2RhBa4WJMBdQ%2Fuploads%2Fgit-blob-4db8009ea94bdb62141bb9e10aa694a193b4803c%2FMonitoring%20--%20Consumer%20lag.jpg?alt=media">Monitoring -- Consumer lag.jpg</a></td><td><a href="/latest/devx/6.1/user-guide/monitoring-and-alerting/consumer-groups.md">Consumer Groups</a></td></tr><tr><td><strong>Alerting</strong></td><td>Lenses provides a set of pre-configured Alert Rules<strong>.</strong> When rules are enabled, Lenses monitors the relevant resources and triggers an Alert Event any time the condition is met.</td><td><a href="https://880527424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNwC1VSrH2RhBa4WJMBdQ%2Fuploads%2Fgit-blob-b6a36d8625d9276747de36b56287a0cf9e9dcd4a%2FMonitoring%20--%20Alerting.jpg?alt=media">Monitoring -- Alerting.jpg</a></td><td><a href="/latest/devx/6.1/user-guide/monitoring-and-alerting/alerting.md">Alerting</a></td></tr><tr><td><strong>Integrations</strong></td><td>Alert events sent to alert Channels. Lenses supports the most common alerting integrations.</td><td><a href="https://880527424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNwC1VSrH2RhBa4WJMBdQ%2Fuploads%2Fgit-blob-70c3164fbb528506dc091be2e1b8fbc00120f76d%2FMonitoring%20--%20Integrations%20(1).jpg?alt=media">Monitoring -- Integrations (1).jpg</a></td><td><a href="/latest/devx/6.1/user-guide/monitoring-and-alerting/integrations.md">Integrations</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lenses.io/latest/devx/6.1/user-guide/monitoring-and-alerting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
