The article describes methods and tools for collecting diagnostic information of the BRIX application. With the collected data, it is possible to identify potential errors and slowdowns in the system, optimize page loading speed, etc.
HAR log collection
To track the process of loading pages and other resources, use HAR logs. These logs record all browser actions related to loading apps or web pages. For a list of supported browsers, see the Workstation requirements article. Instructions for collecting HAR logs are available in the help documentation for the used browsers.
Platform diagnostics
After collecting HAR logs, run platform diagnostics to detect errors. Depending on your edition, follow the corresponding link, activate the diagnostics mode and collect service logs for further analysis:
If you are not sure which edition you have, you can determine it by following the steps below:
- Connect to server with BRIX using SSH.
- Execute a command for determining edition:
- If it’s Kind edition, the following command will display the list of installed services:
docker exec elma365 kubectl get pod –A
- If it’s Helm edition, the following command will display the list of installed services:
kubectl get pod -A or helm list –A
- If it’s MicroK8s edition, the following command will display the list of installed services:
microk8s kubectl get pod –A
The list will look like this:
