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

[Feature]Create new AKS metric for Max Node Count and current node count in AKS Node Pools #4719

Open
anilkumar1619 opened this issue Dec 19, 2024 · 0 comments
Labels
feature-request Requested Features

Comments

@anilkumar1619
Copy link

Is your feature request related to a problem? Please describe.

I am looking for the following metrics to create an alert when a nodepool scales to 90%:

  1. Maximum node count of the nodepool
  2. Current node count of the nodepool

Detailed Explanation:

We would want to create an alert using the maximum node count and the current node count of the nodepool when autoscaler is enabled. This alert will help to monitor and adjust the configuration when the node count reaches 90%, preventing issues related to insufficient nodes or maximum group size limitations.

I have reviewed the default and Prometheus metrics but couldn't find the appropriate metric for this alert.

I am requesting to see if there is a possibility of adding a dedicated alert section for each nodepool. This feature will enable customers to configure alerts easily and directly on the nodepool. It will streamline the alerting process by allowing alerts to be set when the node group size reaches a specific count or percentage, eliminating the need to navigate through cluster alerts to find the relevant metrics and configure.

Since I couldn't find relevant information in the documentation, I am raising this feedback request to explore the possibility of implementing this feature or considering it as feedback.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@anilkumar1619 anilkumar1619 added the feature-request Requested Features label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Requested Features
Projects
None yet
Development

No branches or pull requests

1 participant