In 15.x, how are you finding specific event logs? The timestamps are wrong

In TDX 15.1 and 15.2, the event logs can no longer be reliably sorted because the timestamp behavior has changed. The "Date Created" and "Date Modified" columns now display the user-specific timestamps (the timestamp of the user that kicked off the event – not the timestamp of the user logged into the web UI to review the logs), so it's really hard to find the right log when you have a globally distributed team. It should sort by system timestamps only.

Has anyone come up with a workaround for this, or am I missing something fundamental?

emoji
Parents
  • Hi all, can I add that I'm confused as well :) Allow me to give some history and hopefully that allows a rephrase of the problem statement...

    Up to and including Tridion Docs 15.1.X the date time format has to be DD/MM/YYY and time format to 24-hour clock HH:mm:ss

    Even when we migrated technology (React+OpenAPI) and the new Organize Space experience in the 15.0.0 and 15.1.x releases, we requested a fixed date time format. This because we reused the older technology (ASP.NET MVC) in 15.1.x and earlier and it would be very confusing if some screens showed the local user's format and other screens would show the server system user's format.

    Therefor from the below screenshot, it looks like your date time format is set to English (United States). And that screen layout is rendered by the somewhat older ASP.NET MVC engine - hence 15.1.x or earlier. This must be set to English (United Kingdom) as stated in step "Set the language and region of the InfoShare user" of https://docs.rws.com/en-US/tridion-docs-main-documentation-1151795/establishing-a-dedicated-system-user-127303 In turn 24-hour clock is sortable. [SRQ-28150]

    Starting Tridion Docs 15.2.x the date time format is part of your localization, so chosen by the user's preferences.

    The migration towards the new technology (React+OpenAPI) in the Organize Space component finished in 15.2.0. No more ASP.NET MVC rendered screens. And we activated the possibility that every user could chose their localization regarding language and culture. This is the same behavior as in the Client Tools like Publication Manager. So somebody modifying an object 10:20AM EDT when in Boston, would be displayed as at 15:20 in the UK (if I did my math correctly).

    More information in  Tridion Docs 15.2 Bootcamps >  Tridion Docs 15.2.0 (Alf2) Bootcamp 3of3 - Organize Space > https://youtu.be/kMvz_2gxQyI?t=6523 

    I hope the above clarifies something for you both. If not, then please try to rephrase the question with some examples or so. And if possible, please add the full version number as it is the shortest bit of information that describes the (expected) behavior of a system.

    Best wishes,
    Dave

    emoji
  • We (Elizabeth and I) are using RWS Tridion Docs version 15.1.2/15.1.6328.2.

    The experience we had with the web client event viewer in Tridion Docs 14.x and earlier was event times were fixed to the location of the server, using a 24 hr clock. And the events were ordered properly (the most recent events were shown as the most recent events in the table).

    Now, when we review publish and other events in Organize Space, the event times are fixed to the location of the server using a 12 hr clock (using am and pm). Hovwever (I assume due to the clock change) the event times that appear in the table are all over the place as described above. If I publish a job at 7:05 am today and then publish a job later today at 7:00 pm I expect the 7:00 pm job to the shows as more recent. But the table lists 7:05 today as later than 7:00 today because it's ignoring am and pm. That is the issue that needs to be fixed (at least in our Organize Space). There is no problem with the ordering of dates, just event times in a day.

    emoji
Reply
  • We (Elizabeth and I) are using RWS Tridion Docs version 15.1.2/15.1.6328.2.

    The experience we had with the web client event viewer in Tridion Docs 14.x and earlier was event times were fixed to the location of the server, using a 24 hr clock. And the events were ordered properly (the most recent events were shown as the most recent events in the table).

    Now, when we review publish and other events in Organize Space, the event times are fixed to the location of the server using a 12 hr clock (using am and pm). Hovwever (I assume due to the clock change) the event times that appear in the table are all over the place as described above. If I publish a job at 7:05 am today and then publish a job later today at 7:00 pm I expect the 7:00 pm job to the shows as more recent. But the table lists 7:05 today as later than 7:00 today because it's ignoring am and pm. That is the issue that needs to be fixed (at least in our Organize Space). There is no problem with the ordering of dates, just event times in a day.

    emoji
Children
No Data