Forum Discussion
DanielAmbler
Helper II
Helper IIConverted timestamps using expression functions always have UTC timezone - is this expected?
Hi, I have some pipeline telemetry i'd like to store as part of a pipeline run. What I'd like to store is the offset between the converted timestamp and utc. I am currently testing the timez...
Hi DanielAmbler ,
Apologize for the issue you are facing. The best course of action is to open a support ticket and have our support team take a closer look at it: LinkAfter creating a Support ticket please provide the ticket number as it would help us to track for more information.
Hope this helps. Please let us know if you have any other queries.
DanielAmblerHelper II
Helper IIHi Anonymous
Just taking a single conversion for simplicity, I guess I was expecting something along the lines of
{
"name": "var_utcnow",
"value": "2024-06-13T10:24:21.7790903Z" # expected as this is UTC
}
{
"name": "var_utc_convert_timezone_1",
"value": "2024-06-13T11:24:21.7790903Z" # Assuming UK as the conversion would expect 2024-06-13T11:24:21.7790903+01:00
}
Regardless of the formating options for timezone, the offset always specifies Z. The document I referenced were
"The UTC offset is appended directly to the time instead of "Z" suffix above; other nautical time zone letters are not used. The offset is applied to UTC to get the civil time in the designated time zone in the format '±[hh]:[mm]', '±[hh][mm]', or '±[hh]'."
and
Hi DanielAmbler ,
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.