You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Logs Search View: Unknown expression or function identifier TimestampTime #2251
Unknown expression or function identifier TimestampTime in scope SELECT Timestamp, ServiceName, SeverityText, Body FROM default.otel_logs WHERE (TimestampTime >= fromUnixTimestamp64Milli(_CAST(1778311723231, 'Int64'))) AND (TimestampTime <= fromUnixTimestamp64Milli(_CAST(1778311783231, 'Int64'))) ORDER BY (toStartOfFiveMinutes(Timestamp), Timestamp, TimestampTime) DESC LIMIT _CAST(0, 'Int32'), _CAST(200, 'Int32'). Maybe you meant: ['Timestamp'].
Hey @simadimonyan , likely you have misconfigured your Timestamp Column in Source Settings. Please double check that and share any additional information from that screen if it is set correctly.
I was also experiencing this issue. It was resolved by changing Team Settings > Data > Logs > Timestamp Column to "Timestamp". Why would it have been "TimestampTime"?
TimestampTime used to be included in the schema for logs/traces however we recently did some performance exploration and found it wasn't necessary. (Relevant PR)
Curious if you have both created a new HyperDX service recently or you recently upgraded your instance?
What's your deployment method? Are you using the helm chart, or docker compose, or an image directly? Is this a new installation or an existing one that started erroring after you upgraded?
I was also experiencing this issue. It was resolved by changing Team Settings > Data > Logs > Timestamp Column to "Timestamp". Why would it have been "TimestampTime"?
Activity
brandon-pereira commentedon May 11, 2026
Hey @simadimonyan , likely you have misconfigured your
Timestamp Columnin Source Settings. Please double check that and share any additional information from that screen if it is set correctly.townsag commentedon May 12, 2026
I was also experiencing this issue. It was resolved by changing Team Settings > Data > Logs > Timestamp Column to "Timestamp". Why would it have been "TimestampTime"?
brandon-pereira commentedon May 12, 2026
TimestampTimeused to be included in the schema for logs/traces however we recently did some performance exploration and found it wasn't necessary. (Relevant PR)Curious if you have both created a new HyperDX service recently or you recently upgraded your instance?
townsag commentedon May 13, 2026
I recently changed my hyperDX and hyperdx/hyperdx-otel-collector docker image tags from latest to 2-nightly
knudtty commentedon May 13, 2026
What's your deployment method? Are you using the helm chart, or docker compose, or an image directly? Is this a new installation or an existing one that started erroring after you upgraded?
simadimonyan commentedon May 23, 2026
I use docker compose - latest image of hyperdx
simadimonyan commentedon May 23, 2026
it helped! thank you!