Skip to content

Logs Search View: Unknown expression or function identifier TimestampTime #2251

Closed

Description

@simadimonyan

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'].

Image

Activity

  1. brandon-pereira commented on May 11, 2026

    @brandon-pereira
    Member

    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.

  2. townsag commented on May 12, 2026

    @townsag

    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"?

  3. brandon-pereira commented on May 12, 2026

    @brandon-pereira
    Member

    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?

  4. townsag commented on May 13, 2026

    @townsag

    I recently changed my hyperDX and hyperdx/hyperdx-otel-collector docker image tags from latest to 2-nightly

  5. knudtty commented on May 13, 2026

    @knudtty
    Contributor

    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?

  6. simadimonyan commented on May 23, 2026

    @simadimonyan
    Author

    I use docker compose - latest image of hyperdx

  7. simadimonyan commented on May 23, 2026

    @simadimonyan
    Author

    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"?

    it helped! thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions