[JinchengCao]

Summary

call() in src/sources/util/http_client.rs is the scrape loop shared by the http_client and prometheus_scrape sources. It used to take a fixed list of URLs. It now takes a function that returns the targets for each interval tick. A target can also carry source-specific data, which the source's context builder receives along with the URL.

With this change, Kubernetes Pod discovery (#26013) can reuse the shared loop with a target list that changes between ticks, instead of keeping its own copy of the request logic. Existing callers pass a fixed list through fixed_targets() and behave as before.

References

• Related: feat(prometheus_scrape): support auto discovery in k8s #26013

Vector configuration

NA

How did you test this PR?

Added targets_are_read_on_every_tick: the targets change after the first tick, and each event must carry the data of the target it was scraped from. Existing http_client and prometheus_scrape tests pass unchanged.

make test FEATURES="sources-http_client sources-prometheus_scrape" SCOPE="-E 'test(/sources::util::http_client/) or test(/sources::http_client::tests/) or test(/sources::prometheus::scrape/)'"

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
  For a new deprecation announcement, follow the deprecation policy and add a deprecation.d/ notice instead.
• No. A maintainer will apply the no-changelog label to this PR.

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-12T21:59:43.657115Z	446d904	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadoghq-integration]

More details

The fixed-target adapter preserves existing callers’ endpoint lists, and each request context receives the same target that supplies its URL. The completed static review identified no reportable defects.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit e8d0074}

[datadoghq-integration]

More details

Static review supports that target URLs remain paired with their source-specific context as targets change between ticks, and that the timeout bounds response-body reads. Runtime behavior was not exercised.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 446d904}