Development issues are always at top of mind for the OneSense cloud and the value it brings to clients.
rewriting few components this weekend to save cost of Onesense.The initial design of OneSense had a Azure feature called Azure Data explore which use to add up more than 200 USD for bill.
A few OneSense components used this like for example :
1)Device rate meter
2) Storing Iot Messages
3) Operation logs of OneSense platform
Since we are using Azure Databricks for our new RuleEngine we are now rewriting a few componets to use Table storage and SQL Storage to remove dependency on Azure Data explorer and reduce cost.
We also had integration with EventHub for Azure Data so we can delete those EventHub with this change being another cost saving.
So now all the device telemetry would go to Azure data lake and the rate meter we would use Table Storage. OneSense operational logs would of one month be in SQL Azure database and then we wuld export the last 3 months in Table Storage.
We had stopped Azure DataExplorer to save development cost but with it back on getting this error from OneSense . So I have started the RateMeter job and started Azure data explorer to track which device is hitting the data hard and reaching 8000 cap. When validating a few things this will move from Azure Data Explorer to Table Storage, Azure SQL which would save development and production cost.
