Skip to main content



How does Architecture Dashboard work


How does Architecture Dashboard work


We recently updated this topic.

Let us know what you think with a thumbs up or thumbs down .

Architecture Dashboard is composed of 2 main pieces:

  • Architecture Dashboard Plugin - a LifeTime plugin that is published in a platform installation (on-premises or cloud) with probes to collect data and communicate with the SaaS.

  • Architecture Dashboard SaaS - a "Software as a Service" application that processes and shows all data collected from the Plugin.

Architecture Dashboard diagram


Communications between the Plugin and SaaS are always initiated by the Plugin. This reduces connectivity requirements on the customer side since all that is needed to be ensured is connectivity from the Plugin in LifeTime environment to a well known SaaS endpoint.

Data collected in Plugin and sent to SaaS

  • Platform metamodel data, including Infrastructure activation code, environments information (Name and Platform Version), teams and platform configurations.

  • Applications, Modules (eSpaces) for Code analysis and LifeTime Analytics data for Runtime Performance analysis.

  • Discovery snapshot data (Architectural references, applications, and modules) for Architecture analysis.

  • Users information: Name, Username, Email address, Last Login date (this is only communicated when the user accepts the agreement, after doing the association of the infrastructure username to Architecture Dashboard).

Data in transit

  • Data is exchanged between Plugin and SaaS in binary format through a well-known HTTPS endpoint.

  • There are no IP or DNS addresses being transmitted.

  • No ports besides the defaults need to be open for the correct use of Architecture Dashboard Probes.

  • No Firewall issues will arise, although the customer needs to be able to access the endpoint detailed in How to set up Architecture Dashboard.

Data at rest in SaaS

  • Data of each installation is kept isolated from all other installations using the platform's multi-tenant mechanisms. This ensures data from one installation is not accessible by users of other installations.
  • Was this article helpful?