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

Establish timeseries database for Flotilla #48

Closed
aeshub opened this issue Jan 25, 2022 · 7 comments · Fixed by #805
Closed

Establish timeseries database for Flotilla #48

aeshub opened this issue Jan 25, 2022 · 7 comments · Fixed by #805
Assignees
Labels
backend Backend related functionality feature New feature or request

Comments

@aeshub
Copy link
Contributor

aeshub commented Jan 25, 2022

Describe the new feature you would like to see
The Flotilla system will have access to timeseries streamed from the MQTT broker which should be stored in a timeseries database. Examples are mission status, battery level, pose etc.

Describe the solution you'd like
The MQTT broker established as part of #47 should stream all relevant topics to the database where it is stored in a functional format. An example of a timeseries database is InfluxDB which is available in Azure.

EDIT by Torstein:

While looking into this, I think that PostreSQL and timescale db is a good option for us.
By using that we can link the timeseries relationally to the rest of our database.

https://azure.microsoft.com/nb-no/blog/power-iot-and-time-series-workloads-with-timescaledb-for-azure-database-for-postgresql/
https://docs.timescale.com/getting-started/latest/

How will this feature affect the current Threat Model?
Access to the timeseries database must be managed.

  • Note that the first iteration will only be a database available locally on the facility tightly coupled with Flotilla.
@aeshub aeshub added the feature New feature or request label Jan 25, 2022
@aeshub
Copy link
Contributor Author

aeshub commented Jan 25, 2022

image

@aeshub
Copy link
Contributor Author

aeshub commented Mar 27, 2022

This issue has automatically been marked as stale as there has been no activity for 60 days. Remove stale label or comment or this will be closed in 7 days.

@aeshub aeshub added stale This issue or pull request already exists and removed stale This issue or pull request already exists labels Mar 27, 2022
@aeshub aeshub added the backend Backend related functionality label May 12, 2022
@aeshub
Copy link
Contributor Author

aeshub commented May 20, 2022

Alternatives mentioned have also been IOTHUB, MQTT + SparkPlug

@aeshub aeshub added this to the MVP milestone May 20, 2022
@aeshub aeshub self-assigned this Jun 23, 2022
@aeshub aeshub removed their assignment Aug 4, 2022
@aeshub
Copy link
Contributor Author

aeshub commented Oct 3, 2022

This issue has automatically been marked as stale as there has been no activity for 60 days. Remove stale label or comment or this will be closed in 7 days.

@aeshub aeshub added the stale This issue or pull request already exists label Oct 3, 2022
@oysand oysand removed the stale This issue or pull request already exists label Nov 7, 2022
@aeshub aeshub modified the milestones: MVP, Test&Deployment Jan 12, 2023
@oysand oysand removed this from the Test&Deployment milestone Jan 30, 2023
@GodVenn GodVenn self-assigned this Feb 22, 2023
@GodVenn GodVenn removed their assignment Apr 28, 2023
@GodVenn
Copy link
Contributor

GodVenn commented Apr 28, 2023

While looking into this, I think that PostreSQL and timescale db is a good option for us.
By using that we can link the timeseries relationally to the rest of our database.

https://azure.microsoft.com/nb-no/blog/power-iot-and-time-series-workloads-with-timescaledb-for-azure-database-for-postgresql/
https://docs.timescale.com/getting-started/latest/

@GodVenn GodVenn self-assigned this May 11, 2023
@aeshub
Copy link
Contributor Author

aeshub commented Jul 10, 2023

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label Jul 10, 2023
@Eddasol Eddasol removed the stale This issue or pull request already exists label Jul 10, 2023
@aeshub
Copy link
Contributor Author

aeshub commented Sep 9, 2023

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label Sep 9, 2023
@oysand oysand removed the stale This issue or pull request already exists label Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend related functionality feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants