Action logs with LOG_CATEGORY 'monitoring' and the LOG_ACTION 'measurement' missing when querying the Action log database.

Action logs with LOG_CATEGORY 'monitoring' and the LOG_ACTION 'measurement' missing when querying the Action log database.

When you query the Action log database for the Spotfire you will find some of the entries in the result set as:



However, if you query your Action log database again after a couple of hours. You will find that these rows which were logged earlier are now missing. This is the expected behavior for these logs with the LOG_CATEGORY 'monitoring' and the LOG_ACTION 'measurement'.

There is a parameter/configuration in the user-action log in the configuration.xml, "monitoring-retention-span".
This parameter is set to a value(in hours): The length of time monitoring entries should be saved before they get crunched into averages.

By default, this --monitoring-retention-span=value is set to 1 hour, after which these monitoring logs are crunched into their average values.

The LOG_ACTION monitoring is crunched into the averages for the last hour if the value is set to default.

If you try to increase the default value to a higher value you will find those logs in the Action log database. However, increasing the default value might fill up the disk space by increased number of the rows/logs database. config-action-log-database-logger
https://docs.tibco.com/pub/spotfire_server/7.13.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-F2CA650D-521E-483D-8594-0CCA82D68B93.html