Time Filters and Formatting

• Time Formats Supported:

  • ISO formatted timestamps (e.g, 2025-04-02T15:22:00)

  • Relative time strings:

    • year/s

      • month/s

      • day/s

      • hour/s

      • minute/s

      • second/s

    Example Images:

• Time Filtering Behavior:

  • The API converts time inputs using the provided area_offset so that timestamps match the UTC storage in Redis.

  • End Time Exclusivity:

    • start_time <= dt < end_time This means that it will be equal or higher than Start Time and lower than End Time.

  • Important Considerations:

    • Counter Series:

      • In Weekly Interval, the start_time is based on each monday date (meaning, your start time needs to at least include one monday)

    • SQL Series:

      • Expects YYYYMM since all data is stored and aggregated monthly based.

    • Area filter:

      • Always uses each area specific UTC. Example:

        • If you select "global/all" it will use each area correct offset. Say you use "now", it will use all of the areas most up to date time. If you use a specific ISO, it will look at that specific time for all areas, meaning for some of those that hour might not exist and other it will be in the past. Say right now it is 2025-04-09T14:00:00 for Europe/Lisbon UTC +1 if I do this for Bala which is UTC -4 it will be in the future, therefore it will return values only up to 10:00:00, but for Saarlouis which is UTC +2 it will be in the past returning values up to 14:00:00 for that local area where it is 15:00:00.

        • So in general I recommend you use the relative methods for querying unless you know specifially what you are aiming for or wish to target specific hours.