-
Notifications
You must be signed in to change notification settings - Fork 108
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
Support multi-target #143
Support multi-target #143
Conversation
9a61dc0
to
3654d56
Compare
@roidelapluie can you help us with this PR? |
Apologies for the radio silence @mateusduboli. @SuperQ @roidelapluie So I see that the project's stance on multi-targets has changed? I found @SuperQ's comment from February suggesting exactly this change #111 (comment). The change looks good to me in general. I believe users should explicitly opt-in into the new behavior though by setting a flag. It might be unexpected and even harmful for users upgrading to the newest version if the exporter can be suddenly used to make requests against arbitrary endpoints. |
Yes, we've been adding multi-target exporter scrape support across the ecosystem to better support hosted/blackbox managed instances like Elasticache. |
I don't think we've added any blockers / flags to any other exporter that disable multi-target by default. We typically recommend users that care implement auth/tls. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found a recurring typo: s/scrapp/scrap/
🙂
scrape / scraping: copy (data) from a website using a computer program.
scrap / scrapping: discard or remove from service (a retired, old, or inoperative vehicle, vessel, or machine), especially so as to convert it to scrap metal.
@SuperQ @maxbrunet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nits.
Also, would you please update the README with documentation on how it's intended to work. I get it, but it would be nice to have docs right away.
Signed-off-by: Mateus Dubiela Oliveira <mateus.dubiela@nubank.com.br>
e2a0a12
to
7b73e3d
Compare
@SuperQ done ✅ |
Can this get merged and released? It is a super-useful feature, and it looks like everything that was asked for has been done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please follow Prometheus best practices.
logger: logger, | ||
timeout: timeout, | ||
scrapeCount: prometheus.NewCounter(prometheus.CounterOpts{ | ||
Name: "memcached_exporter_scrape_count", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Name: "memcached_exporter_scrape_count", | |
Name: "memcached_exporter_scrapes_total", |
Help: "Count of memcached exporter scapes.", | ||
}), | ||
scrapeErrors: prometheus.NewCounter(prometheus.CounterOpts{ | ||
Name: "memcached_exporter_scrape_error_count", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Name: "memcached_exporter_scrape_error_count", | |
Name: "memcached_exporter_scrape_errors_total", |
This feature seems helpful, but it has been open for several months without recent activity or approval. Is there a specific reason for the delay? Could someone help resolve any conflicts and get this merged? |
We wrapped this up in #173. |
Completed in #173 |
Thank you for your contribution! |
Adds support for multi-target pattern. Refers to #130
Discussion points:
scrapper
by default? Is this possibly a security problem?