-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
PrometheusTargetMissingWithWarmupTime check issue with multiple jobs on the same target #424
Comments
Do you have multiple Prometheus instances in federation mode or a remote-write setup ? In that case, add a label to differentiate both jobs/prometheus. |
Hi @samber |
Yes, you may have multiple series with identical labels. Do you use service discovery? Did you check if an exporter endpoint is declared twice in prometheus.yml ? |
I don't use service discovery. I don't see any duplicated exporter endpoints It's not clear to me what caused it, because labels are not identical: attaching prometheus.yml
|
Hi, I'm wondering if I can do something to avoid this error:
It's realated to
PrometheusTargetMissingWithWarmupTime
alert and it's expressionsum by (instance, job) ((up == 0) * on (instance) group_right(job) (node_time_seconds - node_boot_time_seconds > 600))
which if I understand correctly can match multipleup==0
if I have more than one job at the same target? Any way to avoid/fix that?The text was updated successfully, but these errors were encountered: