Home » Product » Usage Scenarios » Application Dependency Mapping and Discovery

With the global distribution of applications, service orientation and virtualization, service and application dependencies become more and more volatile. Thus, maintaining static application dependency maps adds a lot of overhead to the day-to-day work of IT, which often means that they quickly get outdated. As a result, application dependencies quickly become impenetrable.

However, it is imperative to easily create a granular and up-to-date map of application dependencies whenever needed to understand the impact of

• Changing instances in server clusters
  Server instances are added/removed on demand – especially in virtualized environments – to adapt to workload resource consumption needs, meaning that transaction routes and involved server and application instances are in constant flux. In order to quickly react to performance problems with certain business transactions, a detailed understanding of all involved components is an absolute necessity.
• Application and service updates
  When services are updated their dependencies or interfaces may change, without notice to administrators. For example, with “service decoupling” app dev teams are more independent in their release cycles. However, such updates may break other dependent services or introduce new requirements to those newly used services.
• Problems in central application components and services
  Components central to many business-critical applications require lower performance thresholds and higher uptimes than those living on the periphery. Problems in those services also need to be resolved with highest priority.

dynaTrace helps you overcome these challenges as it screens complex application environments, automatically discovering application components and their interdependencies using 24x7 runtime transaction tracing at code-level even across system and technology boundaries. dynaTrace lets you quickly map out the dynamic transaction flow on demand and creates easily consumable UML charts. This run-time application dependency map then clearly shows you which application and business transaction is depending on which services – avoiding inefficient guesswork with complex application architectures and service registry mismatches.