[receiver/rabbitmq] add rabbitmq.cluster.name resource attribute

[ayush-singh-0601]

Description

add the disabled-by-default rabbitmq.cluster.name resource attribute

fetch the cluster name from RabbitMQ's /api/cluster-name endpoint once per scrape

propagate it to queue, node, and exchange metrics, with partial-error handling when lookup fails

regenerate metadata artifacts and add client/scraper coverage

Link to tracking issue

Fixes #50168

Testing

• CGO_ENABLED=0 go test ./... (pass)
• CGO_ENABLED=0 go vet ./... (pass)
• git diff --check (pass)
• go test -race ./... could not run on the local Windows image because its installed 32-bit C compiler cannot build 64-bit race binaries; upstream CI should run the race job on supported runners.

Documentation

regenerate metadata artifacts

Authorship

• I, a human, wrote this pull request description myself.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: ayush-singh-0601 / name: ayush-singh-0601 (2377f39)

[github-actions]

Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib.

Important reminders:

• Read our Contributing Guidelines.
• Sign the CLA if you haven't already.
• Follow the OpenTelemetry Generative AI policy: disclose any AI use in your contribution, and communicate (PR descriptions, review replies) in your own words rather than AI-generated text.
• Give reviewers at least a few days before pinging them for feedback.
• If you need help with general setup, development process, or contributor etiquette, ask in #opentelemetry-new-contributors.
• First-time contributors should keep at most one PR marked as ready for review until their first PR is merged; once two are open for review, any further PR is automatically converted to draft.
• If your change isn't one of our priority components, reviews may take more time.
• Raise technical or Collector-specific questions in #otel-collector-dev or a Collector SIG meeting.

[opentelemetry-pr-dashboard]

Pull request dashboard status

Waiting on reviewers · refreshed 2026-08-22 16:51 UTC

Review the latest changes.

Status above doesn't look right?

• Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.

[paulojmdias]

@ayush-singh-0601, please sign the CLA, please check the contributing guidelines, specifically the AI assisted section, and update your PR description.

[paulojmdias]

@ayush-singh-0601 please add a changelog entry

[paulojmdias]

/workflow-approve

[ayush-singh-0601]

i have fixed the issue

[ayush-singh-0601]

can you suggest what should i do next

[paulojmdias]

/workflow-approve

[ayush-singh-0601]

it is asking for approval for the workflow can you please provide it

[singhvibhanshu]

/workflow-approve

[singhvibhanshu]

@ayush-singh-0601,
May I ask why have you replaced our description template with something random? I'd suggest you to check the contributing guidelines, specifically the AI assisted section, and update your PR description accordingly.

[ayush-singh-0601]

i updated my pr description, sorry for the change in description , wont happen again
if there is any changes i need to make please do tell

[singhvibhanshu]

Also check the (I, a human, wrote ...) checkbox. Also, make sure that this won't happen again, otherwise it may lead to closing to your upcoming PRs. For more info, read our contributing guidelines.

[singhvibhanshu]

/workflow-approve

[ayush-singh-0601]

done