linkedin/burrow

Kafka Consumer Lag Checking

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 17th, 2026
Created on June 2nd, 2015
Open Issues & Pull Requests: 250 (+0)
GitHub issues: Enabled
Number of forks: 818
Total Stargazers: 3,961 (+0)
Total Subscribers: 129 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.2 days
Mean response time: 97.1 days
90th percentile: 246.8 days
Tracked items: 11

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 852 days
Stale 30+ days: 10
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Burrow is a monitoring service for Apache Kafka that checks consumer lag without requiring manual threshold configuration.

Burrow solves the problem of tracking whether Kafka consumers are keeping up with their topics by automatically monitoring committed offsets across all consumer groups and calculating their status on demand. Rather than requiring operators to set fixed lag thresholds, it evaluates consumer health over a sliding window, allowing the system to adapt to normal patterns of lag variation. The tool exposes an HTTP endpoint for querying consumer group status, broker information, and consumer details, and includes configurable notifiers that can send alerts via email or HTTP webhooks when issues are detected.

Burrow suits organizations running Apache Kafka who want automated consumer lag monitoring without the operational burden of tuning thresholds per group. It handles multiple Kafka clusters from a single deployment and automatically discovers all consumers using Kafka-committed offsets, with optional support for Zookeeper-committed and Storm-committed offsets. The HTTP API makes it easy to integrate with existing monitoring and alerting systems.

The project maintains active development with regular updates to its codebase. The build system is kept current with recent Go versions, and the team provides multiple deployment options including Docker and Docker Compose configurations for quick local testing. Documentation is centralized in a project wiki covering configuration details, and the repository includes a docker-compose setup with pre-configured test topics to help new users get started quickly.