@Aaron exactly that is what i look for and is needed as it would show even gaps on mapping of solace fields to RDP and target http header like ReplicationGroupMessageId.
I will raise a feature request to make this mappings transparent and public.
They are essential to understand and as mentioned by mixing in Solace sometimes between internal names and solace public names you loose control on what data goes in which field on interface level.
I would include MQTT as well then. Any mapping is needed when different interfaces are exposed by Solace. JMS, RDP (REST) and MQTT are part of that list.
Again mainy thanks for sharing and working on that and let’s hope it is soon part of public documentation.