Open openBackhaul opened 2 years ago
Hi Thorsten, thanks a lot for creating the issue. I would prefer to have the Link ID as measurement identifier because there is only planned to have one measurement per Link ID at once. After a new measurement an ald measurement should be overwritten. Will you update the issue descritpion or should I update it? Thanks a lot and best Regards, Roland
Hi Roland, the Description currently defines that data is retrieved from a device; so it would be one side of a link. You are commenting "one measurement" per link (Link ID). Shall the Description also be adapted in the sense of pairs of devices shall be addressed and pairs of performance data shall be provided?
Hi Thorsten, in my opinion it is a technical decision if the datas are saved per side of a link or per link. It should only be clear that both sides will be recorded at once. Does this answer your question? BR, Roland
Consolidated the input into the Implementation Details. Thanks for commenting.
Description
The FineGrainedLinkDataCollector retrieves a predefined set of measurement and performance data from both ends of a microwave link at high rate and for a limited time period.
Dependencies
Implementation Details
The FineGrainedLinkDataCollector gets addressed with a link ID, measurement resolution and measurement length at a start-measurement service. Based on these attributes it is starting to retrieve the following attributes in the given frequency and for the given time period:
It is answering a measurement identifier in the response body of the start-measurement service request.
Every time the FineGrainedLinkDataCollector gets addressed with the measurement identifier in a refresh service request, it shall provide the measurement results in the response body. The FineGrainedLinkDataCollector excludes several measurements being run on the same link ID in parallel. Starting a new measurement with the same link ID overwrites the old measurement.