Recued
Menu
← Back to recipes

Confluent Get Consumer Group Lag Summary

by recued-core v1 5 views

Non-chat, uncached, read-only Confluent workflow over Get Consumer Group Lag Summary. It performs no provider mutation, stays on the selected enrolled Confluent origin, and reports pagination completeness explicitly.

How it works 2 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (2 steps)
rows ?
scope to_summary
Format results as a summary card
Settings 3 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

cluster id setting =
confluent kafka setting =
consumer group id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Read your Confluent_kafka connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

confluent confluentdata-streamingread-onlypack:confluent-kafka-cluster

Details

2 steps 3 configurable settings recipe_id: get-kafka-consumer-group-lag-summary-confluent