Today, Netperf's database/dashboard relies heavily on unique test IDs generated in the dashboard JSON files from msquic/scripts/secnetperf.ps1, which naturally meshes with the old Secnetperf design.
PR: Standard SecNetPerf Scenario introduces a new API design that includes some breaking changes, which means Netperf needs to update its data platform to accommodate this new design.
The most immediate action item would be to write a "glue" layer that translates this new API into the old interface, and have the data platform functioning as normal.
Today, Netperf's database/dashboard relies heavily on unique test IDs generated in the dashboard JSON files from
msquic/scripts/secnetperf.ps1, which naturally meshes with the old Secnetperf design.PR: Standard SecNetPerf Scenario introduces a new API design that includes some breaking changes, which means Netperf needs to update its data platform to accommodate this new design.
The most immediate action item would be to write a "glue" layer that translates this new API into the old interface, and have the data platform functioning as normal.