-
Notifications
You must be signed in to change notification settings - Fork 40
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
feat: Harvest should collect QOS policy groups #1831
Conversation
instance.SetLabel("min_throughput_iops", min.IOPS) | ||
instance.SetLabel("max_throughput_iops", max.IOPS) | ||
instance.SetLabel("min_throughput_mbps", min.Mbps) | ||
instance.SetLabel("max_throughput_mbps", max.Mbps) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the label be absent/empty instead of having 0 values. For example if qos policy is 19.07MB/s-4.55TB/s
then both min_throughput_iops
and max_throughput_iops
should not be published for that qos policy.
conf/zapi/default.yaml
Outdated
@@ -14,6 +14,7 @@ objects: | |||
# NetPort: netPort.yaml | |||
Node: node.yaml | |||
NtpServer: ntpserver.yaml | |||
QosPolicy: qos_policy.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be qos_policy_fixed.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think name qos_policy
is better. We can differentiate between adapative and non-adaptive with a label in exported metrics? Avoids different names?
No description provided.