The Cube:
Represents traces and logs

A click, a write, a load, anything.

A cube represents something that is occurring in an application, ecosystem or problem space. Examples of this could be clicking a button or loading a web page.

A single cube represents a single operation or a single span.

A stack of cubes represents logically related operations or a trace, such as resetting a password or updating UI.

Related cubes form a stack. Together they create a flame-graph usable for further troubleshooting and diagnosis.

The grid:
Where traces and logs are displayed

Intuitive navigation through actions and actors in the application, ecosystem or problem space.

The grid of Immersive APM shows operation throughput and overall flow.

Simple status colors of the cubes allows users from the grid to visualize how their system is performing.

In a live ecosystem, one can expect a mix of status colors. When your grid is empty, the application is idle.

The topology:
Logical operators in the ecosystem

Logical operators in the ecosystem.

The topology is where you see the performers, actors or consumers of the operations in the application, ecosystem or problem space.

A platform in the topology graph represents a single application. Those could be APIs, worker roles or their dependencies.

The topology view updates dynamically as the different roles communicate with each other giving you a real-team representation of communication flow and throughput.