Skip to end of banner
Go to start of banner

Representation of collected data

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 10 Current »

This page describes all problems, tasks and solution approaches regarding the representation of the collected data.

Main topics

  • How to represent the collected data in a good readable manner?

Current solution (state)

(Previous solution approaches regarding this topic were already discussed in the master thesis.)

In the thesis were two models found:

  • Layer View
  • Red Gate Software View

New approaches / solution

Coming soon...

Questions / Possible Problems

  1.  How should the data be displayed?
  • Tab switch between the different CMR (probably the easier solution)
  • The sequence is displayed directly on one view. (Like Red Gate...)
From brain dumb

How do we want to display invocation sequences over multi nodes

  • We need to differentiate between synchronous response time (that the user sees) and complete runtime (including the time of all asynchronous calls)
  • Dynatrace visualized inter thread/VM calls as an extra node "synchronous call" or "asynchronous call" (which can have multiple children). AppDynamics allows to "jump" to the invocation sequence that represents the connected invocation sequence, meaning that the invocation sequences are not displayed as one, but the user must navigate.

 

  • No labels