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

Currently, the Rabbitmq receiver only supports versions 3.8 and 3.9. Is there any plan to support older versions in the future? #33211

Closed
shenlvcheng opened this issue May 24, 2024 · 5 comments

Comments

@shenlvcheng
Copy link

Component(s)

receiver/rabbitmq

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

Currently, the Rabbitmq receiver only supports versions 3.8 and 3.9. Is there any plan to support older versions in the future?

Describe the solution you'd like

Currently supported versions 3.8 and 3.9 are too new. Many enterprise environments use older versions, which makes it impossible to collect metrics.

Describe alternatives you've considered

No response

Additional context

No response

@shenlvcheng shenlvcheng added enhancement New feature or request needs triage New item requiring triage labels May 24, 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

Hello @shenlvcheng, it looks like as it is, 3.10 is already unsupported, which is more recent than the supported versions of this receiver. I'll defer to code owners, but it may be hard to justify adding support for more out of date versions.

Have you tested to confirm that older versions aren't working? Can you share what's not working?

I can't speak for the code owners here, but you'd be welcome to submit a PR adding support for any version you need 👍

@djaglowski
Copy link
Member

I generally don't think we should explicitly support versions which are EOL. If anything I believe we are due for updating our supported versions to 3.11+, but someone would need to test them first.

@crobert-1 crobert-1 removed the needs triage New item requiring triage label May 29, 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 Jul 29, 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 Sep 27, 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

3 participants