You want to be able to embed a visualization into your website, and let users of the website edit the embedded visualization?
Or do you mean by "passing parameters" that you want to do something else, like change the query parameters in the embedded iframe's src which will be saved to the visualization?
I am talking about scenario 1. I want user to edit embedded visualization.
For ex: If i have graph that shows data between particular date. And now
user wants to modify date and wants to see data with other date range then
visualization should get updated by changing date from website itself.
We don't technically support this functionality yet, but it is on our roadmap. There is a way to hack around this and provide the functionality, but it may not be exactly what you want to do. When you add the IFRAME to your web page, you can remove embed=true from the src value. This will embed the entire Kibana UI instead of just the Visualization or Dashboard. This will give the user the ability to edit the Visualization, but it will also let the user navigate throughout all of Kibana, which may be too much functionality for your use case.
Here it says that "Templates use handlebar syntax that allow you insert javascript clauses into your json. URL parameters are available on the ARGS object. "
By this can i accomplish my goal of updating kibana by passing values from web page ??
One more point to the same question. When i am going through the same steps given in the link. What i found is that kibana directory don't have "[kibanaDirecetory]\app\dashboard folder in it. Whereas kibana 3.0 was having it. so in kibana 3.0 we would able to query dashboard from template or scripted dashboard thing.
so can i know the reason behind removing this thing in kibana 5.0 ?
Hi Varun, to be honest, I'm not sure how valid those 3.0 docs are for 5.0. Have you been able to find anything similar in the 5.0 docs regarding Dashboard templates?
I'm also sorry, I don't have any information about why we removed that ability in 5.0 (or possibly even 4.0?). That was a couple years ago, and I joined the team in the middle of last year. You could probably search through the commit history on the 4.0 branch to identify when and why it was taken out.
Sorry I couldn't be more helpful! If you're trying to add more functionality to KIbana, have you looked into writing a plugin?
Hi Varun, I'm sorry I can't provide any information about Kibana 3... at this point our codebase has evolved so much farther beyond it that I, personally, don't have any insight about it or its features. Also, FYI, that product's End-of-life date was November 2015 (according to our EOL table), so I advise against using it. If you do, we won't be able to provide any additional updates or bug fixes.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.