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

Implement target re-evaluation during runtime #4

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

Implement target re-evaluation during runtime #4

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

Comments

@juliusv
Copy link
Member

juliusv commented Jan 4, 2013

  • via DNS
  • via changed targets file on disk (need to separate targets into own file first)
@ghost ghost assigned juliusv Jan 4, 2013
@matttproud
Copy link
Member

@juliusv, given that we have the service discovery client library along with the DNS resolution coprocessor, I am going to mark this as closed. The question of whether to merge in the DNS-based approach into mainline Prometheus is an open question—one that I will let our early deployment process answer.

matttproud added a commit that referenced this issue Apr 9, 2014
Remove explicit WriteHeader call to have correct content type
juliusv added a commit that referenced this issue Apr 9, 2014
Run gofmt on corpus and include deprecation.
juliusv added a commit that referenced this issue Jun 23, 2016
simonpasquier referenced this issue in simonpasquier/prometheus Oct 12, 2017
cofyc added a commit to cofyc/prometheus that referenced this issue Mar 26, 2018
hectorj2f pushed a commit to hectorj2f/prometheus that referenced this issue Apr 27, 2018
simonpasquier referenced this issue in simonpasquier/prometheus Jun 25, 2018
bobmshannon pushed a commit to bobmshannon/prometheus that referenced this issue Nov 19, 2018
sylr referenced this issue in sylr/prometheus Nov 20, 2018
promql: Provide an option to replace rate extrapolation funcs
@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