0.7.0 - Google Health API & SensorBio #1438
KaliszS
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Highlights
We encourage you to use our official Docker images:
Google Health API & SensorBio
In our latest release, we’re introducing two new integrations with providers. Both integrations will be further developed, but it’s important to note two things:
Admin UI Dashboard improvements
On less efficient infrastructure, the front-end dashboard could take up to several seconds to load data. We optimised this by making improvements to React and removing unnecessary information. In return, we added more details about the volume of stored data and its specific types (see screenshot below). We also improved the display of large numbers (previously, even millions were shown in thousands). The dashboard should now load instantly, even with very large volumes of data and limited RAM.
More information on data sources for the frontend
On the frontend, each piece of data (workouts, sleep sessions, menstrual cycles, activity) will display more information. Until now, we’ve only shown the provider from which the data was saved. Now, the original provider will also be displayed (if applicable – for example, Apple allows data to be synchronised from devices belonging to other providers) along with the device from which the data was retrieved (currently, in the example described earlier, for Apple this will simply be an iPhone, but we also intend to start recording information about the original device soon, provided the providers allow it).
You’ll probably often notice gaps in this information; we intend to rectify them in the next release, as this requires changes to the way data is fetched from the sources.
The option to delete data associated with a selected provider
From now on, the user profile includes an option to delete data from a selected provider. This also automatically disconnects the connection.
SDK applications management in Settings
From now on, you can manage SDK applications via the frontend settings (Admin UI).
Logging improvements
The first change is an improvement to the SDK’s data-saving process. Previously, a single incorrect row would result in the loss of the entire batch. Now, instead, we display the sync status for the problematic rows and log their exact errors to Sentry.
In addition, we have added a lot of new information to the logs, which may be useful for debugging.
HTTP logs from app:
response_body(an error details)request_bytes(how many bytes we are expecting from the payload)error_cause_type(can be helpful to decide whetheran error parsing the bodyresponse_body is caused by connection or decode error)error_cause_msgcontent_type(should beapplication/json)content_encoding(for examplegzip)Logs from celery worker:
first_error_loc(position of the first broken row in S3 payload)data_type(SDK related, exampleHKQuantityTypeIdentifierWalkingStepLength)success(SDK related, exampletrue)record_count(SDK related, int)task_type(SDK related, exampleforeground)low_power(SDK related, examplefalse)thermal_state(SDK related, examplenominal)types(sync status related, example["basal_energy", "energy", "heart_rate", "steps"])What's Changed
Google Health API
SensorBio
Oura
Data model
Frontend improvements
Observability & deployments
Other
Docs & chores
New Contributors
Full Changelog: 0.6.3...0.7.0
This discussion was created from the release 0.7.0 - Google Health API & SensorBio.
All reactions