Queue Browser: Deep Message Visibility for Event Mesh in SAP Integration Suite

Estimated read time 10 min read

Introduction

In event-driven architectures, messages flow continuously between systems, carrying critical business data and triggering essential processes. When something goes wrong—messages pile up, integrations fail, or data appears corrupted—you need immediate visibility into what’s happening inside your queues. Without this insight, troubleshooting becomes a frustrating game of guesswork.

Monitoring message queues is essential in event‑driven architectures. It reveals queue health and uncovers bottlenecks, providing crucial delivery and routing insights that ensure system reliability. With the latest release of Event Mesh in SAP Integration Suite, we’re excited to announce Queue Browser, a new capability that delivers deep message visibility through an intuitive web‑based interface.

The key advantage: Visualizing and inspecting messages using Queue Browser won’t consume them from the message broker queue, so you can safely examine message metadata—such as headers, statuses, and errors—and troubleshoot malformed payloads without disrupting live processing.

What is Queue Browser in Event Mesh in SAP Integration Suite?

Queue Browser is a web-based monitoring and diagnostics tool that allows you to inspect messages in a queue without consuming them from the message broker queue. Think of it as a “read-only window” into your message queues—you can see everything that’s happening without affecting the actual message flow.

Queue Browser bridges the gap between high-level queue metrics and detailed application logs, giving you the message-level insight needed for effective troubleshooting.

Key Capabilities

Search & Filter: Quickly locate messages by criteria such as message ID, correlation ID, and custom properties.Header, Payload, and Custom Properties Inspection: View standard JMS-style headers (timestamp, delivery mode, Dead Message Queue eligibility) and examine the message payload alongside any custom properties. This is invaluable for validating data transformations and ensuring message integrity.Message Management: Identify and inspect stuck or problematic messages in queues, with the option to delete them when needed.Purge Queues: Clear all messages from a selected queue in one action, ideal for resetting test environments or clearing backed-up queues during maintenance.

Queue Browser in action

Accessing the Queue Browser

Step 1: Navigate to Queue Monitoring

In the SAP Integration Suite Cockpit, open the left‑hand menu and navigate to:

Monitor › Event Mesh › Queues

Step 2: Review Queue Metrics

You’ll see a comprehensive table listing all your queues with real-time usage metrics:

Monitoring Event Mesh Usage – Queue List Floorplan

Name: The name of the queueMessages Queued: Number of messages in the queueUnacknowledged Messages: Number of unacknowledged messages in the queue. Messages delivered but not yet acknowledged as processed.Queue Size: The queue size in bytes.Max Queue Size: The maximum size possible for the queue in bytes.

These metrics provide immediate insight into queue health—high unacknowledged message counts often indicate processing issues, while queues approaching their size limits may need attention.

Step 3: Drill Down to Message List

Message List Report Floorplan

Select any queue to drill down to its message list page, where you can view some per‑message information:

Message ID: Identifier for tracking messagesCorrelation ID: Identifier to trace the request journeyTime Sent: Time the message was sentMessage Size: The size of the message content, in bytesRedelivered: Indicates if the message was redelivered or not—a key troubleshooting indicatorDestination: Destination of the messageDMQ Eligible: Indicates whether the message is eligible for the Dead Message Queue (DMQ)

Step 4: Inspect Individual Messages

Message Details – Object Page Floorplan

Click a message entry to navigate to its details page. The level of access depends on your assigned roles:

Users can review the message headers by default; if your BTP user has the EventMeshBusinessExpert role collection assigned, you’ll also see the full payload and any custom properties.

Security Note: Access to single‑message inspection is restricted to specific roles only. Only users assigned the EventMeshBusinessExpert role collection should be granted permission to view full message payloads and custom properties and delete messages. This ensures that message access is tightly controlled per organizational requirements and can be managed via Configuring User Access.

Message Detail Components

Headers Information

IdentifiersMessage ID: Identifier for tracking messagesCorrelation ID: Identifier to trace the request journeyDelivery InformationTime Sent: Time the message was sentRedelivered: Indicates if the message was redelivered or not—a key troubleshooting indicatorDelivery Mode: The mode which is used for message deliveryRouting InformationDestination: The destination of the messageReply To: The address or topic to which the recipient should send the response, when a message that requires a reply or acknowledgment, is published.DMQ Eligible: Indicates whether the message is eligible for the Dead Message Queue (DMQ)Additional Information: Message size in bytes

Payload

The message payload contains the actual business data being transmitted between systems.

Custom Properties

Custom properties contain business-specific metadata that applications attach to messages. These might include:

Customer IDs for filteringSource system identifiers for tracing

This metadata is invaluable for understanding message context and implementing sophisticated filtering strategies.

Available Actions

From the message detail page, users with appropriate permissions can:

Delete individual problematic messagesDownload message payloads for offline analysisCopy message IDs and correlation IDs for use in other tools

Conclusion

The Queue Browser for Event Mesh in SAP Integration Suite transforms how you monitor and troubleshoot event-driven systems. By providing safe, non-disruptive message inspection, it empowers you to validate message content before processing, diagnose complex integration issues, and ensure smooth data flow.

Next Steps

Explore Queue Browser in your SAP Integration Suite tenant—navigate to Monitor › Event Mesh › QueuesReview the official documentation:Monitor Event MeshConfiguring User AccessPersonas & PermissionsShare your experience on the SAP Community—help others understand how Queue Browser improves their troubleshooting workflows

Queue Browser puts the visibility and control you need right at your fingertips. Start exploring your message queues today and experience the difference that comprehensive message visualization and inspection makes in maintaining event-driven architectures.

Happy monitoring!

 

​ IntroductionIn event-driven architectures, messages flow continuously between systems, carrying critical business data and triggering essential processes. When something goes wrong—messages pile up, integrations fail, or data appears corrupted—you need immediate visibility into what’s happening inside your queues. Without this insight, troubleshooting becomes a frustrating game of guesswork.Monitoring message queues is essential in event‑driven architectures. It reveals queue health and uncovers bottlenecks, providing crucial delivery and routing insights that ensure system reliability. With the latest release of Event Mesh in SAP Integration Suite, we’re excited to announce Queue Browser, a new capability that delivers deep message visibility through an intuitive web‑based interface.The key advantage: Visualizing and inspecting messages using Queue Browser won’t consume them from the message broker queue, so you can safely examine message metadata—such as headers, statuses, and errors—and troubleshoot malformed payloads without disrupting live processing.What is Queue Browser in Event Mesh in SAP Integration Suite?Queue Browser is a web-based monitoring and diagnostics tool that allows you to inspect messages in a queue without consuming them from the message broker queue. Think of it as a “read-only window” into your message queues—you can see everything that’s happening without affecting the actual message flow.Queue Browser bridges the gap between high-level queue metrics and detailed application logs, giving you the message-level insight needed for effective troubleshooting.Key CapabilitiesSearch & Filter: Quickly locate messages by criteria such as message ID, correlation ID, and custom properties.Header, Payload, and Custom Properties Inspection: View standard JMS-style headers (timestamp, delivery mode, Dead Message Queue eligibility) and examine the message payload alongside any custom properties. This is invaluable for validating data transformations and ensuring message integrity.Message Management: Identify and inspect stuck or problematic messages in queues, with the option to delete them when needed.Purge Queues: Clear all messages from a selected queue in one action, ideal for resetting test environments or clearing backed-up queues during maintenance.Queue Browser in actionAccessing the Queue BrowserStep 1: Navigate to Queue MonitoringIn the SAP Integration Suite Cockpit, open the left‑hand menu and navigate to:Monitor › Event Mesh › QueuesStep 2: Review Queue MetricsYou’ll see a comprehensive table listing all your queues with real-time usage metrics:Monitoring Event Mesh Usage – Queue List FloorplanName: The name of the queueMessages Queued: Number of messages in the queueUnacknowledged Messages: Number of unacknowledged messages in the queue. Messages delivered but not yet acknowledged as processed.Queue Size: The queue size in bytes.Max Queue Size: The maximum size possible for the queue in bytes.These metrics provide immediate insight into queue health—high unacknowledged message counts often indicate processing issues, while queues approaching their size limits may need attention.Step 3: Drill Down to Message ListMessage List Report FloorplanSelect any queue to drill down to its message list page, where you can view some per‑message information:Message ID: Identifier for tracking messagesCorrelation ID: Identifier to trace the request journeyTime Sent: Time the message was sentMessage Size: The size of the message content, in bytesRedelivered: Indicates if the message was redelivered or not—a key troubleshooting indicatorDestination: Destination of the messageDMQ Eligible: Indicates whether the message is eligible for the Dead Message Queue (DMQ)Step 4: Inspect Individual MessagesMessage Details – Object Page FloorplanClick a message entry to navigate to its details page. The level of access depends on your assigned roles:Users can review the message headers by default; if your BTP user has the EventMeshBusinessExpert role collection assigned, you’ll also see the full payload and any custom properties.Security Note: Access to single‑message inspection is restricted to specific roles only. Only users assigned the EventMeshBusinessExpert role collection should be granted permission to view full message payloads and custom properties and delete messages. This ensures that message access is tightly controlled per organizational requirements and can be managed via Configuring User Access.Message Detail ComponentsHeaders InformationIdentifiersMessage ID: Identifier for tracking messagesCorrelation ID: Identifier to trace the request journeyDelivery InformationTime Sent: Time the message was sentRedelivered: Indicates if the message was redelivered or not—a key troubleshooting indicatorDelivery Mode: The mode which is used for message deliveryRouting InformationDestination: The destination of the messageReply To: The address or topic to which the recipient should send the response, when a message that requires a reply or acknowledgment, is published.DMQ Eligible: Indicates whether the message is eligible for the Dead Message Queue (DMQ)Additional Information: Message size in bytesPayloadThe message payload contains the actual business data being transmitted between systems.Custom PropertiesCustom properties contain business-specific metadata that applications attach to messages. These might include:Customer IDs for filteringSource system identifiers for tracingThis metadata is invaluable for understanding message context and implementing sophisticated filtering strategies.Available ActionsFrom the message detail page, users with appropriate permissions can:Delete individual problematic messagesDownload message payloads for offline analysisCopy message IDs and correlation IDs for use in other toolsConclusionThe Queue Browser for Event Mesh in SAP Integration Suite transforms how you monitor and troubleshoot event-driven systems. By providing safe, non-disruptive message inspection, it empowers you to validate message content before processing, diagnose complex integration issues, and ensure smooth data flow.Next StepsExplore Queue Browser in your SAP Integration Suite tenant—navigate to Monitor › Event Mesh › QueuesReview the official documentation:Monitor Event MeshConfiguring User AccessPersonas & PermissionsShare your experience on the SAP Community—help others understand how Queue Browser improves their troubleshooting workflowsQueue Browser puts the visibility and control you need right at your fingertips. Start exploring your message queues today and experience the difference that comprehensive message visualization and inspection makes in maintaining event-driven architectures.Happy monitoring!   Read More Technology Blog Posts by SAP articles 

#SAP

#SAPTechnologyblog

You May Also Like

More From Author