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

Exclude OS aggregates from capacity used graph #327

Closed
matejzero opened this issue Jul 21, 2021 · 2 comments · Fixed by #977
Closed

Exclude OS aggregates from capacity used graph #327

matejzero opened this issue Jul 21, 2021 · 2 comments · Fixed by #977
Labels

Comments

@matejzero
Copy link

Describe the bug

On the cluster dashboard, capacity usage is calculates as avg(netapp_aggr_space_used_percent{datacenter=~"$Datacenter",cluster="$Cluster"}). This gives wrong result in my case where I have dedicated aggregates for NetApp OS (not sure if this is typical or not). I guess netapp makes them as small as possible and they are always 93%+ full, skewing the calculation.

Screenshot 2021-07-21 at 16 20 25

Capacity usage on the single panel graph is showing 78% instead of 62%, which is a lot of space in my case:)

Environment
Provide accurate information about the environment to help us reproduce the issue.

  • Harvest version: harvest version 21.05.3-2 (commit b482aff) (build date 2021-06-28T21:08:05+0530) linux/amd64
  • ONTAP Version: 9.7

To Reproduce

Load latest Cluster dashboard.

Expected behavior

Take only "data" aggregates into the account, to get more precise usage.

Possible solution, workaround, fix

Solution in my case is simple. Add an exclude filter to the metric: avg(netapp_aggr_space_used_percent{datacenter=~"$Datacenter",cluster="$Cluster",aggr!~"aggr0_.+"})

But I'm not sure, if this is a default name for the aggregates (aggr0_-).

@ruanruijuan
Copy link

Relate to #99.

@cgrinds
Copy link
Collaborator

cgrinds commented Aug 10, 2021

  • Compare with UM capacity aggregate calculation
  • Consider creating a plugin that ignores root-aggregate for ZAPIs (REST does this automatically)

@Hardikl Hardikl linked a pull request Apr 20, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants