Sorry for my question. May be it is out off topic, but I havn't found the answer anywhere else. It is indeed related to mobile development and open telemetry. Is it a possibility to force android emulator to use exactly the host's local time? Whatever I'm trying, the emulatore has allways some time drift and this causes the traces to be out of sync with the backend logs.
Is it a way to get around it? In case only local systems are related I would expect a clean trace ordering.
Below is the behavior I'm observing:
I'm expecting the root span is covering entire action, and the backend spans are on the right place just between the gaps on the left
Setting device's time using adb command seems to ignore the fraction of the second so it is alway a drift between 100 ms and 1s
Thank you
Sorry for my question. May be it is out off topic, but I havn't found the answer anywhere else. It is indeed related to mobile development and open telemetry. Is it a possibility to force android emulator to use exactly the host's local time? Whatever I'm trying, the emulatore has allways some time drift and this causes the traces to be out of sync with the backend logs.
Is it a way to get around it? In case only local systems are related I would expect a clean trace ordering.
Below is the behavior I'm observing:
I'm expecting the root span is covering entire action, and the backend spans are on the right place just between the gaps on the left
Setting device's time using adb command seems to ignore the fraction of the second so it is alway a drift between 100 ms and 1s
Thank you