We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since version 2.x the influx server offers an metrics endpoint on the server (if not disabled): https://docs.influxdata.com/influxdb/v2.5/reference/config-options/#metrics-disabled
Metrics description: https://docs.influxdata.com/influxdb/v2.5/reference/internals/metrics/
In this endpoint you are able to receive information about errors when writing back some measurements or see the used space sizes etc.
Within ioBroker it cloud be interesting when you see the disk space etc for debugging ors see how long the write back of the measurements will need.
Is it an feature what could be considered for this adapter or should it solved in a separate one?
Kind regards Marcus
The text was updated successfully, but these errors were encountered:
I think it could be added to poll it ... but then also the token needs additional rights ... need to think about it
Sorry, something went wrong.
No branches or pull requests
Since version 2.x the influx server offers an metrics endpoint on the server (if not disabled):
https://docs.influxdata.com/influxdb/v2.5/reference/config-options/#metrics-disabled
Metrics description:
https://docs.influxdata.com/influxdb/v2.5/reference/internals/metrics/
In this endpoint you are able to receive information about errors when writing back some measurements or see the used space sizes etc.
Within ioBroker it cloud be interesting when you see the disk space etc for debugging ors see how long the write back of the measurements will need.
Is it an feature what could be considered for this adapter or should it solved in a separate one?
Kind regards
Marcus
The text was updated successfully, but these errors were encountered: