Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

What is the Business Context good for?

APM is often understood from a technical point of view where technical people have a look on the application. In fact the reality is that APM heavily affects operating and business people who need to undestand APM-related data as well. Even for technically affine people it is hard to understand the technical monitoring of an application if the business context is missing.
Understanding the impact of slow or failing requests necessitates that the person knows what part of the application is affected. This is where the business context comes into play.

The business context allows to quickly understand what the user tried to achieve.

Concepts of the Business Context Definition

The goal of defining the business context is to specify how technical requests are mapped to different business goals of the target system's users. The business context comprises two conceptual layers: Applications and Business Transactions.

Business Transactions

A business transaction is the mapping of one technical request / user request to one specific business goal of a user. The boundaries of a business transaction are scenario dependent. Hence, a business transaction may span multiple nodes or only single nodes of a system.

Applications

An application is a grouping of business transactions that logically belong to the same overall business goal.

Example:

Let's assume that we are monitoring two systems with inspectIT:

  • An online shop called DVDStore
  • And an online shop called PetStore 

Both systems are using common components in the backend, as depicted in the following picture:

Although this looks like one system, conceptually, we can differentiate two aplications (DVDStore and Petstore) as, from the perspective of the users, these two have different overall busines goals (selling DVDs vs. selling Pets). The red (dotted) user requests belong to the DVDStore application. The green (dashed) users requests belong to the PetStore application. 

In this example the DVDStore requests can be easily differentiated from the PetStore requests by the path in the URL (/dvdstore/...  vs. /petstore/...). Each of these two onlilne shops may have (potentually individual) different types of user requests like

  • visit the start page
  • search for products
  • view product details
  • put an item to cart
  • checkout cart
  • etc.
Each of this user request types is an own business transaction. Hence, one application comprises a set of business transactions.

Benefits of a Business Context Definition

  • No labels