When user action logs are enabled on TIBCO Spotfire Server, it is observed that the value in "LOGGED_TIME" is logged in UTC timezone regardless of the timezone set on spotfire server and the "Log in Local time" configuration. This happens when the Spotfire database is hosted on AWS platform.
 

The value in the LOGGED_TIME is never passed from the TIBCO Spotfire Server, it is calculated and inserted by the database itself, as a record of when the row actually got persisted. If the User Action database logger is set to log in local time, it is the local time of the database that gets logged.

In AWS, the default time zone for databases is UTC or may be set to a time zone different than the Spotfire Server machine time zone. To resolve, the time zone of the AWS database can be set to be in the same time zone as the Spotfire Server, according to this AWS article: https://aws.amazon.com/premiumsupport/knowledge-center/rds-change-time-zone

Though "Log in Local time" is enabled on Spotfire server, LOGGED_TIME field is logged in UTC timezone where as ORIGINAl_TIME is logged based on the timezone set on Spotfire server. This article will give explain the reason behind the issue.

External: How do I change the time zone of my Amazon RDS DB instance?

• https://aws.amazon.com/premiumsupport/knowledge-center/rds-change-time-zone

Doc: Action log generic entries

• https://docs.tibco.com/pub/spotfire_server/10.3.9/doc/html/TIB_sfire_server_tsas_admin_help/GUID-B2D68E5C-4D4A-460C-9A91-E1CF3E5B7D14.html