-
-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Adding columns to DB for latency and jitter values #48
Comments
I configured influxdb2 integration and checked data after the first speedtest. These are the available fields I could choose from: I picked download/upload, but I noticed very low values in influx: so I checked the mariadb data (record #7): So the data was ok. But the reported speed of that test was this: I didn't understand at first...then I thought maybe those download/upload columns in the db represent the amount of data sent/received, and that you get the actual speed values from the json in the data column. Problem is that the data column is not exported to influx. So, to integrate my OP, I think also the DL/UL speed values should be in their own columns, probably the quantity of data sent/received is not so important, and you could actually reuse those columns. :) |
@alexjustesen from the json data, download/bytes and upload/bytes is being written in the download/upload db columns: maybe it's a bug, and download/bandwidth upload/bandwidth values should be written there. |
Right now DL/UL/Ping values have specific columns in the results table, could it be possible to add the columns relevant to latency and jitter values for DL/UL/Ping? I know you also record the entire json result in a column, but it would be simpler to have the data in the columns to build graphs. :)
JSON result:
The text was updated successfully, but these errors were encountered: