- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to Troubleshoot Services During Installation
- How to Uninstall the Cluster
- How to clean up offline artifacts to improve disk space
- How to Disable TLS 1.0 and 1.1
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bundle
- How to debug failed Automation Suite installations
- How to disable NIC checksum offloading
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Kinit: Cannot Find KDC for Realm <AD Domain> While Getting Initial Credentials
- Kinit: Keytab Contains No Suitable Keys for *** While Getting Initial Credentials
- GSSAPI Operation Failed With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis Probe Failure
- RKE2 Server Fails to Start
- Secret Not Found in UiPath Namespace
- ArgoCD goes into progressing state after first installation
- Unexpected Inconsistency; Run Fsck Manually
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Adding a dedicated agent Node for Task Mining
Before starting the Task Mining installation, make sure to check the Hardware requirements. Task Mining has a dependency on AI Center; therefore, to use Task Mining, you must also install AI Center.
After completing the Automation Suite installation, take the following steps to set up Task Mining.
If you already enabled Task Mining in the configuration during the main install, you can skip this step. If not, you need to enable AI Center and Task Mining by editing the configuration and rerunning the install.
cluster_config.json
during installation in the Advanced Configuration step.
aicenter
and task_mining
should be added as enabled in cluster_config.json
.
cluster_config.json
Task Mining config
{
"aicenter": {
"enabled": Boolean
},
"task_mining": {
"enabled": Boolean
}
}
{
"aicenter": {
"enabled": Boolean
},
"task_mining": {
"enabled": Boolean
}
}
Follow the steps for configuring a server node to ensure the disk is partitioned correctly.
For online installation
SSH to the right machine:
- If you added Task Mining to a single-node evaluation install, go to the machine and run this next step.
- If you added Task Mining to a multi-node HA-ready production install, go to any of the server nodes.
UiPathAutomationSuite
folder to the Task Task Mining node (username and DNS are specific to the Task Mining node):
sudo su -
scp -r /opt/UiPathAutomationSuite <username>@<node dns>:/opt/
scp -r ~/* <username>@<node dns>:/opt/UiPathAutomationSuite/
sudo su -
scp -r /opt/UiPathAutomationSuite <username>@<node dns>:/opt/
scp -r ~/* <username>@<node dns>:/opt/UiPathAutomationSuite/
For offline installation
SSH to the primary installation node
UiPathAutomationSuite
directory contains sf-infra.tar.gz
file ( is a part of the installation package download step )
scp -r ~/opt/UiPathAutomationSuite <username>@<node dns>:/var/tmp
scp -r ~/opt/UiPathAutomationSuite <username>@<node dns>:/var/tmp
For online installation
SSH to the Task Mining Node and run the following commands:
sudo su -
cd /opt/UiPathAutomationSuite
yum install unzip jq -y
CONFIG_PATH=/opt/UiPathAutomationSuite/cluster_config.json
UNATTENDED_ACTION="accept_eula,download_bundle,extract_bundle,join_task_mining" ./installUiPathAS.sh
sudo su -
cd /opt/UiPathAutomationSuite
yum install unzip jq -y
CONFIG_PATH=/opt/UiPathAutomationSuite/cluster_config.json
UNATTENDED_ACTION="accept_eula,download_bundle,extract_bundle,join_task_mining" ./installUiPathAS.sh
For offline installation
Connect via SSH to the Task Mining dedicated node & install the platform bundle on it using the script below.
sudo su
mv /var/tmp/UiPathAutomationSuite /opt
cd /opt/UiPathAutomationSuite
sudo chmod -R 755 /opt/UiPathAutomationSuite
sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j task-mining --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp --install-offline-prereqs --accept-license-agreement
sudo su
mv /var/tmp/UiPathAutomationSuite /opt
cd /opt/UiPathAutomationSuite
sudo chmod -R 755 /opt/UiPathAutomationSuite
sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j task-mining --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp --install-offline-prereqs --accept-license-agreement
Run below command to set the kubectl context on taskmining machine
sudo su -
export KUBECONFIG=/var/lib/rancher/rke2/agent/kubelet.kubeconfig
export PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get nodes
sudo su -
export KUBECONFIG=/var/lib/rancher/rke2/agent/kubelet.kubeconfig
export PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get nodes
You should see the nodes and their corresponding names. You need the name of the Task Mining node for the next step.
Finally, run the following command to check if the Task Mining node is configured. Please update the \<node name\> with Task Mining node name in below command.
kubectl describe node <node name> | grep -i "taints"
kubectl describe node <node name> | grep -i "taints"
Above command should return you the following output
At this point, you have successfully completed the installation for Task Mining. Sign in to the Automation Suite Portal and enable it in the tenant management UX under the Admin section.
You must configure system email notifications as Task Mining relies on the Automation Suite notification system to send emails.
For instructions on creating a Task Mining project, see the Task Mining documentation.
Follow the steps for the given deployment type, online or offline.
Before proceeding with the steps below, it is mandatory to start with following the steps from Uploading ML Packages.
After uploading the ML package, follow the listed steps:
5. Name the package, choose the most recent package version, and click Submit to create a machine-learning deployment package.
As Task Mining is a data-heavy application, we recommend an additional 1024 GiB of storage to handle the screenshots and metadata collected during studies. After adding a secondary disk, you must resize the Longhorn storage to incorporate it.
You can add the additional disk either pre- or post installation. If you add it post-installation, you must take additional steps to configure the new disk in the cluster.
For details, see Configuring new data disk in the cluster.
UiPathAutomationSuite
folder and run the following command:
sudo su -
cd /opt/UiPathAutomationSuite
sudo ./configureUiPathAS.sh objectstore resize-pvc --size 1000Gi --sub-component data
sudo su -
cd /opt/UiPathAutomationSuite
sudo ./configureUiPathAS.sh objectstore resize-pvc --size 1000Gi --sub-component data
- Hardware requirements
- Enable Task Mining on the Cluster
- Editing the Configuration
- Configuring a Dedicated Node for Task Mining
- Step One: Configure the Machine
- Step Two: Copy the Interactive Installation Wizard to the Target Machine for Installation
- Step Three: Run the Interactive Install Wizard to Configure the Dedicated Node
- Step Four: Enabling Kubectl
- Step Five: Verifying Task Mining Configuration
- Configuring email
- Starting a Task Mining project
- Configuring the Task Mining ML Model in AI Center
- Online and Offline Installations
- Increasing secondary disk/Longhorn storage
- Configuring a new disk in the cluster
- Increasing storage capacity