Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The Immuta Support section includes guides to troubleshoot issues with the Immuta application.
Background Jobs: These pages include SQL queries that allow you to examine Immuta's various background jobs.
Application Logs: This page details accessible logs of various Immuta components, necessary for administrators who need to troubleshoot installation issues with the Immuta application.
Fingerprint Service Timeout: This page details a tutorial about the Fingerprint Service in Immuta, which shows how to increase the timeout threshold for the service.
Audience: Data Users
Content Summary: This page shows users how to identify background jobs that take too long to run.
Below is a SQL query, which will help determine background jobs that take too long to run.
Note: This query unions the job and archive table. Adjust the top interval appropriately for your needs.
Run the following SQL query to determine background jobs that take too long to run.
Audience: Data Users
Content Summary: This page details how to terminate long-running or hanging SQL commands or queries.
Below is a SQL Query, which contains instructions to help terminate long-running SQL commands or queries.
Note: This query excludes START_REPLICATION SLOT %
.
Use the inner select to determine if you have hanging queries, and replace pg_cancel_backend
with pg_terminate_backend
if they do not actually cancel. You can also change the interval if needed.
Audience: System Administrators
Content Summary: This page shows how to determine when Immuta background jobs will complete.
Below is a SQL query, which will help determine when some background jobs will be complete.
Note: This query unions the job and archive table. Adjust the top interval appropriately for your needs. In addition, collections of jobs aren’t typically differentiated. For example, if you hit LDAP three times, that is one collection of jobs, not three.
Avg Time: The value for the average time will have a standard deviation applied to it.
Duration: How long it has been running for. If this reads towards 12 hours, then this value is longer than the reported value.
Until Complete: How long it will take to complete the remaining queue. This is assuming the job is the only active job to utilize all of the web pods.
When EDT: When the jobs will be completed. This is assuming the job is the only active job to utilize all of the web pods.
Run the following SQL query to investigate Immuta's background jobs.
For further instruction on how to monitor background jobs, refer to this video.
Audience: System Administrators
Content Summary: This page provides a SQL query that determines batches of background jobs.
Below is a SQL query, which will help determine batches of background jobs.
Note: This query unions the job and archive table. Adjust the top interval appropriately for your needs.
This query is for all 2022.1 versions of Immuta and above.
Audience: System Administrators
Content Summary: This page outlines commands to retrieve Helm values, pods, and logs of various Immuta components (such as the Fingerprint Service or Immuta Web Service) to identify installation issues.
Note: You can enable debug logging for the Fingerprint Service in the Helm Chart with fingerprint.logLevel: DEBUG
.
Note: You can change the value of the log level to DEBUG
for Patroni in the Helm Chart for the Database and Query Engine pods by using the following values:
database.patroniLogLevel: DEBUG
database.patroniRequestsLogLevel: DEBUG
queryEngine.patroniLogLevel: DEBUG
queryEngine.patroniRequestsLogLevel: DEBUG
Occasionally, the size of a table can cause the fingerprint service to repeatedly fail. Without a valid fingerprint, data sources show as Not Healthy in the UI, and you cannot apply advanced privacy enhancing techniques on those data sources.
To address this issue, you can increase timeout settings for the fingerprint service in Immuta.
As a user with the APPLICATION_ADMIN
permission in Immuta, navigate to the App Settings Page.
Scroll to Advanced Configuration.
Enter the following configuration to increase the timeout threshold for the fingerprint service. Entries in the Advanced Configuration must adhere to YAML syntax. Read more here for YAML syntax details.
Note: Timeout is set in seconds. The above example is a 20-minute timeout.
Click Save and confirm your changes.
Audience: System Administrators
Content Summary: This page contains support for administrators who are trying to determine the change in performance over a given duration for background jobs.
Below is a SQL query, which will help determine the change in performance over a given duration for background jobs.
SELECT INTERVAL '1 hour' AS duration.
The duration of the interval can be altered, though durations of 12 hours are not advised.
/ : The average duration increased.
\ : The average duration decreased.
Run the following SQL query to determine the change in performance over a given duration for background jobs.