Network dashboard thresholds

[mamoep]

A note for the community

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please let us know in a comment

Problem

On the dashboard "ONTAP: Network" the table panels "NIC ports" and "Link aggregation groups" both have thresholds defined for Send and Receive values. The configured thresholds only make sense for 1Gbit interfaces. For 10Gbit or more it will turn red while utilization is 10%. Yellow threshold is set so low, it is questionable even for 1Gbit.
For LAGs it doesn't make sense at all, even for 1Gbit interfaces. Because there will always be 2 or more ports in the group.

If possible change it to dynamic thresholds based on port speed. Transformation function "Config from query results" should make it work. Though I must admit I didn't test it.

https://grafana.com/docs/grafana/latest/visualizations/panels-visualizations/query-transform-data/transform-data/#config-from-query-results

Configuration

Poller

restperf,keyperf,zapiperf

Version

25.11.0

Poller logs

OS and platform

RHEL8

ONTAP or StorageGRID version

NetApp Release 9.16.1P8: Sat Oct 04 03:23:15 UTC 2025

Additional Context

No response

References

No response

[Hardikl]

@mamoep , The details of approach is updated here in PR #4062 (comment)

Just wanted to confirm regarding the ifgrp table,

• Weighted percentage makes sense for ifgrp based on the number of ports included in it?
• Does the threshold based on percentage would be correct, like 50%, 75% 90%?

[mamoep]

I don't fully understand the weighted percentage approach. Could you elaborate on that?
Thresholds 50%, 75% 90% looks good to me.

[Hardikl]

Thanks for the confirmation.

Sure, let me give one example.

If one ifgrp a0a has 2 ports included in it e0a and e0b. Now, e0a has utilization as 5% based on it's link speed as 1Gbit, and e0b has utilization as 15% based on it's link speed as 2Gbit.

Weighted percentage for the a0a ifgrp would be 11.67% as total supported link speed is 3Gbit.

[mamoep]

OK I understand now and in this scenario it makes sense. But I don't think ifgrps with different member link speeds are desired or even supported.

[Hardikl]

Got it. In that case, it's straight forward to sum and divide by number of ports in ifgrp. Thanks.