0031177: Time in Process Monitor || Process Request || Process Log is the server time instead the user time

Notes
(0081163) alostale (manager) 2015-10-21 08:51 edited on: 2015-10-21 12:31	The problem is process log is saved as plain text, including for each line a timestamp within server's timezone. Displaying this timestamp in client's timezone is not possible without parsing and converting it in client side. Different approaches could be implemented, though none of them would be optimal: 1. Log text is saved as it is now and parsed in client to convert it to local timezone. This should be done both in grid and form views. Problem: * It could lead to performance problems in browser. * Big implementation effort 2. Process log is not saved as plain text but in a new table where each line is a record with two fields: text and time. In this manner standard time conversion would be performed. Problems: * Major change in the manner log is created and visualized * Possible performance issues due to massive records generation in this new table * Backwards compatibility: old logs wouldn't be migrated to new system, so they could not be visualized anymore. 3. Log timestamp is created in client's timezone instead of sever's one. Problems: * We would still have the same problem when logs are visualized from clients in different timezones * From browser it is possible to know current offset with UTC but not timezone. This would mean processes scheduled in timezones with DST would be incorrectly logged after time change, this would mainly affect to recurring scheduled jobs. 4. Keep current logging including current timezone info. In this way a line like: "2015-10-21 08:46:49.16 - Starting background process." would be created as "2015-10-21 08:46:49.16 CEST - Starting background process.". This would, at least, make visible the actual timezone the log is for. Problems: * There is no immediate time transformation but user needs to do the calculations if needed * Not backwards compatibility: existing logs would be kept as they are now 5. Log elapsed time since the process started instead of date time. As start time is also displayed in the same window properly translated to client's time zone, complete information would be available. Problems: * Behavioral change: now process time instead of timestamp would be shown * Not backwards compatibility: existing logs would be kept as they are now

Issue History
Date Modified	Username	Field	Change
2015-10-19 19:15	amayavicente	New Issue
2015-10-19 19:15	amayavicente	Assigned To	=> Triage Finance
2015-10-19 19:15	amayavicente	Modules	=> Core
2015-10-19 19:15	amayavicente	Triggers an Emergency Pack	=> No
2015-10-19 19:17	networkb	Resolution time	=> 1446418800
2015-10-20 09:30	vmromanos	Assigned To	Triage Finance => platform
2015-10-20 12:37	eduardo_Argal	Resolution time	1446418800 =>
2015-10-20 12:37	eduardo_Argal	Type	defect => design defect
2015-10-21 08:51	alostale	Note Added: 0081163
2015-10-21 08:51	alostale	Status	new => acknowledged
2015-10-21 12:31	alostale	Note Edited: 0081163	View Revisions
2022-02-01 08:09	alostale	Assigned To	platform => Triage Platform Base

Relationships [ Relation Graph ] [ Dependency Graph ]