The PR https://github.com/prometheus/prometheus/pull/12933, merged in Prometheus v2.52.0 highlight the issue. Duplicated series in a single scrape seem to no longer be ignored. The error below is raised in the logs and the prometheus_target_scrapes_sample_duplicate_timestamp_total metric is incremented (which I monitor using Alertmanager):
ts=2024-05-11T14:03:07.232Z caller=scrape.go:1738 level=warn component="scrape manager" scrape_pool=frigate-exporter target=http://10.0.10.10:9100/metrics msg="Error on ingesting samples with different value but same timestamp" num_dropped=2
The two duplicated series in my case are from:
# HELP frigate_storage_mount_type_info Storage mount type
# TYPE frigate_storage_mount_type_info gauge
frigate_storage_mount_type_info{mount_type="tmpfs",storage="/"} 1.0
frigate_storage_mount_type_info{mount_type="ext4",storage="/"} 1.0
frigate_storage_mount_type_info{mount_type="ext4",storage="/"} 1.0
frigate_storage_mount_type_info{mount_type="tmpfs",storage="/"} 1.0
I think it might be dependant on the Frigate container deployment (volumes, tmpfs...) but I found a similar problem in the sample included in the README of the repository.
There is only one duplicate here (common with my case) and this will cause the same issue:
# HELP frigate_storage_mount_type_info Storage mount type
# TYPE frigate_storage_mount_type_info gauge
frigate_storage_mount_type_info{mount_type="tmpfs",storage="/"} 1.0
frigate_storage_mount_type_info{mount_type="ext4",storage="/"} 1.0
frigate_storage_mount_type_info{mount_type="ext4",storage="/"} 1.0
frigate_storage_mount_type_info{mount_type="overlay",storage="/"} 1.0
You will find below a sample docker compose having the issue:
Hello,
Using the newly released Prometheus v2.52.0 (https://github.com/prometheus/prometheus/releases/tag/v2.52.0) errors are raised in Prometheus side because of duplicated series from this exporter.
The PR https://github.com/prometheus/prometheus/pull/12933, merged in Prometheus v2.52.0 highlight the issue. Duplicated series in a single scrape seem to no longer be ignored. The error below is raised in the logs and the
prometheus_target_scrapes_sample_duplicate_timestamp_total
metric is incremented (which I monitor using Alertmanager):The two duplicated series in my case are from:
I think it might be dependant on the Frigate container deployment (volumes, tmpfs...) but I found a similar problem in the sample included in the README of the repository. There is only one duplicate here (common with my case) and this will cause the same issue:
You will find below a sample docker compose having the issue:
And also the full output of my
/metrics
:Thanks,