Skip to content

Specify connection name for the RabbitMQ exporter from config #34681

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

Closed
snichme opened this issue Aug 14, 2024 · 4 comments
Closed

Specify connection name for the RabbitMQ exporter from config #34681

snichme opened this issue Aug 14, 2024 · 4 comments

Comments

@snichme
Copy link
Contributor

snichme commented Aug 14, 2024

Component(s)

exporter/rabbitmq

Is your feature request related to a problem? Please describe.

Having a lot of agents connecting to the same RabbitMQ server makes it difficult to detect which connection might be having issue and from where the connection comes from.

Describe the solution you'd like

Be able to specify the name of the connection in the config for the agent.

Describe alternatives you've considered

No response

Additional context

No response

@snichme snichme added enhancement New feature or request needs triage New item requiring triage labels Aug 14, 2024
Copy link
Contributor

Pinging code owners:

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

@crobert-1
Copy link
Member

Removing needs triage as code owner has approved PR for this change`.

@crobert-1 crobert-1 removed the needs triage New item requiring triage label Aug 14, 2024
Copy link
Contributor

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 Oct 14, 2024
Copy link
Contributor

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 Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants