Error on ingesting samples with different value but same timestamp

[MoSunDay]

We not only make P8S alarm system, at the same time also wants to use it as a temporal database, all work is good, but there is such a demand I hope with the new time-stamped data to cover the old data, as far as I know InfluxDB is support the operation, Did I miss something? If it is, please let us know.

I now think of benzene HTTP API method is invoked P8S delete old data, and then to collect new time-stamped old data, so clumsy

[simonpasquier]

I'm not sure exactly what you are asking for or if there's even a question. For what is worth, Prometheus will refuse to scrape samples with identical labels and timestamp.

[MoSunDay]

Thank you for your recovery. I know from the log of P8S that P8S rejects the indicators with the same timestamp. In fact, I want to know whether there is a switch that can make P8S accept the indicators with the same timestamp and cover the old data. There seems to be none. The current approach is to clean up old data through the HTTP API.

[MoSunDay]

Finally, we used remote_write/remote_read InfluxDB, and developed a middleware to accept Push data and forward Push data directly to InfluxDB, which is compatible with P8S query and alarm, and also supports the coverage with timestamp data, but it will consume double resources, so far we are satisfied