Planning Analytics

Hi Roei,

This is a known timezone mismatch between PAW's log viewer and the raw log file. TM1 server logs default to GMT timestamps regardless of your server's OS timezone setting. PAW's log viewer displays those GMT timestamps as-is, so if you're comparing them to something displayed in local time, they'll look off.

The fix is in your tm1s-log.properties file, located in the same folder as tm1s.cfg. Find or add this line:

log4j.appender.S1.TimeZone=Local

This tells the TM1 server to write log timestamps in the local server time instead of GMT. The parameter accepts only two values, GMT or Local. If it's missing entirely, it defaults to GMT. If the file doesn't exist yet, create it in your TM1 config folder with that parameter.

One important note: this only controls the tm1server.log (server message log). The tm1s.log transaction log timestamps are always GMT and can't be changed through this setting.

If you're on PAaaS, you won't have direct file access and will need to open a support case with IBM to apply this change.

Hope that helps.

Hi Tyler,

Thanks for your answer.
This is not the case. My parameter is already set to Local and server files includes the correct timestamp.
However, the PAW time is not GMT.
My local time is GMT+3 but in PAW I see GMT+6

Roei

Hi Roei and Tyler,

As download the file happen from the server where no browser is involved, the time is shown correctly.

However, the developers see the log viewer in Workbench in the browser where the user's timezone is applied.

I'm not shure why such a big difference (3 hours),  worth to check your timezone.

Best regards,