When you run a messaging service like SAP Event Mesh in SAP Integration Suite, you quickly accumulate a wide mix of messaging clients and their connections — AMQP-based integrations, MQTT devices, REST publishers, and webhooks. Until now, understanding who is connected, how many connections are active, and which protocols they use meant digging into logs or asking the platform team.
Connection Monitoring changes that. It is now generally available in the Event Mesh in the SAP Integration Suite monitoring UI, as a dedicated screen that provides a real-time, protocol-aware view of all active messaging connections on your service instance.
What is Connection Monitoring in Event Mesh in SAP Integration Suite?
Connection Monitoring provides a live, protocol-aware view of all active messaging connections on a service instance, directly in the Event Mesh in the SAP Integration Suite monitoring UI. You can see which message clients are connected, which protocols they are using, and how that usage has evolved over time.
Key Capabilities
Real-time connection overview: A time-series line chart and client table give you an immediate snapshot of all active connections across every message client on the service instance.
Protocol-level breakdown: Connections are categorized by protocol — AMQP, MQTT, Webhook, and REST — so you can understand not just whether a client is connected, but how it is connected.
Per-client drill-down: Selecting any message client opens a Detail view with a dedicated time-series line chart showing connection details for that client alone, making it easy to isolate anomalies.
Chart personalization: Following the SAP Fiori Analytical List Page pattern, the overview provides some standard chart personalization controls — time range selection, zoom, legend selection, and fullscreen mode — letting you tailor the visualization to the window of interest without leaving the screen.
Accessing Connection Monitoring
Step 1: Navigate to Connections in the Event Mesh Monitor
Open your SAP Integration Suite cockpit and navigate to Monitor > Event Mesh > Connections using the left-hand navigation panel.
The main Connections screen presents two components: a time-series line chart at the top and a message client table below. Together, they give you both a historical perspective and a current-state summary of all connections on the service instance.
Connections Per Message Client — chart and client table overview – Analytical List Page Floorplan
The chart is titled Connections Per Message Client and plots the maximum concurrent connections observed per time interval — each message client appears as its own line in the chart. Critically, the chart also displays your tenant’s maximum allowed connections and the total concurrent connections across all clients — so you can compare actual usage against your plan limits at a glance. The time range can be adjusted to cover a day, week, or month using the selector in the chart toolbar.
Below the chart, the Message Clients table lists every client on the service instance. The connection counts shown — both total and per-protocol — represent the maximum concurrent connections observed during the selected time range, not a point-in-time snapshot:
Message Client Name: The human-readable name as created in your Cloud Foundry environment. If the service instance has been deleted, the client may appear by its GUID instead.
Namespace: The namespace the client belongs to, useful for multi-tenant or multi-team environments.
Total Connections: The aggregate maximum concurrent connection count across all protocols for that client.
AMQP: Maximum concurrent connections using the AMQP 1.0 protocol.
MQTT: Maximum concurrent connections using the MQTT protocol.
Webhook: Maximum concurrent webhook-based connections.
REST: Maximum concurrent connections using the REST messaging protocol.
Step 3: Select a Client to Open the Detail View
Click on any row in the Message Clients table to navigate to the Detail view for that specific client. This is where you go when you need to understand the connection details of one integration in isolation — for example, when troubleshooting a failing integration flow or validating a new deployment.
Connection Monitoring Detail Components
Connections Over Time Chart
The Detail view centers on a chart titled Connections Over Time, which plots connection counts for the selected message client across all protocols that have recorded data. Only protocols with actual connections appear as lines in the chart, keeping the visualization focused and readable. A Max line is also rendered, showing the peak connection count across all protocols at any given point in time.
Connections Over Time — per-client protocol breakdown
The same chart personalization controls available in the Overview are present here: time range selector, zoom, legend selection, and fullscreen mode. Adjusting the time range is particularly useful when correlating a connection drop with a deployment event or an incident window.
Supported Protocols
Connection Monitoring tracks connections across all protocols supported by Event Mesh in SAP Integration Suite. Understanding which protocols a client uses can reveal misconfigurations, unexpected fallback behavior, or opportunities to consolidate connection types.
AMQP: Advanced Message Queuing Protocol — commonly used by SAP BTP services and enterprise integration adapters.
MQTT: Lightweight publish/subscribe protocol — typical in IoT and high-volume event streaming scenarios.
Webhook: Push-based delivery connections — active when Event Mesh is configured to push messages to an HTTP endpoint.
REST: HTTP-based messaging — used when consumers or producers interact with queues and topics via REST APIs.
Practical Use Cases
Troubleshooting a failing integration: Navigate to the relevant message client and confirm whether an active connection is present. A zero connection count immediately narrows the root cause to the client side rather than the broker.
Understanding your integration landscape: The protocol columns in the overview table show you how many connections each client has per protocol, giving you a complete picture of your messaging landscape at a glance.
Capacity and scaling decisions:The chart displays a Max VPN Connections line representing your plan’s connection ceiling, making it immediately visible when you are approaching the limit. This matters because once the limit is reached, existing sessions continue normally — but new clients cannot connect, and any client that disconnects may be unable to reconnect until usage drops back below the limit.
Validating a new deployment: After deploying a new integration flow, open the Detail view for the corresponding message client and confirm the expected connection was established on schedule.
Conclusion
Connection Monitoring closes a significant observability gap for teams operating event-driven integrations on SAP Integration Suite. By surfacing real-time, protocol-aware connection data directly in the monitoring UI — without requiring access to broker logs or external dashboards — it reduces the time needed to diagnose connectivity issues and understand the runtime state of your messaging infrastructure.
IntroductionWhen you run a messaging service like SAP Event Mesh in SAP Integration Suite, you quickly accumulate a wide mix of messaging clients and their connections — AMQP-based integrations, MQTT devices, REST publishers, and webhooks. Until now, understanding who is connected, how many connections are active, and which protocols they use meant digging into logs or asking the platform team.Connection Monitoring changes that. It is now generally available in the Event Mesh in the SAP Integration Suite monitoring UI, as a dedicated screen that provides a real-time, protocol-aware view of all active messaging connections on your service instance.What is Connection Monitoring in Event Mesh in SAP Integration Suite?Connection Monitoring provides a live, protocol-aware view of all active messaging connections on a service instance, directly in the Event Mesh in the SAP Integration Suite monitoring UI. You can see which message clients are connected, which protocols they are using, and how that usage has evolved over time.Key CapabilitiesReal-time connection overview: A time-series line chart and client table give you an immediate snapshot of all active connections across every message client on the service instance.Protocol-level breakdown: Connections are categorized by protocol — AMQP, MQTT, Webhook, and REST — so you can understand not just whether a client is connected, but how it is connected.Per-client drill-down: Selecting any message client opens a Detail view with a dedicated time-series line chart showing connection details for that client alone, making it easy to isolate anomalies.Chart personalization: Following the SAP Fiori Analytical List Page pattern, the overview provides some standard chart personalization controls — time range selection, zoom, legend selection, and fullscreen mode — letting you tailor the visualization to the window of interest without leaving the screen.Accessing Connection MonitoringStep 1: Navigate to Connections in the Event Mesh MonitorOpen your SAP Integration Suite cockpit and navigate to Monitor > Event Mesh > Connections using the left-hand navigation panel.For official documentation, see Monitor Event Mesh in SAP Integration Suite.Step 2: Explore the OverviewThe main Connections screen presents two components: a time-series line chart at the top and a message client table below. Together, they give you both a historical perspective and a current-state summary of all connections on the service instance.Connections Per Message Client — chart and client table overview – Analytical List Page FloorplanThe chart is titled Connections Per Message Client and plots the maximum concurrent connections observed per time interval — each message client appears as its own line in the chart. Critically, the chart also displays your tenant’s maximum allowed connections and the total concurrent connections across all clients — so you can compare actual usage against your plan limits at a glance. The time range can be adjusted to cover a day, week, or month using the selector in the chart toolbar.Below the chart, the Message Clients table lists every client on the service instance. The connection counts shown — both total and per-protocol — represent the maximum concurrent connections observed during the selected time range, not a point-in-time snapshot:Message Client Name: The human-readable name as created in your Cloud Foundry environment. If the service instance has been deleted, the client may appear by its GUID instead.Namespace: The namespace the client belongs to, useful for multi-tenant or multi-team environments.Total Connections: The aggregate maximum concurrent connection count across all protocols for that client.AMQP: Maximum concurrent connections using the AMQP 1.0 protocol.MQTT: Maximum concurrent connections using the MQTT protocol.Webhook: Maximum concurrent webhook-based connections.REST: Maximum concurrent connections using the REST messaging protocol.Step 3: Select a Client to Open the Detail ViewClick on any row in the Message Clients table to navigate to the Detail view for that specific client. This is where you go when you need to understand the connection details of one integration in isolation — for example, when troubleshooting a failing integration flow or validating a new deployment.Connection Monitoring Detail ComponentsConnections Over Time ChartThe Detail view centers on a chart titled Connections Over Time, which plots connection counts for the selected message client across all protocols that have recorded data. Only protocols with actual connections appear as lines in the chart, keeping the visualization focused and readable. A Max line is also rendered, showing the peak connection count across all protocols at any given point in time.Connections Over Time — per-client protocol breakdownThe same chart personalization controls available in the Overview are present here: time range selector, zoom, legend selection, and fullscreen mode. Adjusting the time range is particularly useful when correlating a connection drop with a deployment event or an incident window.Supported ProtocolsConnection Monitoring tracks connections across all protocols supported by Event Mesh in SAP Integration Suite. Understanding which protocols a client uses can reveal misconfigurations, unexpected fallback behavior, or opportunities to consolidate connection types.AMQP: Advanced Message Queuing Protocol — commonly used by SAP BTP services and enterprise integration adapters.MQTT: Lightweight publish/subscribe protocol — typical in IoT and high-volume event streaming scenarios.Webhook: Push-based delivery connections — active when Event Mesh is configured to push messages to an HTTP endpoint.REST: HTTP-based messaging — used when consumers or producers interact with queues and topics via REST APIs.Practical Use CasesTroubleshooting a failing integration: Navigate to the relevant message client and confirm whether an active connection is present. A zero connection count immediately narrows the root cause to the client side rather than the broker.Understanding your integration landscape: The protocol columns in the overview table show you how many connections each client has per protocol, giving you a complete picture of your messaging landscape at a glance.Capacity and scaling decisions: The chart displays a Max VPN Connections line representing your plan’s connection ceiling, making it immediately visible when you are approaching the limit. This matters because once the limit is reached, existing sessions continue normally — but new clients cannot connect, and any client that disconnects may be unable to reconnect until usage drops back below the limit.Validating a new deployment: After deploying a new integration flow, open the Detail view for the corresponding message client and confirm the expected connection was established on schedule.ConclusionConnection Monitoring closes a significant observability gap for teams operating event-driven integrations on SAP Integration Suite. By surfacing real-time, protocol-aware connection data directly in the monitoring UI — without requiring access to broker logs or external dashboards — it reduces the time needed to diagnose connectivity issues and understand the runtime state of your messaging infrastructure.If you are interested in complementary visibility tools within Event Mesh in SAP Integration Suite, check out Queue Browser: Deep Message Visibility for Event Mesh in SAP Integration Suite, which covers message-level inspection for queues.Happy monitoring! Read More Technology Blog Posts by SAP articles
