Hi @CDanis, can you please associate one or more active project tags with this task (via the Add Action... → Change Project Tags dropdown)? That will allow to see a task when looking at project workboards or searching for tasks in certain projects, and get notified about a task when watching a related project tag. Thanks!

Should I add some kind of identifier to match NEL reports and Probenet reports? Like instead of making a request to https://measure-{data-center}.wikimedia.org/measure, we may send a request to https://measure-{data-center}.wikimedia.org/measure?id={some-random-identifier}. This will help us in comparing the both reports in a better way. We don't have to modify in the NEL part. But we have to edit the schema of the report a bit to include the identifier as well and a small update to the JS fetch code patch.

In T337317#8877056, @JameelKaisar wrote:

Should I add some kind of identifier to match NEL reports and Probenet reports? Like instead of making a request to https://measure-{data-center}.wikimedia.org/measure, we may send a request to https://measure-{data-center}.wikimedia.org/measure?id={some-random-identifier}. This will help us in comparing the both reports in a better way. We don't have to modify in the NEL part. But we have to edit the schema of the report a bit to include the identifier as well and a small update to the JS fetch code patch.

Sounds good to me!

It might also be interesting to include the pulse number in the measurement URL as well. That way we'd also get the pulse ID in the NEL reports.

That's not needed. We can match the identifier then get the pulse number from the Probenet report. But we may add it to the url as well.

Change 923448 had a related patch set uploaded (by Jameel Kaisar; author: Jameel Kaisar):

[operations/puppet@production] Allow query parameters in network probe url

https://gerrit.wikimedia.org/r/923448

Change 924120 had a related patch set uploaded (by Jameel Kaisar; author: Jameel Kaisar):

[schemas/event/primary@master] Add metadata to network/probe schema

https://gerrit.wikimedia.org/r/924120

Change 924120 merged by Ottomata:

[schemas/event/primary@master] Add metadata to network/probe schema

https://gerrit.wikimedia.org/r/924120

Change 923448 merged by CDanis:

[operations/puppet@production] Allow query parameters in network probe url

https://gerrit.wikimedia.org/r/923448

The 'elapsed_time' filed in the NEL report is similar to the 'duration_ms' field in the Probenet report. They are not equal but follow a similar trend. If we ignore the first pulse to each data center (identifier_dc_0), the 'elapsed_time' filed in the NEL report is similar to the 'request_time_ms' field in the Probenet report. Since we mostly depend on the 'request_time_ms' field for analysing the latency data, we can easily rely on the NEL data for that. But, as of now, NEL is not supported on all browsers.

Probenet Report vs NEL Report: