Open faatihi opened 4 years ago
@faatihi Bernard has now created issue #1529 which is supposed to contain all things that have to be changed for the dashboard. Can you have a look at it and see if it contains everything that is needed?
@JonasCir @MartinWahnschaffeSymeda @MateStrysewske @markusmann-vg I had a meeting with @JinasCir to discuss ways on moving ahead of building and using other applications with sormas. We thought of integrating known dashboard tools to allow countries to configure what they need to see. I will plan a followup meeting to discuss the bast way and technology to use. Here are possible solutions: Kibana or Grafana ? Jonas will do a preliminary analysis of these technologies The current suggested workflow is to use R for data analysis and modelling, push the results in a statistics database than can be used by other applications for visualization
Grafana is an open source visualization platform. It can directly ingest data from PostgreSQL and can be provided as Docker container. It is extremely flexible and allows to create dashboards in no time. Visualizations can be exported and shared.
Kibana is also a great way to analyze and visualize data, however, it is tied to the Elasticsearch (ES) DB. Bringing this in makes the setup a bit more complex and resource intensive. Further, the relevant data has to be imported to ES first. However, @bernardsilenou mentioned that there were ideas for data warehousing and the need to query time series data dynamically. ES provides first class support for both. I already worked with the ELK stack in the past.
I just set up Grafana with SORMAS. Deployment is super easy, creating Dashboards is straight forward and looks like this:
@JonasCir that looks cool
@JonasCir Super! One thing lacking now is the creating of the statistics database in sormas. I will clone and test and also schedule a short meeting with the sormas gurus next week to decide the best was of information flow and documentation
As discussed briefly in #1475 ,
If we make the dashboard configurable, we won't have to go for "least common denominator" design when more countries get on board.
If there's a new adaptation request for another information on the dashboard, we only code the component for that information and make it available for all countries to add or switch out existing components.