Hello We are exporting metrics from an OpenTelemetry collector using the prometheusremotewrite exporter to Prometheus started with the --enable-feature=remote-write-receiver The metrics are the results of k6 http requests eg response time which are passed into the Opentelemetry collector and then exported to Prometheus and we want to ingest all the data points into Prometheus. We then use Grafana to aggregate and visualise the metrics. It generally works fine except when a metric has the same name and value within the same time interval inside Prometheus. In this case Prometheus rejects the metric as a duplicate when Opentelemetry tries to export it and the metric is dropped. In this use case my question is why doesn't Prometheus use the metric timestamp which has nanosecond precision. If it did then it would be unlikely that 2 metrics would be duplicates. The other option we have had some success with is to add a random number tag to the metric but this doesn't always work and is not ideal. I'm not clear on how Prometheus creates it's internal timestamps in this case and wondered if there is some way to configure it to use the metric timestamp.
-- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/1bfd389f-7980-40a8-a847-c5e275ac282en%40googlegroups.com.
