Request for existing cases, user IDs, Portal navigation support and more
Integration & Exception Monitoring in SAP Focused Run provides monitoring of data exchange between different systems within a system landscape or between systems within the landscape and external components (e.g. public cloud services).
In Integration & Exception Monitoring data is collected on managed system side (e.g. for IDocs and PI Messages) and transferred to the SAP Focused Run system or is directly pulled from APIs exposed by the public cloud services into the SAP Focused Run system. In the Integration & Exception Monitoring application you find the following monitoring areas:
To setup Integration & Exception Monitoring please follow the monitoring setup guide provided for each of the supported categories.
In Integration & Exception Monitoring, integration monitoring information is collected on the technical component level. This makes the setup much easier and less error-prone because SAP Focused Run can suggest monitoring categories based on the installed software components. For most of the categories SAP Focused Run also offers default filters, which collect all communication for this monitoring category, no matter where they came from or where they are sent to. These capabilities speed up the initial setup of Integration & Exception Monitoring, as it is no longer necessary to maintain a specific source-target combination for an interface.
However, this new setup approach also means that the landscape topology, which shows the connections between the systems in the landscape, is no longer created automatically. Instead, the landscape topology can be created in a scenario, if it is required. Creating the landscape topology will usually not be necessary for all interfaces in a landscape. For most of them, the technical component-based view will be sufficient. But if you want to group different point-to-point connections that belong to a more complex interface scenario together, you can do this by setting up a scenario.
For some monitoring categories SAP Focused Run can further more correlate messages sent, via the SAP passport. For these monitoring categories you can set up end-to-end flows that describe messages flows that run over several technical components. You can monitor where in the flow a message is located and how long the overall flow took.
For more information, please check the Scenario Configuration.
Ensure that you enter the IFlow instead of the Artifact name when configuring monitoring and alerting filters for SAP Integration Suite. Though the Artifact name and the IFlow may seem similar, they are distinct elements and cannot be used interchangeably.
Tip: For ease of configuration, you can choose the value help and select the desired IFlow value.
You can find the IFlow information in the Message details screen of an Integration Flow artifact.
Wildcard characters, like asterisk (*), are not supported in the filter configuration for Monitoring, Alerting, Reusable filter variants, and Configuration Variants.
If you use the character asterisk (*) as a parameter value, it filters for values with the character (*) as per the parameter and operator definition. It will not function like a wildcard character and create a filter with all values.
The value help is populated based on the data collected by the SAP Focused Run system. Therefore, only the values related to the collected data are listed. Values that haven’t been collected yet are not listed. For this reason, you may not see some values in the value help.
In such scenarios, enter the value directly into the field.