Timestamps should be stored in UTC format

[bdb-dd]

Description

Check data transfer objects for DateTime properties and convert to DateTimeOffset to avoid serializing with local time zone offset.

Additional Information

No response

Tasks

No response

Acceptance Criterias

No response

[olebhansen]

@bdb-dd : Can you elaborate a bit on how this is having an impact? Where/how did you observe it? My understanding is that UTC is already in use (and with our external API being JSON-based, the DTO de-serialization is left to the consumer).

[bdb-dd]

@bdb-dd : Can you elaborate a bit on how this is having an impact? Where/how did you observe it? My understanding is that UTC is already in use (and with our external API being JSON-based, the DTO de-serialization is left to the consumer).

As far as I can remember, this was mostly for improving correlation across the timestamps available internally. Pretty sure I added this after spending time looking for an event, only to discover that my filter range was off by two hours.

I believe this is an example of a timestamp that would be in local time, which can make it hard to correlate with other values stored in UTC.

altinn-events/src/Events/Services/OutboundService.cs

Line 133 in 2170c8b

Pushed = DateTime.Now,

The other examples I am able to find now are limited to tests.
https://github.com/search?q=repo%3AAltinn%2Faltinn-events+DateTime.Now&type=code