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

Grafana dashboards: needs an update for 4.x because rabbitmq_process_max_tcp_sockets is no longer available #12673

Open
garry-t opened this issue Nov 6, 2024 · 1 comment

Comments

@garry-t
Copy link

garry-t commented Nov 6, 2024

Describe the bug

I use Grafana dashboard for Rabbitmq provided by your team. After ugrade from 3.13.x to 4.0.x I fount that

Reproduction steps

  1. Prometheus + Grafana need to be installed
  2. Import official dashboard ID 10991
  3. Install Rabbitmq 3.13.x
  4. Point attention to panel TCP sockets available
  5. Upgrade Rabbitmq to 4.0.x
  6. Check same panel.

Or just shorter flow

  1. Prometheus + Grafana need to be installed
  2. Import official dashboard ID 10991
  3. Install rabbitmq 4.0.x
  4. Point attention to panel TCP sockets available

Expected behavior

Metrics are available or dashboard needs to be updated.

Additional context

n/a

@garry-t garry-t added the bug label Nov 6, 2024
@michaelklishin michaelklishin changed the title RabbitMQ 4.x does not report rabbitmq_process_max_tcp_sockets, or the metric name has changed, leading to missing data on the Grafana panel. Grafana dashboards: needs an update for 4.x because rabbitmq_process_max_tcp_sockets is no longer available Nov 6, 2024
@michaelklishin michaelklishin transferred this issue from rabbitmq/rabbitmq-website Nov 6, 2024
@michaelklishin
Copy link
Member

@garry-t you are welcome to update the dashboard.

In 4.0, as the change log suggests, several I/O-related metrics were removed. They should be monitored outside of RabbitMQ.

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