Relevent telegraf.conf
...
data_format = "json_v2"
[[inputs.mqtt_consumer.json_v2]]
measurement_name = "test"
timestamp_path = "@this.timestamp"
timestamp_format = "unix_ns"
Logs from Telegraf
N/A
System info
docker telegraf:latest (1.21.2)
Docker
No response
Steps to reproduce
- MQTT payload: {"timestamp":1641667732350000000, .............}
- InfluxDB timestamp: 1641667732350000128
There is a small variation in the influxdb timestamp compared to MQTT timestamp.
(note, I also have an input.mqtt_consumer defined with data_format = "influx", which also receives a unix_ns timestamp; this timestamp is exactly forwarded to influxdb
Expected behavior
- MQTT payload: {"timestamp":1641667732350000000, .............}
- InfluxDB timestamp: 1641667732350000000
Actual behavior
- MQTT payload: {"timestamp":1641667732350000000, .............}
- InfluxDB timestamp: 1641667732350000128
Additional info
No response
Relevent telegraf.conf
Logs from Telegraf
N/A
System info
docker telegraf:latest (1.21.2)
Docker
No response
Steps to reproduce
There is a small variation in the influxdb timestamp compared to MQTT timestamp.
(note, I also have an input.mqtt_consumer defined with data_format = "influx", which also receives a unix_ns timestamp; this timestamp is exactly forwarded to influxdb
Expected behavior
Actual behavior
Additional info
No response