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

[receivers/prometheusreceiver] cannot configure http client used by target allocator generated scrape targets #18054

Closed
sfc-gh-rscott opened this issue Jan 26, 2023 · 3 comments
Labels
bug Something isn't working closed as inactive receiver/prometheus Prometheus receiver Stale

Comments

@sfc-gh-rscott
Copy link

Component(s)

receiver/prometheus

What happened?

Description

The target allocator component of the prometheus receiver supports configuring the http client used to retrieve scrape configs from the target allocator, but it does not support configuring the http clients used to perform the actual scrapes.

The configuration from the http_sd_config is used when communicating with the target allocator, but is not propagated to the generated scrape targets.

Steps to Reproduce

  1. Set up the prometheus receiver with the target allocator enabled. In my case, I used the opentelemetry operator.
  2. Set up a service to scrape in such a way that configuration of the http client is required to perform the scrape. This could be something like specifying a proxy URL or requiring custom TLS certs.

Expected Result

The http client config can be specified so that the target can be scraped.

Actual Result

There is no way to specify the http client config and the target cannot be scraped.

Collector version

v0.67.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

No response

@sfc-gh-rscott sfc-gh-rscott added bug Something isn't working needs triage New item requiring triage labels Jan 26, 2023
@github-actions github-actions bot added the receiver/prometheus Prometheus receiver label Jan 26, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@atoulme atoulme removed the needs triage New item requiring triage label Mar 7, 2023
@github-actions
Copy link
Contributor

github-actions bot commented May 8, 2023

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label May 8, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jul 7, 2023

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working closed as inactive receiver/prometheus Prometheus receiver Stale
Projects
None yet
Development

No branches or pull requests

2 participants