This repository was archived by the owner on Oct 29, 2024. It is now read-only.
UDP Precision still locked at seconds #554
Comments
|
Feel free to open a PR |
mdhausman
pushed a commit
to wayfair-archive/influxdb-python
that referenced
this issue
Jan 15, 2018
- address issue influxdata#554 - UDP writes can now convert timestamps to the desired precision - add time_precision argument to `InfluxDBClient.send_packet`, defaults to None - add tests for udp precision - remove old udp precision failure tests
mdhausman
pushed a commit
to wayfair-archive/influxdb-python
that referenced
this issue
Feb 12, 2018
- address issue influxdata#554 - UDP writes can now convert timestamps to the desired precision - add time_precision argument to `InfluxDBClient.send_packet`, defaults to None - add tests for udp precision - remove old udp precision failure tests
xginn8
pushed a commit
that referenced
this issue
Feb 13, 2018
- address issue #554 - UDP writes can now convert timestamps to the desired precision - add time_precision argument to `InfluxDBClient.send_packet`, defaults to None - add tests for udp precision - remove old udp precision failure tests
|
Fixed by #557 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Debugging some issues getting InfluxDB metrics from our python services, I found that even in the latest code UDP writes are locked into seconds precision when this hasn't been a necessity for influxdb since early 2016.
Isn't it time for this to be updated? I'd be happy to jot up a quick pull request for it.
The text was updated successfully, but these errors were encountered: