Time zone control over timestamps inside logging messages
Description
Environment
Activity
Scott Cantor April 21, 2020 at 2:09 PM
I can't really recall the specific annoyance that led to this, so unless I run across a clear need again, I'll just leave it at auditing and move on.
Scott Cantor March 5, 2016 at 1:39 AM
Just for the record, I did a bit of this at the Audit logging layer by adding more features there, but didn't factor it out into an actual bean to handle lower layers.
Scott Cantor October 2, 2014 at 3:14 PM
I have not, but I still think it's worth doing. What we need to add is a bean that handles "translation" of DateTime objects into a string, and then attach the desired formatting and time zone use to that object. Then we need to try and sweep the code where we can for DateTime output into logs (audit is easy, the process log is harder) and inject this bean into the components doing the logging.
So it's not hard exactly, but a little invasive, and it hits lower layers since a lot of this is the services and metadata logging things about refresh times.
We can discuss tomorrow on the call and decide.
Rod Widdowson October 2, 2014 at 3:08 PM
Again, assigning to Scott, since he may have fixed this when he rejigged logging
Rod Widdowson November 29, 2012 at 11:50 AM
Make Chad's cases unassigned
I find it very helpful for timestamps in the log to be in local time rather than UTC, but can appreciate others don't agree. The logging layer can only control the timestamps in the event records, but I wondered if having a helper routine to run any timestamp parameters through when logging them might allow it to be controlled above that layer.
This would have to across all the code layers, but I'm filing here for now.