Insights Is Missing Data

How to resolve when Insights is missing data or process specific tables?

Troubleshooting Steps

  1. To diagnose the issue start by making sure that Orchestrator is digesting the logs and sending them to the Insights database.
    • In order for this to occur, the Orchestrator license needs to be moved to the host tenant
    • Login to Orchestrator and select the tenant that Insights should be enabled for
    • Click insights. If it says feature not licensed, then the license most likely needs to be moved to the host tenant
    • If Insights loads, and the Orchestrator version is 20.10, go to the licensing page in Orchestrator
      • Tenant->License
    • It should say the license is uploaded to host, if it does not, go to the section - Uploading License to Host
      • When its uploaded to host, it looks like this:image.png
  2. If the license is correct, next check the event viewer logs on Orchestrator. Every 15 minutes there should be an event related to log ingestion.
    • Open the Event viewer (Run->eventvwr)
    • Click Find or prest ctrl+F and search for the key word "Ingest"
    • This should return Orchestrator events related to ingesting. If this returns, then that means Orchestrator is sending the data to the Insights database.
      • An example log message: Ingesting data for (1, IngestQueueSpecificData, IngestQueueOutputData, IngestQueueAnalyticsData)
    • If this is not present and the license is uploaded to the host tenant, check for exceptions related to the key word 'Sisense'
    • If there is an exception like: "UiPath.Orchestrator.Analytics.SiSense.SisenseHttpClientException: Sisense request https://insightserver/api/v1/live_connectors/UiFrost/table_schema_details/ returned unsuccessful response StatusCode: 500," then that means the UiPath Custom data connector is not working properly. Go to the section - Fixing the Data Connector
  3. If the above steps do not reveal the issue, check the Insights DB to make sure it is receiving new data. Best place to check is the Queues table or the License table. Just sort the table by timestamps. However, most likely it is receiving data (if its not, it most likely means that the wrong DB is being looked at)
  4. Next, check the build status of Insights:
    • Login to Orchestrator or login to the insights admin at https:///app/account/login
      • Admin account will show the status of everything
    • After logging in go to https:///app/data. This will show the status of all the cubes.
    • Check to see if any of the build statuses have failures. If they do, go to the section - Resolving Build Errors
  5. If the build looks successful and the missing data is related to custom tables, verify that the processes were whitelisted by referring Manage Custom Tables
  6. Also make sure to read Adding Custom Data To Insights . It is very common that there is a misunderstanding of what data gets imported into insights for custom process logs.
  7. Finally, if the issue is related to custom data, go to the section - Fixing the Data Connector.

Uploading License to Host

  1. Make sure to understand the difference between the host and other tenants.
  2. Make sure to have the license code handy.
  3. It is OK to reach out to UiPath for help with this activity. Most times the switch is trivial but if Orchestrator had to be activated offline, then an issue can occur where the license does not get deactivated on our system and the licenses can not be re-activated. For an issue like this, our license team has to clear the deactivations.
  4. Open a regular browser and incognito browser.
  5. On the regular browser, login to the the Default tenant.
  6. On the incognito browser login to the host tenant.
  7. In the regular browser, go to Tenant->License and remove the license (just click remove)
  8. On the incognito browser go to License and upload the license.
  9. After uploading the license, select allocate and allocate the licenses to the correct tenant. Read Managing Licenses .
Fixing the Data Connector
  1. Check the connector logs on the Insights machine.
    • %programdata%\Sisense\DataConnectors\JVMContainer\Connectors\UiFrost\Connector.log
  2. The most common error is: Could not start connector. com.sisense.connectors.exceptions.ConnectorException: Could not connect to SiSense.
    • This error means that the Insights HTTP certificate is not in trusted root on the insights machine.
    • Try importing the certificate to trusted root.
    • Open certlm.msc from the Windows Search bar.
    • Go to the personal node, right click the certificate used by Insights and select 'Open'. Then go to the Details section and select 'Copy To File'.
      • When asked if the private keys should be exported, select 'No'.
    • After this is done, double click the .CER file and import it into Trusted Root. Read Using Certificate for Https Protocol .
    • Wait at least 15 minutes and see if the connector log starts to work as expected.
  3. If the log just says: Scanning for Schema Change Requests, that means that no processes are whitelisted. To fix this whitelist the needed processes.
  4. For any other errors, address them as makes sense or open a ticket with UiPath.
    • For SQL string connection errors, the connection string for this connector can be modified at: C:\Program Files\Sisense\DataConnectors\JVMContainer\Connectors\UiFrost\
    • The following types of connection strings would need to be changed
      • insights.db.conn=jdbc:sqlserver://,1433;Database=insights;user=uipath
      • JDBC connection strings do not support commons for specifying the port. Switch it to a colon ":"
      • Should be: insights.db.conn=jdbc:sqlserver://;Database=insights;user=uipath
      • insights.db.conn=jdbc:sqlserver://servername\instance:1433;Database=insights;user=uipath
      • The slash between instance needs to be escaped
      • Should be: insights.db.conn=jdbc:sqlserver://servername\\instance:1433;Database=insights;user=uipath
  5. If using 19.10.6, see corresponding Release Notes .

Resolving Build Errors

  1. After logging into Insights go to https:///app/data
  2. Select the failing cube.
  3. On the right hand side, click the three-dotted icon and select "View Latest Logs"
    • image.png
  4. Next, try to rebuild the cube. To do this click the build button. Which clicking the button, select 'Replace All'
    • image.png
  5. If a rebuild works, things should be good. Its OK if a build fails as long as it recovers.
  6. If the error is "Schema of the requested table has been changed," then do the following:
    • Run a build. Once the build fails, check the errors. It should list a table that caused the build to fail.
    • Find the table on the right hand side and then select delete or refresh (either should work. Start with a refresh and then try a delete). The table should be under the UiPath Analytics data source.
      • If for example the schema change was related to a table called Process-CustomLogInfo-1 it would be deleted as shown in the screenshot below. (Click the 3-dotted icon to see the option to delete)
      • This might have to be done a few times on different tablesimage.png
  7. If the issue is still not resolved, open a ticket with UiPath Support.
  8. As a best practice setup build alerts to catch these issues faster in the future:
    • Go to https://<Insights URL/app/settings
    • Select Data Sources
    • On the top right, select "Add Build Alert"
    • If Emails are configured, build alerts will be sent via email.
    • All build alerts will also show up under the pulse tab.
    • Make sure to add whoever manages Insights to the build alert.
DB schema issue -
The .[dbo].QueueItems.ProcessingExceptionDetails has a column length of 400 characters, however Orchestrator has it defined as varchar(max) .

Resolution: This has been fixed in 22.10 CU, however this has been found as a bug in 22.10.3 version.

The below query will solve the issue with this mismatch-