PromptVault
CodingProIntermediate

Consumer lag that returns after every rebalance

For engineers diagnosing recurring stream lag from code, metrics, and broker behavior.

Works with
  • Codex
  • GitHub Copilot
  • Ollama
The prompt237 words · 3 blanks

Diagnose why consumer lag returns after rebalancing in [stream_platform] when the observed…

The full prompt is in the app

Included with PromptVault Pro. Fill in the blanks there, then copy it into GitHub Copilot.

What you fill in

  • Streaming platform[stream_platform]ExampleApache Kafka
  • Recurring lag pattern[lag_pattern]ExampleLag clears after deploy, then spikes after each cooperative rebalance
  • Consumer evidence[evidence_bundle]ExampleConsumer code, rebalance logs, partition lag, poll timings, commit metrics, and downstream latency

How to use it

  1. 1Open it in PromptVault. Find it in Coding, or search for “Consumer lag that returns after every rebalance”.
  2. 2Fill in the 3 blanks. streaming platform, recurring lag pattern and consumer evidence — the only things the prompt cannot know.
  3. 3Copy and paste it into GitHub Copilot. It also works with Codex and Ollama.

About this prompt

“Consumer lag that returns after every rebalance” is a intermediate coding prompt. For engineers diagnosing recurring stream lag from code, metrics, and broker behavior. It is 237 words long and written to get a usable answer on the first message, in Codex, GitHub Copilot and Ollama or any other chat assistant. Good for: troubleshooting, debugging, performance, deep dive and devops. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.

More coding prompts

All 120 in Coding