feat(queues): Split transaction table into producer and consumer tables#109683
Merged
DominikB2014 merged 1 commit intomasterfrom Mar 2, 2026
Conversation
…umer tables Replace the combined transactions table in the queue summary prebuilt dashboard with two dedicated tables — one for producer (queue.publish) and one for consumer (queue.process) transactions. Each table only shows relevant fields for its operation type, making it easier to analyze producer and consumer behavior independently. Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
bot
added
the
Scope: Frontend
narsaynorath
approved these changes
Mar 2, 2026
DominikB2014
deleted the
dominikbuszowiecki/browse-377-split-queue-producerconsumer-table-into-two
branch
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace the single combined transactions table in the queue summary prebuilt dashboard with two separate tables — one for producer (
queue.publish) operations and one for consumer (queue.process) operations.The original combined table showed all fields regardless of relevance, including columns like "Avg time in queue" for producers (which don't receive messages) and "Published" for consumers. Splitting into dedicated tables removes the irrelevant fields and makes it clearer what metrics matter for each side of the queue.
Producer table fields: Transaction, Error rate, Published, Time spent
Consumer table fields: Transaction, Avg time in queue, Avg processing time, Error rate, Processed, Time spent
Refs DAIN-1239