Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upTargetpools scrape only first target in pool #33
Comments
ghost
assigned
matttproud
Jan 15, 2013
This comment has been minimized.
This comment has been minimized.
|
Can you patch in https://github.com/matttproud/prometheus/pull/32 and see
|
This comment has been minimized.
This comment has been minimized.
|
Nope, still only scrapes the first target :-/ |
This comment has been minimized.
This comment has been minimized.
matttproud
closed this
Jan 16, 2013
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 25, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
juliusv commentedJan 15, 2013
Targetpools scrape only first target that was added to the pool (at pool creation time). I haven't figured out the exact problem yet, but maybe it is something wrong with the heap handling? I've verified that Add() is called correctly for all targets on the right pools, but after that in the actual runs, p.Len() is always just 1.
I'll send a minimal config with multiple targets via mail.