-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Date histogram range selection should add filter on visualized date field #3173
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Visualizations
Generic visualization features (in case no more specific feature label is available)
PR sent
Comments
rashidkpc
changed the title
Date histogram range selection should add filter on visualized field, not @timestamp
Date histogram range selection should add filter on visualized date field
Feb 25, 2015
+1 |
2 similar comments
+1 |
+1 |
@rashidkpc any ETA for fixing this? |
👍 this one gets annoying |
+1 |
I would honestly consider this a bug, not an enhancement. |
lukasolson
added
bug
Fixes for quality problems that affect the customer experience
and removed
release_note:enhancement
labels
Jan 17, 2017
tbragin
added
the
Feature:Visualizations
Generic visualization features (in case no more specific feature label is available)
label
Feb 14, 2017
+1 - it's annoying that this is open since 2015 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Visualizations
Generic visualization features (in case no more specific feature label is available)
PR sent
Currently the Date Histogram visualization can be used on any datetime field, but when ranges are selected on the visualization Kibana's date filter is being updated.
Instead, I'd expect Kibana to apply a date range filter on the field the visualization was created on similar to the way the Terms Aggregation works when a term is selected in a visualization - unless its the
@timestamp
(or the one configured to replace it) that's being visualized - only then it makes sense for Kibana to update the global date filter.This is especially important when showing several date visualizations (etc createdDate, updateDate etc) and need to allow for filtering based on one or more than that - and we can't just replicate this data to
@timestamp
The text was updated successfully, but these errors were encountered: