-
Notifications
You must be signed in to change notification settings - Fork 36
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: support flexgroup constituents in template #2410
Conversation
# Conflicts: # conf/rest/9.10.0/volume.yaml # conf/rest/9.9.0/volume.yaml
Any impact to published metrics? |
This change would only increase the # records of the existing metrics, doesn't add/change the shape of existing ones. |
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.
looks good. Needs relevant changes if counters needs to be disabled by default.
changed to false for default. |
conf/rest/9.10.0/volume.yaml
Outdated
@@ -79,7 +79,7 @@ plugins: | |||
- Volume: | |||
schedule: | |||
- data: 15m # should be multiple of poll duration | |||
include_constituents: true | |||
include_constituents: false |
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.
needs dashboard text also about the steps needed to enable dashboard
Supporting one flag
includeConstituents
in all volume templates, which can decide to export flexgroup constituents or not from Harvest poller.Changes:
For Zapi,
Config api gives all the records, flag
includeConstituents
will control constituents records in plugin.For ZapiPerf,
Perf api gives all the records, flag
includeConstituents
will control constituents records in plugin.For RestPerf,
Perf api gives all the records, flag
includeConstituents
will control constituents records in plugin.For Rest,
Public api either gives Flexgroup and Flexvols Or only Flexgroup_constituents but not all.
Used private api gives all the records, Then call public api 2 times for fetching all config details for them. 1 with filter
is_constituent = false
and 2 with filteris_constituent = true
. Later, flagincludeConstituents
will control constituents records in plugin.One alternate option would be to duplicate volume template based on
is_constituent
filter, But I would not be inclined towards it as maintenance cost and complexity to User while update/add metrics in both.