Testing the import of test results through the Murakami HTTP exporter and Murakami Viz POST API, I've successfully set up one device that uses the HTTP exporter, posting results to the API. However, not all fields for supported tests are included. Fields are aligned with ndt5 and ndt7 tests, but other fields from speedtest-cli are not included.
The table below is from the output of downloaded the results from Murakami Viz, transposed in columns for readability:
Murakami's output specification for speedtest-cli single and multi stream tests includes several fields that are not currently being stored by the API.
As a guide for which fields are missing, below is a table showing the fields currently in the output of Murakami Viz, the fields present in the speedtest-cli tests, and sample values from a recent speedtest-cli test that was sent to Murakami Viz:
Testing the import of test results through the Murakami HTTP exporter and Murakami Viz POST API, I've successfully set up one device that uses the HTTP exporter, posting results to the API. However, not all fields for supported tests are included. Fields are aligned with ndt5 and ndt7 tests, but other fields from speedtest-cli are not included.
The table below is from the output of downloaded the results from Murakami Viz, transposed in columns for readability:
Murakami's output specification for speedtest-cli single and multi stream tests includes several fields that are not currently being stored by the API.
As a guide for which fields are missing, below is a table showing the fields currently in the output of Murakami Viz, the fields present in the speedtest-cli tests, and sample values from a recent speedtest-cli test that was sent to Murakami Viz: