Skip to content
This repository has been archived by the owner on Dec 11, 2022. It is now read-only.

v7.3.3 broke $__timeFilter #285

Closed
bacheson opened this issue Nov 22, 2020 · 0 comments
Closed

v7.3.3 broke $__timeFilter #285

bacheson opened this issue Nov 22, 2020 · 0 comments

Comments

@bacheson
Copy link

Bug Report

$__timeFilter(timestamp) no longer works in v7.3.3

Expected Behavior

The where statement should reference the selected time picker period (ie last 1 hour etc.)

timestamp BETWEEN TIMESTAMP_MILLIS ({timestamp_in_miliseconds_1_hour_ago}) AND TIMESTAMP_MILLIS ({timestamp_in_milliseconds_now})

Actual Behavior

The between start and end values are always the same like:
timestamp BETWEEN TIMESTAMP_MILLIS (1606071745741) AND TIMESTAMP_MILLIS (1606075345741)

Steps to Reproduce the Problem

  1. use $__timeFilter on a timestamp value

Specifications

  • Version: v1.0.8
  • Platform: Grafana Cloud / Linux?
  • Grafana Version: v7.3.3
@bacheson bacheson changed the title v7.3.3 broke $__timeFilter ... currently unusable v7.3.3 broke $__timeFilter Nov 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bacheson