Sap Se

Michael Decker

Mathias Zietzschmann

Steffen Maier

Susanne Gottlieb

Andreas Vogel

Andreas Jahr

Sigo Henkel

Stefan Vormbrock

Dominic Hehn

Andreas Kunstein

Mike Luang-Khot

Pradeep Rathod

Philipp Thiele

Arthee Pranadharthi Haran

In an example embodiment, a data model, software architecture, and process for synchronizing information about tags is provided, that permits assignment between different microservices. When a tag is added to an entity, then an assignment is made. The assignment is a record that contains a reference to a unique identifier for the tag and also describes the entity's domain and entity type. Each service uses at least one distinct domain, so tag assignments from different services should not conflict with one another.

Tag management for distributed applications

A catalog application includes data for key indicators for performance measurement of applications. The catalog application comprises data for a large number of key indicators that may be compatible for different application. A monitoring application utilizes data for key indicators to measure performance of external applications. A catalog service interface is instantiated to process requests from the monitoring application to the catalog application. The external applications run in different technical environments and are part of different technical landscapes. A request to provide data for key indicators compatible with a first application is received at the instantiated service interface. The key indicators in the catalog application are filtered based on matching the technical characteristics of the first application with the key indicators' prerequisites. The data for the compatible key indicators is provided through invoking a user interface of the catalog application for display within the measuring application.

Integration of a catalog application with a monitoring application

Systems and methods to provide integrated incident management for hybrid landscapes are provided. In example embodiments, an incident ticket is received, at a communication hub, from a first component of a first landscape indicating an incident. A second component in a second landscape is determined to which to route incident information including the incident ticket. The determination of the second component is based on an attribute extracted from the incident ticket. The incident information is transmitted to the second component by the communication hub. A solution for the incident ticket is received from the second component based on the second component having the solution or is received from a component of a service backbone based on the component of the service backbone having the solution by the communication hub, and the solution is forwarded to at least one of the first component or the second component.

Integrated incident management for hybrid landscapes

Growing community of inventors

Graben-Neudorf, Germany

Michael Decker