unbridled-41 opened a new issue, #3998:
URL: https://github.com/apache/rocketmq-dashboard/issues/3998
1. Please describe the feature you are requesting.
The DLQ message drawer (`web/src/pages/instance/dlq.tsx`, backed by `GET
/api/dlq/{groupName}/messages`) shows msgId, topic, queue, offset, store time,
keys, and a truncated body — but no user properties. The Apache provider builds
each `DLQMessageVO` from the full `MessageExt` it has already scanned
(`RocketMQDLQProvider.toExportVO`), so the properties are in hand and simply
dropped. The classic dashboard's DLQ detail dialog
(`frontend-new/src/components/DlqMessageDetailViewDialog.jsx` on the `master`
branch) renders the properties payload (including TAGS/KEYS).
2. Provide any additional detail on your proposed use case for this feature.
Business user properties are usually the only way to tell why one dead
letter matters more than another (trace ids, tenant markers, retry counters).
The resend path already values them: #1436 made DLQ resend preserve user
properties. Displaying them in the drawer completes that picture without any
extra broker call — the data is already scanned and in memory per request.
3. Indicate the importance of this issue to you (blocker, must-have,
should-have, nice-to-have).
should-have. Workaround today is opening the Message Explorer, querying the
`%DLQ%<group>` topic manually, and opening each message there.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
