Alerting

This section describes how to configure alerting in Lenses.

Alerts rules are configurable in Lenses, alerts that are generated can then be sent to specific channels. Several different integration points are available for channels.

Infrastructure alerts

These are a set of built-in alerting rules for the core connections, Kafka, Schema Registry, Zookeeper, and Kafka Connect. See infrastructure health.

Data Produced Alerts

Data produced are user-defined alerts on the amount of data on a topic over time. Users have a choice to notify if the topic receives either:

1. more than

2. or less than

Consumer lag alerts

Consumer rules are alerting on consumer group lag. Users can define:

1. a lag

2. on a topic

3. for a consumer group

4. which channels to send an alert to

Application alerts

Lenses allows operators to configure alerting on Connectors. Operators can:

1. Set channels to send alerts to

2. Enable auto restart of connector tasks. Lenses will restart failed tasks with a grace period.

The sequence is:

1. Lenses watches for task failures.

2. If a task fails, Lenses will restart it.

3. If the restart is successful Lenses resets the "restart attempts" back to zero

4. If the restart is not successful, Lenses increments the restart attempts, waits for the grace period and tries another restart if the task is still in a failed state.

Steps 4 is repeated until restart attempts is reached. Lenses will only rest the restart attempts to zero after the tasks have been brought back to a healthy start by manual intervention.

The number of times Lenses attempts to restart is based on the entry in the alert setting.

The restart attempts can be tracked in the Audits page.

Viewing alert events

To view events go to Environments->[Your Environment]->Admin -> Alerts -> Events.