Skip to content

fix: isolate cluster metadata per probe target - #1259

Open
wangyusheng1985 wants to merge 1 commit into
prometheus-community:masterfrom
wangyusheng1985:fix/probe-cluster-metadata-isolation-1248
Open

wangyusheng1985 wants to merge 1 commit into
prometheus-community:masterfrom
wangyusheng1985:fix/probe-cluster-metadata-isolation-1248

Conversation

@wangyusheng1985

Copy link
Copy Markdown

Refactor the /probe endpoint into a standalone newProbeHandler and ensure per-probe instances of cluster.InfoProvider, ElasticsearchCollector, and Prometheus registry are isolated per request, preventing target A cluster metadata (cluster and cluster_uuid) from bleeding into target B. Add end-to-end multi-target probe tests.

Closes #1248

Signed-off-by: yusheng.wang <yusheng.wang@chaitin.com>
@sysadmind

Copy link
Copy Markdown
Contributor

This is already fixed on the master branch. It was resolved in #1147. The one thing that this PR does seem to add is some extra testing which could be useful. Do you want to close this or cut the changes down to just the tests?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

v1.11.0 multi-target /probe reuses first target's cluster metadata for later targets

2 participants