- Release Notes
- Getting Started
- Access and Permissions
- Installation and Upgrade
- Interacting with Insights
- Historical data export
- Logs
- Performance and Scalability
Upgrading
To upgrade to a new version of Insights, you need to follow the steps based on your upgrading scenario.
- Please note that this is a change from our HW/SW specs from Insights 2021.10. Insights 2021.10 requires a single Windows machine, while Insights 2023.10 requires a Windows machine and a Linux machine with RHEL.
- If the customer uses the GPG key for any version prior to the April release (23.10.3, 23.4.6, etc.), they must upgrade using the same account/user that performed the initial install, or they will need to do a fresh install.
In 2021.10, the Insights Windows machine ran Docker which hosted the Looker Linux container. Starting with Windows 2022, the driver used to nest the Linux containers in Windows OS (called lcow) is not supported anymore by Microsoft for enterprise applications. As a result, we had to change our deployment architecture to require two machines - one Windows machine to run the UiPath Insights components, and a Linux machine to run the Looker container. With this change, enterprise support is available from OS vendors for the components needed to run UiPath products. The supported versions of Linux OS are the same that Automation Suite supports.
Both the Orchestrator and Insights versions need to match. For example, if you have upgraded Orchestrator to 2023.10.1, you need to run the same 2023.10.1 version of Insights to establish proper communication between the two UiPath products.
ProcessingExceptionDetails
and HostMachineName
columns. The installation might fail during the Insights Database migration if it has to index a large set of data.
Task | Description |
---|---|
1. Migrate users | When upgrading from a version earlier than 2021.10, users with Insights permissions are not automatically migrated to your new installation. They can be optionally migrated via the User Migration tool. |
2. Install the new Insights version on a separate machine from the existing installation | Follow the Insights Installation instructions to install it on a separate machine.
After you install the latest Insights version on a new machine, the ingestion of old data will stop. |
3. Uninstall the old version of Insights | Once you have completed the creation of the new custom dashboards and formulas on the newly installed version of Insights, you can safely uninstall the old version. |
- Both old and new Insights installations will use the same database while the dashboards are being moved.
- To login to Insights, you can use the old
https://<old Insights url>/app/account/login
URL and the same admin account that was configured during installation.
To disable the old builds, follow the steps below:
- Login to the old URL (
https://<old Insights url>/app/account/login
). - Go to
https://<old Insights url>/app/data
. - Click the three-dots icon on each cube and go to the build schedule to disable the builds.
Raw
Message
column in your database table.
The default nlog rule has changed. To find out more details check Default Log Rules for Versions 2022.4 and above page.
Task | Description |
---|---|
1. Review feature comparison |
Review the for functionality and feature comparisons from previous product versions before upgrading to 2022.10. |
2. Migrate users | When upgrading from a version earlier than 2021.10, users with Insights permissions are not automatically migrated to your
new installation. They can be optionally migrated via the User Migration tool.
If you already used the tool when upgrading to 2021.10, you do not have to re-run the user migration tool again. |
3. (Dashboard migration) Run LookerPreInstallationTool and export Looker volumes | When upgrading your Looker on the Insights Linux Machine, run the preinstallation tool from the Insights Windows Machine to
generate a ZIP file. Use the same procedure to run the Looker-initialization.sh script.
Make sure to export your Looker data (dashboards, views, and app settings), in Step 6 of the Looker Preinstallation tool section, to migrate your dashboards to the Insights Linux Machine. |
4. Install the new Insights version on a separate machine from the existing installation | Follow the Insights Installation instructions to install it on a separate machine.
After you install the latest Insights version on a new machine, the ingestion of old data will stop. |
5. Uninstall the old version of Insights | Once you have completed the creation of the new custom dashboards and formulas on the newly installed version of Insights, you can safely uninstall the old version. |
Upgrade steps
Before upgrading Insights to a higher version, make sure you:
- Check and upgrade Orchestrator version if needed. It's recommended for Orchestrator and Insights to be on the same version (Ex. Orchestrator version 2022.10.3 and Insights version 2022.10.3). Not having the same version impacts the application performance. To find out how to install Orchestrator check About Installation and About Updating if you wish to update your current version (minor-minor version must match).
- Have the MSI package and preinstallationtool.exe downloaded and make sure it matches between versions.(Ex. Orchestrator version 2022.10.3 , preinstallationtool for Insights version 2022.10.3). Check the Customer Portal > Product download page to download the required files or ask the support team.
To start the upgrade process follow the steps:
- Have the UiPath Orchestrator version upgraded to match the version of Insights.
- Have the MSI package and preinstallationtool.exe downloaded. Check the Customer Portal > Product download page to download the required files or ask the support team.
- Run and provide the requested information in the preinstallationtool. ( Linux Hostname, Certificate Thumbprint etc.)
- Copy the file generated by the preinstallationtool to the linux VM.
- Unzip the zip file from the preinstallationtool into the installation
directory.
- Locate the parent directory:
dirname $(sudo docker inspect looker-container | jq -r '.[0].HostConfig.Binds' | grep 'deploy' | awk -F':/app/.deploy:Z' '{print $1}' | awk -F'"' '{print $2}')
- Unzip to that directory:
unzip <looker zip file> -d <parent dir>
- Locate the parent directory:
- Run the looker-initialization.sh script.
bash insights/looker-initialization.sh -k <Public Key>
- Copy the generated file to the Windows VM.
- Run Insights MSI and provide the path to looker.json when the pop-up window is displayed.