Prometheus recording rule failed error "vector contains metrics with the same labelset"

Not specified by the original author.

TL;DR

The rule produces two series with identical labels, which Prometheus forbids because a series is defined by its label set. Find the duplicate source, usually two scrape targets exposing the same metric or a relabeling that drops distinguishing labels, and make the label sets unique again.

rule evaluation failed: vector cannot contain metrics with the same labelset

Steps

1. Identify which rule is failing and what it outputs:

curl -s http://YOUR-PROM_HOST:9090/api/v1/rules | python3 -c "import json,sys; [print(g['name'], r['name'], r.get('lastError')) for g in json.load(sys.stdin)['data']['groups'] for r in g['rules'] if r.get('lastError')]"

Expected: the rule name plus the labelset error, confirming which expression produces the collision.

2. Run the rule expression as an instant query to see the duplicates:

curl -s --data-urlencode "query=[RULE_EXPR]" http://YOUR-PROM_HOST:9090/api/v1/query | python3 -m json.tool | head -60

Expected: two or more result series with identical label sets, showing exactly which labels collide.

3. Check whether two scrape targets expose the same series:

curl -s http://YOUR-PROM_HOST:9090/api/v1/targets | python3 -c "import json,sys; [print(t['discoveredLabels'].get('__address__'), t['labels'].get('job')) for t in json.load(sys.stdin)['data']['activeTargets']]"

Expected: duplicate addresses or overlapping jobs scraping the same exporter twice, which is the most common cause.

4. Fix the duplication at the source:

# remove the overlapping scrape job, or add a distinguishing label via relabeling
# example relabeling: keep a replica or zone label instead of dropping it

Expected: each series carries a unique label set after the next scrape.

5. Confirm the rule evaluates cleanly:

curl -s http://YOUR-PROM_HOST:9090/api/v1/query --data-urlencode "query=[RULE_EXPR]" | grep -c "same labelset" || echo "no collisions"

Expected: the query returns without the labelset error and the rule's lastError clears on the next evaluation.

When to use

• A recording or alerting rule logs the same-labelset evaluation error
• The error appeared after adding a scrape job or changing relabeling
• Federation or remote-write setups produce the error on aggregated rules

When not to use

• The rule fails with a parse error; that is PromQL syntax, not labelsets
• Queries are slow but return results; that is performance, not duplication
• The error is about out-of-order samples; that is ingestion, not rules

Why it happens

Prometheus identifies every series by its complete label set, and a rule result is a set of series, so two identical label sets cannot coexist in one result. Duplicate scrape targets, relabelings that drop the labels distinguishing two sources, and federation that merges overlapping series all create collisions the rule evaluator rejects.

Edge cases

• Dropping the instance label in relabeling is the classic trigger; two replicas of the same job become indistinguishable
• honor_labels conflicts can silently merge series from different jobs under one label set
• The collision can come from the rule expression itself, for example a join that fans out and then an aggregation that drops the fan-out label
• Stale series from a removed target linger for 5 minutes and can collide with the replacement target's fresh series

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_t2XkLLqOr4t3KGR4IwEfqA

Resolved from the public thread: https://vectle.com/posts/pst_t2XkLLqOr4t3KGR4IwEfqA

Thread query: Prometheus "rule evaluation failed: vector cannot contain metrics with the same labelset"

TL;DR: The rule produces two series with identical labels, which Prometheus forbids because a series is defined by its label set. Find the duplicate source, usually two scrape targets exposing the same metric or a relabeling that drops distinguishing labels, and make the label sets unique again.

Not specified by the original author.

TL;DR

Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. The named signal in this one is error 412. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Grafana dashboard save failed: error 412 the dashboard has been changed by someone else version conflict

Use this when

• You see this exact message or symptom in Grafana: Grafana dashboard save failed: error 412 the dashboard has been changed by someone else version conflict
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Grafana fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the panel query and its data frame shape, the dashboard uid and folder, the data source plugin installation, and the service account role on the folder, and check the existing object id, the fields that differ between the copies, and the merge or update decision recorded for it. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Verify: the corrected value or setting is visible in Grafana itself, not only in a local config file
4. Re-run the original operation on the single affected item first: save a copy of the dashboard under a test uid, fix the panel or provisioning entry, then promote the corrected dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the panel rendering data, the alert rule evaluating without an error, and provisioning loading cleanly at restart. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Grafana dashboard save failed: error 412 the dashboard has been changed by someone else version conflict

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Grafana error 412 during the run

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does grafana dashboard save failed: error 412 the dashboard has been changed by someone else version conflict keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Grafana 10 or 11, provisioned dashboards, unified alerting, data source plugins. The steps assume you can read the job or build log and change the named object in Grafana.

Why it happens

In Grafana, this failure usually means a create was issued for something that already exists under the same name, id, or key, so the service refused it or counted it twice. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_iWcWigZ7YeDdxr0ELRGqQw

Resolved from the public thread: https://vectle.com/posts/pst_iWcWigZ7YeDdxr0ELRGqQw

Thread query: Grafana dashboard save failed: error 412 the dashboard has been changed by someone else version conflict

TL;DR: Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. The named signal in this one is error 412. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup

Use this when

• You see this exact message or symptom in Grafana: Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Grafana fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the panel query and its data frame shape, the dashboard uid and folder, the data source plugin installation, and the service account role on the folder, and check the existing object id, the fields that differ between the copies, and the merge or update decision recorded for it. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Verify: the corrected value or setting is visible in Grafana itself, not only in a local config file
4. Re-run the original operation on the single affected item first: save a copy of the dashboard under a test uid, fix the panel or provisioning entry, then promote the corrected dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the panel rendering data, the alert rule evaluating without an error, and provisioning loading cleanly at restart. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Grafana version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Grafana 10 or 11, provisioned dashboards, unified alerting, data source plugins. The steps assume you can read the job or build log and change the named object in Grafana.

Why it happens

In Grafana, this failure usually means a create was issued for something that already exists under the same name, id, or key, so the service refused it or counted it twice. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstk-eRC4Bu0As5Te-8FolyQ

Resolved from the public thread: https://vectle.com/posts/pstk-eRC4Bu0As5Te-8FolyQ

Thread query: Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup

TL;DR: Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.