Hi To be honest there are a variety of options but it all comes down to who will be querying these dashboards.
If the end user is an engineer then the ELK stack is fine and I can attest to the ease of use of kibana since I used it quite heavily. On the other hand in my experience it isnt the engineers that are in charge of reporting so if the end user is a data analyst or data scientist then they are most comfortable using SQL and would be slightly aversed to learning the nuances of creating dashboards and using elastic search. Trust me no matter how much you try, these folks are more comfortable using sql and Tableau like platforms. So you will have to educate them, Not to mention the fact that any new hire will have to undergo the same training to be productive My suggestion for that is to push your data to Google BigQuery <https://cloud.google.com/bigquery/>. It really is simple to use and people can just focus on writing their queries. It also returns within seconds for queries over terabytes of data. The caveat here is that you are paying per query. But it's $5 for 1 TB which is peanuts really. Its a managed service so there is zero setup costs and management compared to the other services. I suppose in the end you are paying to abstract that knowledge away Happy to answer any questions you might have Kind Regards Sam On Wed, 12 Apr 2017 at 09:36, tencas <diego...@gmail.com> wrote: > Hi Gaurav1809 , > > I was thinking about using elasticsearch + kibana too (actually don't know > the differences between ELK and elasticsearch). > I was wondering about pros and cons of using a document indexer vs NoSQL > database. > > > > -- > View this message in context: http://apache-spark-user-list. > 1001560.n3.nabble.com/Spark-Streaming-Real-time-save-data- > and-visualize-on-dashboard-tp28587p28589.html > Sent from the Apache Spark User List mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe e-mail: user-unsubscr...@spark.apache.org > >
