[RabbitMQ] Capture erlang_vm metrics as part of the RabbitMQ module
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12.7k
- Forks
- 5k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 370
Description
Describe the enhancement:
The RabbitMQ module to be updated to capture the erlang_vm metrics like erlang_vm_dist_node_queue_size_bytes, erlang_vm_dist_send_bytes, erlang_vm_dist_node_state, erlang_vm_dist_proc_status, erlang_vm_dist_send_bytes, erlang_vm_dist_node_queue_size_bytes or their equivalents. Currently these metrics are only available by using the prometheus vm dist collector prometheus_vm_dist_collector — prometheus v6.1.1.
Describe a specific use case for the enhancement or feature:
This enhancement would help in the case of migrating RabbitMQ dashboards from Grafana to Kibana. There is a customer wanting to completely move out of Prometheus and use only ELK stack for collecting these metrics.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the RabbitMQ module and compare its current metrics with the prometheus_vm_dist_collector documentation linked in the issue. Identify the requested erlang_vm metrics or their equivalents, then verify that the RabbitMQ module exposes them for collection and that the resulting values support the stated dashboard migration use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang, go, prometheus
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100