How does Architecture Dashboard work
Architecture Dashboard is composed of 2 main pieces:
-
Architecture Dashboard Plugin - a LifeTime plugin that's 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.
Communication
Communications between the Plugin and SaaS are always initiated by the Plugin. This reduces connectivity requirements on your side since all that needs to be ensured is connectivity from the Plugin in the LifeTime environment to the Architecture Dashboard SaaS endpoint.
Data collected in Plugin and sent to SaaS
Architecture Dashboard collects the following data from your infrastructure:
-
Platform metamodel data, including the infrastructure activation code, environments information (name and Platform Server version), teams and platform configurations.
-
Applications, modules for code analysis and LifeTime Analytics data for runtime performance analysis.
-
Discovery snapshot data (architectural references, applications, and modules) for architecture analysis.
-
Upon acceptance of the agreement, during Architecture Dashboard set up: users information (name, username, email address, last login date).
Data of each installation is kept in the OutSystems cloud and 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.
Data in transit
-
The Plugin and SaaS share data in binary format through a well-known HTTPS endpoint.
-
IP or DNS addresses aren't transmitted.
-
No ports besides the defaults need to be open for the correct use of Architecture Dashboard Probes.
-
No firewall issues should arise, although you need 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 isn't accessible by users of other installations.
More information about security and compliance
Read more about security and compliance in the following FAQ sections:
Architecture Dashboard administrator
Architecture Dashboard considers an IT user an administrator in the following cases:
-
The IT user has the default administrator role for the infrastructure.
-
The IT user belongs to a team and has the default administrator role for the team.
Only administrators can update probes and other maintenance tasks in Architecture Dashboard.