Hi Tim Sullivan,
Thank you about your response.
It seems that I found the solution to that problem (but not automatically and safely as i expect -any suggestion are highly welcomed):
-
How to Import/Export dashboard as json file manually:
You can export saved dashboards, visualizations, and searches from Settings >> Objects (see below)
Remember to export associated visualizations and searches alongside the dashboard...
just clicking on dashboard export does not automatically include dependent objects.
2. Kibana under the hood: object persistence:
Users of Kibana create saved searches, visualizations, dashboards, and other such objects.
Kibana, of course, has to persist these objects somewhere so they can be loaded up next time users start it up.
As Kibana connects to Elasticsearch for querying users’ data anyway, it conveniently uses Elasticsearch to store its objects as well.
This blog post explores some of these objects, how they are stored in Elasticsearch, and when they are created.
The goal is for this information to serve as a useful tool not only for debugging but also for administrators who might want to deploy Kibana in an automated, repeatable fashion today.
3. Creating Kibana Dashboard Programmatically:
You can either write directly to the .kibana index or use the URL structure to create dynamic dashboards (though the latter requires you already have saved visualizations you're combining).
4. Building Kibana Dashboard Dynamically:
Look at the .kibana index in your elasticsearch ... it contains all the visualizations , dashboards etc.
You can use the normal elasticsearch REST Api to modify and add to this index.
Alternatively , a lot of what drives a dashboard (the different panels and filters) can be changed directly in the url (in RISON format)
generate the dashboard object with graphs for each new chart and then push it to the .kibana index ,
which will then update the existing dashboard and everyone who uses it will get the updated dashboard next time they refresh.
The visualizations are also stored there , so the same concept applies where you would first generate a visualization object
(tying to extract the data to the specific new chart from ES before )
to push to .kibana , before you reference it in your dashboard.