Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ADD database for writing history and building statistic reports #155

Open
4 tasks
acmenezes opened this issue Aug 17, 2022 · 0 comments
Open
4 tasks

ADD database for writing history and building statistic reports #155

acmenezes opened this issue Aug 17, 2022 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. Not-Easy hard to implement, requires some experience

Comments

@acmenezes
Copy link
Contributor

In order to follow up with trends and details on operator data to better evaluate the operator quality contained in the catalog sources we need to store that data in a robust database that can be queried easily and with performance. That will allow for multiple analysis on many metrics and also may inform later architectural decisions on the operator framework.

Some suggestions are:

  • Elasticsearch and Kibana
  • Other NoSQL databases with Grafana, such as MongoDB
  • For numerical time oriented data, AKA metrics, we can use time series databases

This is an exploratory issue and may require multiple PRs to solve it.

Acceptance criteria is (Each one may or may not be a separate issue/PR as we progress):

  • Include the libraries and necessary code to write the Json data collected to the database
  • Include a test database that will hold the historical data as part of a building automation
  • Include a reporting tool that can read that database and automate statistical data reporting
  • Include an official database to keep the data online 24x7 out of the opcap building and perform backups regularly
@acmenezes acmenezes added kind/feature Categorizes issue or PR as related to a new feature. Not-Easy hard to implement, requires some experience labels Aug 17, 2022
@acmenezes acmenezes added this to the Basic Install - v0.2.0 milestone Aug 17, 2022
@acmenezes acmenezes self-assigned this Aug 17, 2022
@acmenezes acmenezes removed this from the Basic Install - v0.2.0 milestone Sep 26, 2022
@acmenezes acmenezes removed their assignment Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. Not-Easy hard to implement, requires some experience
Projects
None yet
Development

No branches or pull requests

1 participant