- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- Configuring the machines
- Configuring the external objectstore
- Configuring an external Docker registry
- Configuring the load balancer
- Configuring the DNS
- Configuring Microsoft SQL Server
- Configuring the certificates
- Online multi-node HA-ready production installation
- Offline multi-node HA-ready production installation
- Disaster recovery - Installing the secondary cluster
- Downloading the installation packages
- install-uipath.sh parameters
- Enabling Redis High Availability Add-On for the cluster
- Document Understanding configuration file
- Adding a dedicated agent node with GPU support
- Adding a dedicated agent Node for Task Mining
- Connecting Task Mining application
- Adding a Dedicated Agent Node for Automation Suite Robots
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Product-specific configuration
- Remapping the organization IDs
- Migrating Looker data to Automation Suite
- Performing Insights database maintenance
- 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 clear Redis data
- 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 disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable TX checksum offloading
- How to manually set the ArgoCD log level to Info
- How to generate the encoded pull_secret_value for external registries
- How to address weak ciphers in TLS 1.2
- 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
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure after certificate update
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- GPU node affected by resource unavailability
- Volume unable to mount due to not being ready for workloads
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to resize PVC
- Failure to resize objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Authentication not working after migration
- 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 due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- ArgoCD login failed
- 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
- Issues accessing the ArgoCD read-only account
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- Unable to connect to AutomationSuite_ProcessMining_Warehouse database using a pyodbc format connection string
- Airflow installation fails with sqlalchemy.exc.ArgumentError: Could not parse rfc1738 URL from string ''
- How to add an IP table rule to use SQL Server port 1433
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Performing Insights database maintenance
dbo
and read
. Both tables store data from Orchestrator databases and pass data between each other. Over time, tables store a large amount
of data that can impact database performance. You can free up space by removing data that is not relevant or outdated.
The estimated threshold for storing historical data is set to
- 200 million RobotLogs
- 100 million QueueItemEvents
- 100 million JobEvents
- 20 million QueueItems
- 20 million Job
[dbo].Jobs
, [dbo].JobEvents
, [dbo].QueueItems
, [dbo].QueueItemEvents
, [dbo].RobotLogs
tables, or just the [dbo].RobotLogs
.
PROCEDURE
[read].[Delete_Insights_Data_Read]
and PROCEDURE
[read].[Delete_Process_Logs_Read]
scripts, the Insights module needs to be
disabled.
- Scripts with the
_DBO
suffix are used to delete data from DBO schema tables, - Scripts with the
_Read
suffix are used to delete data from Read schema tables. - Large-sized batches might impact the speed of execution. Consider using the default batch size, which is set to 100000.
PROCEDURE [read].[Delete_Insights_Data_Read]
and
PROCEDURE [read].[Delete_Process_Logs_Read]
scripts, the Insights module
needs to be disabled.
Jobs
, JobEvents
, QueueItems
, QueueItemEvents
, RobotLogs
) for a cut-off timestamp.
SQL Stored Procedures | Parameter | Description |
---|---|---|
Delete_Insights_Data_DBO |
| Delete data from [dbo].[Jobs] ,
[dbo].[JobEvents] , [dbo].[QueueItems] , [dbo].[QueueItemEvents] , [dbo].[RobotLogs] tables based on a cut-off timestamp.
|
Delete_Insights_Data_Read | N/A | Truncate [read].Jobs , [read].JobEvents ,[read].QueueItems , [read].QueueItemEvents , [read].RobotLogs tables.
|
The Insights Dashboard widgets are available again after SQL Stored Procedure 1 has finished, and the data has been backfilled. Keep in mind that the backfill process may take hours to complete given that you have a large amount of data.
Delete_Insights_Data_DBO
SQL Script, it creates a QueueItems.IX_CreationTime
nonclustered index with the purpose of making future executions faster.
Generate and save this SQL Stored Procedure to delete RobotsLogs based on ProcessNames and Tenant ID.
SQL Stored Procedures | Parameter | Description |
---|---|---|
Delete_Process_Logs_DBO |
The Orchestrator process name.
Tenant ID is required as two tenants might run processes with identical names.
Delete data in batches of 100000. See Considerations. | Delete data from [dbo].[RobotLogs] table by ProcessName and Tenant ID.
|
Delete_Process_Logs_Read |
| Truncate [read].RobotLogs table.
|