During the testing with Grafana 11.3.0 and RabbitMQ 3.13.7, deployed on Kubernetes, we noticed several issues with the Erlang Distribution and Erlang BEAM dashboards.
Erlang Distribution dashboard:
The "State of distribution links" panel on the Erlang Distribution dashboard was failing due to a query error caused by duplicate series in the match group, resulting in many-to-many matching conflicts.
The "Process state" panel was unable to display correctly due to the flant status map being deprecated.
Erlang-BEAM dashboard:
Data was unable to be retrieved due to the missing DS_Prometheus variable, which was not defined as a datasource.
The "Erlang VM Run Queue Length" panel displayed data for all nodes in the cluster rather than filtering to show data only for the selected node.
Changes:
Updated the Erlang Distribution dashboard to refine instance filtering, preventing many-to-many matching errors.
Replaced the deprecated flant status map of "Process state" panel to status map.
On the Erlang-BEAM dashboard, defined the DS_Prometheus variable as a datasource to ensure accurate data retrieval.
Enhanced the "Erlang VM Run Queue Length" panel to filter data by the currently selected node.
Types of Changes
What types of changes does your code introduce to this project?
Put an x in the boxes that apply
[x] Bug fix (non-breaking change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
[ ] Documentation improvements (corrections, new content, etc)
[ ] Cosmetic change (whitespace, formatting, etc)
[ ] Build system and/or CI
Checklist
Put an x in the boxes that apply.
You can also fill these out after creating the PR.
If you're unsure about any of them, don't hesitate to ask on the mailing list.
We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
[x] If relevant, I have added this change to the first version(s) in release-notes that I expect to introduce it
Further Comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution
you did and what alternatives you considered, etc.
Proposed Changes
Hi,
During the testing with Grafana 11.3.0 and RabbitMQ 3.13.7, deployed on Kubernetes, we noticed several issues with the Erlang Distribution and Erlang BEAM dashboards.
Erlang Distribution dashboard:
The "State of distribution links" panel on the Erlang Distribution dashboard was failing due to a query error caused by duplicate series in the match group, resulting in many-to-many matching conflicts.
The "Process state" panel was unable to display correctly due to the flant status map being deprecated.
Erlang-BEAM dashboard:
Data was unable to be retrieved due to the missing DS_Prometheus variable, which was not defined as a datasource.
The "Erlang VM Run Queue Length" panel displayed data for all nodes in the cluster rather than filtering to show data only for the selected node.
Changes:
Types of Changes
What types of changes does your code introduce to this project? Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask on the mailing list. We're here to help! This is simply a reminder of what we are going to look for before merging your code.CONTRIBUTING.mddocumentFurther Comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc.