Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HostPhysicalComponentTooHot throws "many-to-many matching not allowed: matching labels must be unique on one side" #414

Open
baurmatt opened this issue May 13, 2024 · 2 comments

Comments

@baurmatt
Copy link

The HostPhysicalComponentTooHot alert throws the following warning:

execution: found duplicate series for the match group {instance="host.docker.internal:9100"} on the right hand-side of the operation: [{__name__="node_uname_info", domainname="(none)", instance="host.docker.internal:9100", job="nodeexporter", machine="x86_64", nodename="nas01", release="5.15.0-107-generic", sysname="Linux", version="#117-Ubuntu SMP Fri Apr 26 12:26:49 UTC 2024"}, {__name__="node_uname_info", domainname="(none)", instance="host.docker.internal:9100", job="nodeexporter", machine="x86_64", nodename="nas01", release="5.15.0-105-generic", sysname="Linux", version="#115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024"}];many-to-many matching not allowed: matching labels must be unique on one side

This is because some labels of the node_uname_info metric changed (due to system upgrades) and thus metric is duplicated (for some time).

@maggie44
Copy link

And these I have come across so far with the same issue:

HostOutOfMemory
HostUnusualDiskReadRate
HostHighCpuLoad
HostCpuHighIowait

@roock
Copy link
Contributor

roock commented Aug 13, 2024

This is a duplicate of #397. I'm updating the original issue that it affects more alerts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants