Use Analytics
Search every processed message, group it by iFlow, read volumes and response times, and export it.
Analytics lists the messages Integration Mapper collected from SAP Cloud Integration, successful or not: status, start, duration, sender, receiver and IDs. Use it to find messages, compare iFlows and read volumes and response times.
Choose the period
Section titled “Choose the period”At the top: 1h, 24h (the default), 7d, All or Custom, with a start and an end. All covers everything still retained, which can be slow in a large environment: prefer a period.
With Auto on, the first page reloads every 15 seconds. The refresh button reloads it now. Analytics reads what Monitoring collected; new messages arrive with each Monitoring sync.
Search
Section titled “Search”Type in the search box, or build a filter with the field list and Add filter: iFlow, Sender, Receiver, Message GUID, Correlation ID or Application Msg ID.
| You type | It finds |
|---|---|
@IntegrationFlowId:Orders | Messages of iFlows whose ID contains “Orders”. |
@MessageGuid:AGb3… | That message. |
@SenderId: @Receiver: @CorrelationId: @ApplicationMessageId: | Messages whose field contains the value. |
| Any other text | Messages with that text in the iFlow, sender, receiver, any ID or the error message. |
Matching ignores case and finds the value anywhere in the field. Put values with spaces in quotes. All filters must match.
The status chips narrow the list; choose several to see any of them, or All.
Three views
Section titled “Three views”| View | What it shows |
|---|---|
| List | A chart of executions in the period, then the messages, newest first, 100 per page. Columns chooses the columns. Drag the handles on the chart to zoom into a period. |
| Fields | One row per iFlow: total, completed, failures, discarded, average duration and last run. Expand a row to see its latest messages. |
| Dashboard | Overview: volume over time and the distribution of durations, with average, p95, p99 and maximum, and the slowest messages. Status: messages by status, and the iFlows with most errors. |
Open a message
Section titled “Open a message”Click a row to see its duration, sender and receiver, start and end, its IDs and, when it failed, the error. Message trace draws the path the message takes according to the iFlow’s design: it is an estimate, marked as such, not a record of the steps it went through.
Save your setup
Section titled “Save your setup”- Views → Save current view keeps the period, statuses, search and columns under a name. Views are personal.
- CSV downloads the messages of the current period, statuses and search: up to 50,000, newest first, with times in UTC. In the file, a message that went through an exception subprocess has the status COMPLETED, as SAP records it.
Next steps
Section titled “Next steps”- Use Monitoring: errors grouped by iFlow and signature
- Monitoring settings: how often messages are collected and how long they are kept