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

[Feature request] Kibana 3 style filter narrowing on click for Elasticsearch #8052

Closed
jonesn opened this Issue Apr 6, 2017 · 6 comments

Comments

@jonesn

jonesn commented Apr 6, 2017

Kibana 3 offered a feature where you could click on a magnifying glass beside a term in a table to apply a filter that would further narrow the results returned from a query.

It would be great to have this in Grafana.

Example screenshot below.

kibana_narrowing2

@daniellee

This comment has been minimized.

Show comment
Hide comment
@daniellee

daniellee Apr 6, 2017

Member

In Kibana 3, this was great for filtering logs to see how often an error occurred. In Grafana, where would you want to see this? In the table panel? Would this be for all data sources?

Member

daniellee commented Apr 6, 2017

In Kibana 3, this was great for filtering logs to see how often an error occurred. In Grafana, where would you want to see this? In the table panel? Would this be for all data sources?

@jonesn

This comment has been minimized.

Show comment
Hide comment
@jonesn

jonesn Apr 6, 2017

The magnifying glass would be in the table panel and if possible the filter would be applied across all Elastic data sources in use on the dashboard.

A visual indication of the filter being applied could be added to the header section of the dashboard where the template variables go now (ala Kibana 3).

jonesn commented Apr 6, 2017

The magnifying glass would be in the table panel and if possible the filter would be applied across all Elastic data sources in use on the dashboard.

A visual indication of the filter being applied could be added to the header section of the dashboard where the template variables go now (ala Kibana 3).

@chrisjschultz

This comment has been minimized.

Show comment
Hide comment
@chrisjschultz

chrisjschultz Apr 6, 2017

This would be great. We are kinda stuck at the moment as this is one of the Kibana3 features we need. We want to move to Grafana and away from Kibana and having this would allow us to do so.

chrisjschultz commented Apr 6, 2017

This would be great. We are kinda stuck at the moment as this is one of the Kibana3 features we need. We want to move to Grafana and away from Kibana and having this would allow us to do so.

@torkelo

This comment has been minimized.

Show comment
Hide comment
@torkelo

torkelo Aug 8, 2017

Member

this is now merged to master can be tested in latest nightly build!

For a video demo of the feature:
https://twitter.com/grafana/status/895000347630084096

Member

torkelo commented Aug 8, 2017

this is now merged to master can be tested in latest nightly build!

For a video demo of the feature:
https://twitter.com/grafana/status/895000347630084096

@torkelo torkelo closed this Aug 8, 2017

@torkelo

This comment has been minimized.

Show comment
Hide comment
@torkelo

torkelo Aug 8, 2017

Member

please test and give feedback on how it works!

Member

torkelo commented Aug 8, 2017

please test and give feedback on how it works!

torkelo added a commit that referenced this issue Aug 10, 2017

torkelo added a commit that referenced this issue Aug 10, 2017

@torkelo torkelo modified the milestones: 4.5.0, 5.0 Aug 28, 2017

@arienchen

This comment has been minimized.

Show comment
Hide comment
@arienchen

arienchen Oct 17, 2017

Is there an option to disable by column,
not each column required to be filtered.

arienchen commented Oct 17, 2017

Is there an option to disable by column,
not each column required to be filtered.

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