awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
linkedin avatar

linkedin/Burrow

0
View on GitHub↗
3,954 stars·810 forks·Go·Apache-2.0·17 views

Burrow

Burrow is a monitoring and alerting service for Kafka clusters. It tracks consumer group lag by evaluating committed offsets and identifying the gap between produced and consumed messages.

The system calculates processing delays using a sliding-window offset evaluation and monitors overall cluster health. When consumer group conditions meet predefined thresholds, it triggers notifications to external services via email or webhooks.

The service provides HTTP endpoints for querying broker information and consumer group status, allowing external tools to poll for system health and performance metrics.

Features

  • Kafka Cluster Health Monitors - Provides real-time metrics and health status of Kafka brokers and consumer groups through a dedicated API.
  • Consumer Lag Monitoring - Tracks the delay between produced and consumed messages in Kafka to identify processing bottlenecks and system latency.
  • Offset Metadata Retrievers - Fetches current offset positions directly from Kafka brokers to determine the gap between production and consumption.
  • Sliding-Window Evaluators - Calculates consumer lag by tracking committed offsets over a specific time interval to detect processing delays.
  • Stream Offset Tracking - Evaluates committed offsets over a sliding window to determine if consumer groups are keeping up with data streams.
  • Event-Driven Notification Triggers - Dispatches alerts to external services immediately when Kafka consumer group conditions cross predefined threshold limits.
  • Message Broker Monitoring - Monitors the gap between the last produced and last consumed message to detect processing bottlenecks.
  • Kafka Alerting Integrations - Sends notifications to external services when Kafka consumer groups meet specific error or delay conditions.
  • Monitoring Alerting Systems - Implements a notification engine that triggers email or web call alerts based on Kafka consumer lag thresholds.
  • Event-Triggered Alert Deliveries - Triggers configurable alarms via email or web-calls when specific Kafka consumer group lag conditions are met.
  • Polling-Based Health Monitors - Exposes an on-demand HTTP endpoint that allows external monitoring tools to poll for system health and broker information.
  • Webhook Notifications - Sends automated HTTP webhook calls to third-party services when consumer lag conditions are met.
  • Broker HTTP Endpoints - Provides HTTP endpoints within the service to retrieve broker information and consumer group status for health monitoring.

Star history

Star history chart for linkedin/burrowStar history chart for linkedin/burrow

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Frequently asked questions

What does linkedin/burrow do?

Burrow is a monitoring and alerting service for Kafka clusters. It tracks consumer group lag by evaluating committed offsets and identifying the gap between produced and consumed messages.

What are the main features of linkedin/burrow?

The main features of linkedin/burrow are: Kafka Cluster Health Monitors, Consumer Lag Monitoring, Offset Metadata Retrievers, Sliding-Window Evaluators, Stream Offset Tracking, Event-Driven Notification Triggers, Message Broker Monitoring, Kafka Alerting Integrations.

Which projects share features with linkedin/burrow?

Projects with overlapping indexed features include: obsidiandynamics/kafdrop — Kafdrop is a web-based interface for monitoring and managing Apache Kafka clusters, topics, brokers, and consumer… tchiotludo/akhq — AKHQ is a web-based management interface for Apache Kafka, providing a centralized platform for administering… arachnys/cabot — Cabot is a self-hosted incident management platform and monitoring alert manager. It serves as a centralized system… yahoo/cmak — CMAK is a Kafka cluster management tool and web interface designed for the administration of brokers, topics, and… acassen/keepalived — Keepalived is a high availability manager and virtual IP failover tool that ensures continuous service availability.… pantsel/konga — Konga is a web-based administration panel for managing Kong API Gateway entities, nodes, and configurations without…

Projects sharing features with Burrow

These projects share indexed features with Burrow. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • tchiotludo/akhqtchiotludo avatar

    tchiotludo/akhq

    3,824View on GitHub↗

    AKHQ is a web-based management interface for Apache Kafka, providing a centralized platform for administering clusters, topics, and consumer groups. It serves as a comprehensive monitoring and administration tool that includes a Kafka Connect manager and a ksqlDB administration interface. The platform distinguishes itself through extensive schema registry integration, allowing users to browse and decode Avro, Protobuf, and JSON messages using Confluent, Tibco, or AWS Glue registries. It also features a granular security model with role-based access control, sensitive data masking, and support

    Javaguijavakafka
    View on GitHub↗3,824
  • obsidiandynamics/kafdropobsidiandynamics avatar

    obsidiandynamics/kafdrop

    6,139View on GitHub↗

    Kafdrop is a web-based interface for monitoring and managing Apache Kafka clusters, topics, brokers, and consumer groups. It functions as a cluster monitor and topic manager that provides a visual representation of broker health, partition assignments, and consumer group lag. The system includes a message browser capable of reading, decoding, and publishing messages to Kafka topics using schema registries or descriptor files. It also provides a metadata API that exposes cluster information through JSON endpoints for integration with external monitoring tools. The platform covers administrati

    Javaconsumer-groupconsumer-producerdocker
    View on GitHub↗6,139
  • arachnys/cabotarachnys avatar

    arachnys/cabot

    5,668View on GitHub↗

    Cabot is a self-hosted incident management platform and monitoring alert manager. It serves as a centralized system for receiving external monitoring data, managing on-call responder rotations, and dispatching incident notifications to administrators to ensure prompt resolution of system failures. The platform provides a containerized monitoring interface and a REST API for programmatically creating and modifying monitoring data and incident reports. It coordinates the routing of critical system alerts and manages the scheduling of personnel for on-call rotations. The system includes capabil

    JavaScript
    View on GitHub↗5,668
  • yahoo/cmakyahoo avatar

    yahoo/CMAK

    11,926View on GitHub↗

    CMAK is a Kafka cluster management tool and web interface designed for the administration of brokers, topics, and partitions. It provides a centralized system for Kafka cluster governance, encompassing resource administration, access control, and data distribution optimization. The project features a management UI that allows for the creation, deletion, and update of topic configurations and partition counts. It includes a partition rebalancer for executing data reassignment and preferred replica elections to balance load across cluster nodes. The system provides observability through broker

    Scala
    View on GitHub↗11,926
Compare all 30 related projects→