So I have a RabbitMQ queue with messages containing a single point in line protocol.
These points are generated by the Node.js client library by doing:
const point = new Point("some-measurement") .timestamp(1620838490826) // in milliseconds .floatField("value", 0.125)
Now, using the Telegraf amqp_consumer input plugin I’m able to process these messages.
Problem is, the influxdb_v2 output plugin does not like the line protocol generated by the client library (!?)
E! [outputs.influxdb_v2] Failed to write metric (will be dropped: 422 Unprocessable Entity): unprocessable entity: failure writing points to database: partial write: points beyond retention policy dropped=X
The target bucket does not have any retention policy set.
I’ve read somewhere that’s caused by the fact that the influxdb_v2 output plugin expects the line protocol to use nanoseconds? Is that the case?
If so, then why the client libraries do not write these in nanoseconds?
Is it really impossible for the Telegraf influxdb_v2 output plugin to understand a unix timestamp in seconds or milliseconds? Maybe with a configuration option?