-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Visualization Plugin Infrastructure #1440
Comments
This would be a great addition to Kibana, and something we would like to offer at some point in Kibana 4 |
👍 |
1 similar comment
+1 |
What is the status on standardizing and documenting the plugin infrastructure present in Kibana 4.0? |
👍 |
We're interested in knowing how "stable" the plugin infrastructure is too |
👍 , again :). |
+1 |
👍 where is this documented ? |
Plugin documentation is here: 👎 |
Yes and it's explicitly written "don't write custom plugins" since it is purposely undocumented and may disappear in the future. Should I take your comment as an approval to write one ? |
What about adding an iframe visualization that points to a custom url? Kibana could give the data points to render in the body of a HTTP PUT request. I do not know if it is a very optimized solution for performance, but it would enable lots of custom visualizations making it easier to integrate with the awesome query and filter operations of Kibana. |
I'm sure what they're thinking is something more native to the Kibana environment. If it's anything like what is being used internally a plugin would define itself according to some protocol and then be able to inject its functionality wherever visualizations are served and modified. The iframe approach might be a nice band-aid, but wouldn't suffice long term. Development on this cannot come quickly enough. We are clamoring to integrate our custom Kibana 3 panels into Kibana 4 as visualizations. |
and update on this thread ? |
https://github.com/chenryn/kibana4/commit/4e0bcbeb4c8fd94807c3a0b1df2ac6f56634f9a5 I'd try to write a sankey vis, but the webpage always crash, is here anyone farmilar with js can help me? |
@spalger Any updates on this? |
@Tawel I don't really have any updates, development still continues. |
+1 |
+1 |
+1 I am looking at building a word cloud chart as part of Kibana similar to the one implemented here. http://birdwatch.matthiasnehlsen.com/ |
+1 |
So far I have been able to create a visualization, but have a lot of issues regarding the actual Elasticsearch querying. I'll doing the whole shebang in the View, and that is just plain bad. It would be really great to have like a step by step guide of how to create a Visualization. |
@JuanCarniglia seems one visualization in kibana got the aggData already, no need to create a query by yourself. |
Very nice tutorial from Tim Roes - Writing Kibana 4 Plugins - Exactly what you need..An extension point for adding new visualizations. |
+1 it would be really helpful |
I have created some visualizations (all here: https://github.com/JuanCarniglia). I am now in the process of updating gulp files to ES6… which is proving painfully slow). Also currently writing a tutorial on all this. In the meantime I invite you to look at them and let me know what you think! Quick update: Now writing visualizations for Kibana 4.1 to 4.5 (soon going to 5.0). If anyone need some hints or tips, mail me, I'm getting the hang of it. Glad to help. |
+1 |
I updated some of the visualizations and added a couple more. I also found the way to query external (or same ES) from a visualization (what I actually solve by adding a front-less Plugin to kibana). If anyone is interested, I am yet to publish this code, but will real soon. |
We have recently introduced the following resources regarding developing of visualizations:
The docs will also be updated and extended in the future. |
There is some visualizations , I would like to add to Kibana panels.
Though i can code it to the existing code base , I need a plugin point to do this.
So that up-gradation and other operations are seemless.
The text was updated successfully, but these errors were encountered: