-
Notifications
You must be signed in to change notification settings - Fork 37
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
Comments
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. |
Alternatives mentioned have also been IOTHUB, MQTT + SparkPlug |
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. |
While looking into this, I think that PostreSQL and timescale db is a good option for us. https://azure.microsoft.com/nb-no/blog/power-iot-and-time-series-workloads-with-timescaledb-for-azure-database-for-postgresql/ |
This issue has automatically been marked as stale as there has been no activity for 60 days. |
This issue has automatically been marked as stale as there has been no activity for 60 days. |
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.
The text was updated successfully, but these errors were encountered: