InfoFounding Members35 lifetime licenses available — view the offer > https://uptriva.com/foundingInfoMCP launch announcementConnect Claude, Cursor or any MCP client with your API token — let an agent create monitors, manage incidents and configure alerts. Read the docs → https://uptriva.com/docs/api/mcp
All check types
Databases & Queues

Kafka Monitoring

Kafka monitoring connects to the broker port and validates the protocol handshake — the earliest signal that partitions, ZK/KRaft trouble or resource pressure are about to stall your pipelines.

A broker that stops accepting connections stalls every stream

What it checks

  • Broker port handshake
  • Connection latency
  • Acceptance failures during partition or controller issues

Set it up

  1. 1Add a Kafka monitor per broker
  2. 2Run private clusters via the internal agent
  3. 3Escalate to the platform team

FAQ

What about consumer lag?

Lag is app-level and belongs in your metrics pipeline. This check is the availability floor — the broker must accept connections before lag even matters.

Related check types

PostgreSQL MonitoringThe database answering 'accepting connections' is not the same as healthyMySQL / MariaDB MonitoringConnection refused is how your app learns the DB is down — get there firstRedis MonitoringWhen the cache dies, the database takes the hit

Start monitoring in minutes

External probes plus internal agents, escalation chains and status pages — free tier, no card required.

Start free Read the docs