Question: New to bluez & bluetooth. I have a few general questions about the management of data sourced from
a Polar sensor and written to the d-bus.

I'm working on a Jetson Nano that connects to a Polar heart rate sensor using Bluez.

When I worked in Data Warehousing I always pulled data from source systems by collecting data
where the source record's entry time stamp exceeded my last pull date. This prevented duplication
of data and missing new entries.

For this question, I consider the Jetson's d-bus as the source of my data. I pull from there.

Does this same concept I used in DW apply when pulling d-bus data? Is the d-bus data timestamped?
When data is read, is it read destruct, or should I delete it after I read it? Does data expire
and then automatically removed from the d-bus based on a built in timer? Is there a chance I would
miss data? Is there a mechanism (linux, d-bus, Bluez) to manage the life of the data?

Thanks for your assistance. If you can provide a few clues or point me to some documentation it
would be appreciated.

Answer: 
In the compose file, simply refer to bitnami/mariadb:10.6. You don't have to specify docker.io.

Also note that **depends\_on** is ignored and there's no need to specify port 443 as App Service does TLS termination.
i may be wrong but i think it won't work simply because there's a compatibility problem when it come to Docker-compose (preview) port, by that i mean that the only port that will work should either be 80 or 8080.

<https://learn.microsoft.com/en-us/azure/app-service/configure-custom-container?pivots=container-linux#docker-compose-options>

<https://i.stack.imgur.com/1LZBE.png>