-
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
Drill down from one visualization to another #4439
Comments
I'm not exactly sure what the ask is here? Is there another tool that works like this that you could give an example of? |
Yes I have seen this feature in Splunk , though it is not free . But it provides an advance drill down option . So it provides feature like drilling down from one visualize to another or from one dashboard to another . |
So that mean we do not have solution for this as of now..? |
There is currently no functionality like this. |
+1 for this..one of the biggest limitations I am running into when developing a workflow with Kibana. |
+1 |
2 similar comments
+1 |
+1 |
+1 |
Definitelly +1 for this. Drill down dashboards! |
+1 Would be a nice feature |
+1 |
A start would be to use the markdown widget containing links to different dashboards. For this to work when clicking those links the next dashboard being viewed must inherit the current dashboards searches and filters. This includes lots of manual work but it would also save work in the long run. For example, lets say we have 5 apps, each have a similar logging structure but work completely different. You would start by creating 5 dashboards to show the most important information relevant to each app. When an error comes up all 5 apps log the same and what is important is shared between all of them so you could save time by creating one error dashboard that is accessible from all 5 main dashboards. Going from those dashboards to the error dashboard should inherit the filters the main one had. |
Is there a milestone for this enhancement? |
+1 We are proposing Kibana to a major client and drill down capability is a must. Personally I have worked with multiple dashboard tools with this capability including Splunk. An ideal solution would include embedding external URLs capable of passing parameters to drill into monitoring tools for a state of the art ITSM solution. |
@tslarkin61 If i understand correctly this should be doable with the extensions to kibana we have developed (aka the Kibi project - our friendly-kibana-fork-for-relational-data) check out the videos, might be close to what you need (and we'd be interested to know if its not!) https://www.youtube.com/channel/UCKGsC-vD28r7hW6T9QspKPA .. so you'll be able to propose Elasticsearch and Kibi/Kibana to your major client :) we're at Elasticon next week btw (sponsoring) so if you're around |
@jccq You understand correctly. We need to drill down from one dashboard to another dashboard and use the selection to filter into the next dashboard. Looks like you solved that design issue. Our other requirement is to drill down into other monitoring tools to execute reports based on passing parameters. Have you considered how you could handle external links associated with indexed data items? |
+1: A way to link from one dashboard to another in a way that preserves filters+search would be awesome. (Kibi seems overkill for our use.) |
+1. Would be killer feature! |
grafana has such a feature in case anyone is looknig for examples |
+1 for drilldown |
+1 |
This is a requirement for us as well |
+1 |
|
Wish they could have it |
+1 |
+1 |
+1 |
+1. Absolutely required. |
+1 |
2 similar comments
+1 |
+1 |
+1 on fire |
+1 |
+1 because we have recently started ELK and feel that it is only through X-Pack i.e. paid . Please implement this as a native feature in Kibana |
What about a dashboard panel that contains a list of related dashboards? Clicking on the dashboard link would transfer all context (time, filters, and lucene queries) to the drill-down dashboard. Issue #10461 is asking for a similar feature within Markdown widgets but maybe this should be its own panel type. |
@nreese You can achieve that by using markdown widget and pinning the required filters. |
+1 |
1 similar comment
+1 |
+1 |
Any update on this??? |
The current approach for drill down links we plan to implement is detailed here: #12560. |
+1 |
+1, for more details of drill down operations check https://community.tableau.com/thread/192365 |
I just found Kibana can drill down like this : https://demo.elastic.co/app/kibana#/visualize/edit/ba53d7d0-6b1d-11e7-90da-29dd6409b5ed |
The work arounds I found are either in the visualization builder or in the
field settings - you can set up the field type to URL, with a link to the
other kibana dashboard. Using the field value in the URL is possible by
teplate: {{value}}
…On Mar 9, 2018 10:08 AM, "floatingtony" ***@***.***> wrote:
I just found Kibana can drill down like this :
https://demo.elastic.co/app/kibana#/visualize/edit/
ba53d7d0-6b1d-11e7-90da-29dd6409b5ed
I prepare to drill down by this way. Are there any problem if i use the
Visual Builder?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4439 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIm7Fqht1gmaCEeBOq5RfmXYBBnlYm80ks5tcjhkgaJpZM4FZoOv>
.
|
I'll close this in favor of #12560 which keeps track about our effort about building drilldowns between dashboards. |
Hi Experts,
It seems we do not have this feature yet on kibana 4 ,to drill down from one visualization to another . Something like if I click on overall count of events it will open detail of all those events and further if I click on any event it will open detail for that particular event only . So basically a token concept, token value should pass to the next visualization.
Another scenario would be
I have logs from arcSight , so I have base and correlated events .Now I want to drill base to correlated or Vise versa .
Trust me if we have this feature that would be really great or if you guys are already working on it please update us , we can wait for next version of kibana.
Thank you
The text was updated successfully, but these errors were encountered: