just a theoric question about Kibana reporting capabilities.
We have a Oracle database where there are at least 10 tables we want to report data of.
We started using Microsoft Power Bi and the results were very good: we imported all involved tables and relating relations and then we used table/map visualizations "built-in" in Power Bi. We create pretty huge reports with lots of pages and the possibility to navigate from a page to another with navigation buttons or something like that.
Now, we want to explore more or less the same with Kibana functionalities. So the questions:
- when we need to import lots of tables from a relational database, what is the best to do the job? I started by creating nested json object in a single index because I know that in a NOSQL DB like Elastic it is highly unrecommended performing classical SQL JOIN. Using nested json object, though, probably will turn out out to be a real mess when we will reproduce all relations because we will need probably to create nested objects of nested objects and so on... Is there an alternative way to replicate SQL relations between tables?
- Is there the possibility to create reports divided by pages or is it better creating multiple dashboards linked each other? What is the most expressive way for an end user to navigate top down the data (thus, starting from column charts to a table view)?