Query alerts: parseEventTime and parseTime return null on ClickHouse ISO timestamps with timezone suffixes #5072

Activity

1. duongynhi000005-oss commented on Oct 27, 2026

   

   duongynhi000005-oss

   on Oct 27, 2026

   More actions

   Root Cause & Proposed Fix

   1. Root Cause:

      • On current main, rowTime in apps/webapp/app/v3/services/alerts/engine/productionEvaluateBinding.server.ts (lines 170–178) and rowTimeIso in apps/webapp/app/v3/services/alerts/previewQuery.server.ts (lines 66–70) still construct new Date(\${value.replace(" ", "T")}Z`)directly instead of callingparseClickhouseDateTime (apps/webapp/app/v3/services/alerts/clickhouseDateTime.ts`).
      • When ClickHouse returns an ISO timestamp that already includes a Z or numeric offset suffix (e.g. 2026-07-01T12:30:15Z or 2026-07-01T14:30:15+02:00), unconditionally appending "Z" produces an invalid Date (NaN), causing rowTime to return undefined and rowTimeIso to fall back to the raw string.

   2. Proposed Fix:

      • Import and use parseClickhouseDateTime(value) in both rowTime (productionEvaluateBinding.server.ts) and rowTimeIso (previewQuery.server.ts), matching alertSeries.server.ts and healthQuerySeries.server.ts.
      • Extend apps/webapp/app/v3/services/alerts/clickhouseDateTime.test.ts to cover ISO timestamps with Z and numeric timezone offsets alongside space-separated DateTime / DateTime64 strings.

   I have a verified patch and unit tests ready on my fork and can open a PR if assigned.