Common issues with last activity updates

[Andrii_Logvin]

Common issues with last activity updates

Background

In addition to the Audit Log and Usage Analytics Model, Sisense also collects activity metrics in the system, for example, the lastActivity field of the user (can be found on the Admin -> Users page) and the lastOpened field of the dashboards (available in the dashboard tooltips).

Involved services

This functionality is handled by the galaxy and usage services in the installation.

Common issues

If the fields are not automatically updated in your installation, check the following:

If the usage service is in the Running state without recent container restarts:

kubectl get po -n sisense -l app=usage

Check whether tracking is enabled in your system configuration:

As an admin, navigate to the [Admin] > [Server & Hardware] > [System management] > [Configuration] page.

Click on the Sisense logo 5 times.

Select [Base Configuration].

Find and expand the [Tracking] tile.

Confirm that “tracking.enabled” flag is turned on.

Review galaxy logs for the following message:

[Error: [{"keyword":"format","dataPath":".ip","schemaPath":"#/properties/ip/format","params":{"format":"ipv4"},"message":"should match format \"ipv4\""}]

To view the logs, run the following command:

kubectl logs -n sisense -l app=galaxy –tail=-1 | less

If you spotted the aforementioned message, ensure that “Client port preservation” is turned off in your Load Balancer settings.

Use browser developer tools to view the network activity and check if browser extensions block any requests when you load Sisense. For example, /tracknavigation requests to the Sisense application.

The article addresses issues where the "Last Activity" field for users in Sisense may not update as expected. It highlights that the system collects activity metrics like the lastActivity of users and lastOpened of dashboards.

Related Resources

• https://docs.sisense.com/main/SisenseLinux/managing-dashboard-users.htm 

Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this please let us know.