Enable metrics_collector

[qibint]

Hello, we're using RabbitMQ Cluster Kubernetes Operator and created the rabbitmq instances from it attached is the yaml file.
However, I can't update disable_metrics_collector value to true through the additionalConfig since this management_agent.disable_metrics_collector.conf file in lines

https://github.com/docker-library/rabbitmq/blob/master/Dockerfile-alpine.template#L298-L299
https://github.com/docker-library/rabbitmq/blob/master/Dockerfile-ubuntu.template#L292-L295

always takes the priority over the 90-userDefinedConfiguration.conf file. Can you help with this problem?

apiVersion: rabbitmq.com/v1beta1
kind: RabbitmqCluster
metadata:
  name: amqp-workers
spec:
  image: rabbitmq:3.11.10
  service:
    type: ClusterIP
  replicas: 3
  persistence:
    storage: 20Gi
    storageClassName: gp2
  rabbitmq:
    additionalConfig: |
      # https://www.rabbitmq.com/configure.html
      # management metrics can be disabled altogether
      management_agent.disable_metrics_collector = false

[lukebakken]

I'm pretty sure that if we rename /etc/rabbitmq/conf.d/management_agent.disable_metrics_collector.conf to /etc/rabbitmq/conf.d/00-management_agent.disable_metrics_collector.conf, it will fix your issue.

To confirm this, in your environment, please use this Dockerfile as your image, rather than rabbitmq:3.11.10. It has a build step to move the /etc/rabbitmq/conf.d/management_agent.disable_metrics_collector.conf to a file with a 00- prefix.

Once you confirm that fixes your issue, I can make the change here. It won't be "live" until the next RabbitMQ release, however.

Thanks a lot!

[qibint]

Hey I built a docker image of the above Dockerfile and applied it in the manifest file. Now I can update the metrics collector value successfully. Thank you for the help!
Do you have an ETA for the next release?

Thanks

[michaelklishin]

This image is usually rebuilt and published when a new RabbitMQ patch release comes out, which on average happens every 2-3 weeks.

[lukebakken]

This will be fixed in PR #626