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

Filter Grafana Dashboard Metric Values Based on ScaledObject, scaler and namespace #5714

Open
B4llouk opened this issue Apr 21, 2024 · 1 comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion

Comments

@B4llouk
Copy link

B4llouk commented Apr 21, 2024

Proposal

On the Grafana dashboard, metric variable is not filtered on other variables like ScaledObject , scaler and namespace.
This creates combinations in the Grafana dashboard that make no sense. In the Scaler Metric Value panel for example.

Use-Case

Current Behavior

When using the Grafana dashboard with KEDA, I select the variables such as:

  • scaler A
  • scaledObject B
  • namespace C

However, the subsequent metric variables that appear are not automatically filtered to correspond with these selections. This requires manual verification to ensure that the metrics displayed are relevant to the chosen scaler , scaledObject and namespace.

Expected Behavior

I would like the Grafana dashboard to automatically filter metric variables based on the previously selected variables like scaler, scaledObject and namespace. This enhancement would ensure that the metrics displayed are directly relevant to my selections.

Is this a feature you are interested in implementing yourself?

Yes

Anything else?

No response

@B4llouk B4llouk added feature-request All issues for new features that have not been committed to needs-discussion labels Apr 21, 2024
@tomkerkhove
Copy link
Member

Good idea, feel free to open a PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion
Projects
None yet
Development

No branches or pull requests

2 participants