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). 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:
Focused Run 2.0 FP02
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.