Message GUID Visible via Node.js Client but Python Client Cannot View GUID in PubSub+ Cloud Monitor

General Discussions
1

We have two clients connecting to the same Solace PubSub+ Cloud broker. The Node.js client works correctly — messages are published and consumed with a per-message GUID
visible in logs. The Python client is not working — we are unable to view GUID details in the Solace PubSub+ Cloud Monitor for messages published via Python.

Broker Details:

┌────────────┬───────────────────────────────────────────────────────────────┐
│ Field │ Value │
├────────────┼───────────────────────────────────────────────────────────────┤
│ Broker URL │ tcps://mr-connection-fvw2m7bu50o.messaging.solace.cloud:55443 │
├────────────┼───────────────────────────────────────────────────────────────┤
│ Protocol │ TCPS (SMF over TLS, port 55443) │
├────────────┼───────────────────────────────────────────────────────────────┤
│ Platform │ Solace PubSub+ Cloud │
└────────────┴───────────────────────────────────────────────────────────────┘

Client 1 — Node.js (WORKING):

  • SDK: solclientjs v10.18.2
  • Protocol: TCPS (SMF over TLS, port 55443)
  • Auth: mTLS (client certificate + SSL trust store)
  • GUID: UUID v4 generated per message (requestguid), embedded in message payload
  • Behaviour: Publisher and consumer both log the GUID correctly end-to-end:
    Tested across multiple regions: US East, US West, Tokyo

Client 2 — Python (NOT WORKING):

  • SDK: solace-messaging-client 1.8.0
  • Protocol: TCPS (SMF over TLS, port 55443)
  • Auth: Username/password + mTLS (client certificates)
  • GUID: UUID v4 set via .with_application_message_id(str(uuid4())) at publish time
  • Behaviour: Messages are published but GUID details are not visible in Solace PubSub+ Cloud Monitor — cannot trace or correlate messages by GUID from the Monitor UI

Questions:

  1. Why does the Node.js (solclientjs) client allow GUID visibility while the Python (solace-messaging-client) client does not?
  2. Is .with_application_message_id() the correct API to set a traceable GUID in the Python SDK? Is there a different method needed?
  3. Is there a SEMP v2 endpoint to browse queued messages with their payload/headers per message?
    • e.g. /SEMP/v2/monitor/msgVpns/{vpn}/queues/{queue}/msgs
  4. What is the recommended approach for end-to-end message traceability using the Python SDK on PubSub+ Cloud?
  5. Is there a SEMP v2 endpoint to list/search individual queued messages by application_message_id?
    • e.g. /SEMP/v2/monitor/msgVpns/{vpn}/queues/{queue}/msgs