Integration and Cloud Monitoring provides monitoring of data exchange in-between different systems within a system landscape or between systems within a 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 Focused Run system or is directly pulled from APIs exposed by the public cloud services into the Focused Run system. Please also check the latest video about Advanced Integration Monitoring in Focused Run.
General availability with Focused Run 1.0 FP01
Focused Run 2.0 SP00
Focused Run 2.0 FP01
To set up Advanced Integration Monitoring please follow the monitoring setup guide provided for each of the supported categories below:
The monitoring of following exception categories are supported:
In today's business scenarios and processes are often distributed cross-system and over multiple application components. SAP Exception Management includes proactive monitoring of mission critical components, required for a smooth and reliable flow of the core business processes in heterogeneous cross-technology landscapes. Also, it provides tools for deeper error analysis, processing and documentation.
The SAP Exception Management is the central place to monitor and analyze critical exceptions. Exceptions are distinguished by category. Customers have the possibility to define collection and alerting filters to their own needs. The following categories are currently supported:
In Advanced Integration Monitoring, integration monitoring information is collected on the technical component level. This makes the setup much easier and less error-prone because Focused Run can suggest monitoring categories based on the installed software components. For most of the categories 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 Advanced Integration 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 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.