Skip to content
This repository has been archived by the owner on Sep 14, 2021. It is now read-only.

Measurement results and incorrect datetime #8

Open
MindaugasStankevicius opened this issue Sep 4, 2020 · 0 comments
Open

Measurement results and incorrect datetime #8

MindaugasStankevicius opened this issue Sep 4, 2020 · 0 comments

Comments

@MindaugasStankevicius
Copy link

Dear developers,

I found strange values in couch-db (Measurement result).
(Measurement type web-browser)

Example data form database:
date (measurement was done on september 2)

network_info": {
"network_points_in_time": [
{
"time": "2020-09-02T08:02:56.911",

"system_uuid": "f0b6d3f1-40c8-4835-82df-747b28caa326",
"submit_time": "2020-09-02T08:02:56.993",
"time": {
"start_time": "2020-09-02T08:01:44.159",
"end_time": "2020-09-02T08:02:56.911",
"duration_ns": 72752000000

but in other part of measurement parameters the date is different - a time in future (september 27)

"time": {
"relative_start_time_ns": 1599033704170000000,
"relative_end_time_ns": 1599033750158000000,
"start_time": "2020-09-27T04:33:07.806",
"end_time": "2020-09-27T04:33:07.806",
"duration_ns": 45988000000

The dates are correct on measurement peer, other server where controller, collector, databases containers running.
Also correct date on measurement agent pc.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant