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

Targetpools scrape only first target in pool #33

Closed
juliusv opened this issue Jan 15, 2013 · 4 comments
Closed

Targetpools scrape only first target in pool #33

juliusv opened this issue Jan 15, 2013 · 4 comments
Assignees

Comments

@juliusv
Copy link
Member

juliusv commented Jan 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.

@ghost ghost assigned matttproud Jan 15, 2013
@matttproud
Copy link
Member

Can you patch in https://github.com/matttproud/prometheus/pull/32 and see
if that improves anything?
Am 15.01.2013 03:11 schrieb "juliusv" notifications@github.com:

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.


Reply to this email directly or view it on GitHubhttps://github.com/matttproud/prometheus/issues/33.

@juliusv
Copy link
Member Author

juliusv commented Jan 15, 2013

Nope, still only scrapes the first target :-/

@matttproud
Copy link
Member

simonpasquier pushed a commit to simonpasquier/prometheus that referenced this issue Oct 12, 2017
@lock
Copy link

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.

@lock lock bot locked and limited conversation to collaborators Mar 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants