BUILD-345: Added csi shared resource metrics to telemetry#1477
Conversation
|
/assign @jan--f |
|
/retest |
| # | ||
| # owners: (@openshift/team-build-api) | ||
| # | ||
| # openshift:openshift_csi_share_configmap_total:sum measures total amount of secrets shared by csi shared resource driver. |
There was a problem hiding this comment.
| # openshift:openshift_csi_share_configmap_total:sum measures total amount of secrets shared by csi shared resource driver. | |
| # openshift_csi_share_secret_total measures total amount of secrets shared by csi shared resource driver. |
| # | ||
| # owners: (@openshift/team-build-api) | ||
| # | ||
| # openshift:openshift_csi_share_configmap_total:sum measures total amount of secrets shared by csi shared resource driver. |
There was a problem hiding this comment.
| # openshift:openshift_csi_share_configmap_total:sum measures total amount of secrets shared by csi shared resource driver. | |
| # openshift_csi_share_secret_total measures total amount of secrets shared by csi shared resource driver. |
| # owners: (@openshift/team-build-api) | ||
| # | ||
| # openshift:openshift_csi_share_configmap_total:sum measures total amount of config maps shared by csi shared resource driver. | ||
| - '{__name__="openshift_csi_share_configmap_total"}' |
There was a problem hiding this comment.
this looks like a gauge so it shouldn't have the _total suffix (reserved for counters). openshift_csi_shared_configmaps would be a better name.
There was a problem hiding this comment.
we actuall use total suffix for a bunch of other gauges. should i go back to the operator and change this metric name everywhere? this will require another pr and we weirdly don't have consistency here.
There was a problem hiding this comment.
Ideally i'd recommend that you update all metrics and make them consistent with the instrumentation guidelines. Now I understand that it may not be possible for the project.
| # | ||
| # owners: (@openshift/team-build-api) | ||
| # | ||
| # openshift:openshift_csi_share_configmap_total:sum measures total amount of config maps shared by csi shared resource driver. |
There was a problem hiding this comment.
this doesn't match the metric name
There was a problem hiding this comment.
i think i forgot to rebuild the docs. thanks!
| # owners: (@openshift/team-build-api) | ||
| # | ||
| # openshift:openshift_csi_share_mount_total:sum measures total amount of csi shared resources mounted in the pods. | ||
| - '{__name__="openshift_csi_share_mount_total"}' |
There was a problem hiding this comment.
about this metric, it's usually better to track requests and failures in different counters (see https://promcon.io/2017-munich/slides/best-practices-and-beastly-pitfalls.pdf, page 10). For instance, openshift_csi_share_mount_requests_total and openshift_csi_share_mount_failures_total.
There was a problem hiding this comment.
I don't see this recommendation to use different metrics instead of different labels in the slides. Slides do suggest that it's better to use failure_total and requests_total instead of failure_total and success_total though. Do you think we should go all the way back to already merged metrics and change them again?
@gabemontero wdyt?
There was a problem hiding this comment.
Again i would recommend that you follow the recommendations. The idea of tracking requests and failures is that you can later alert on the percentage of operations failing.
There was a problem hiding this comment.
This was discussed on the PR introducing this and I recommended the label way of solving this.
Calculating error rates should still be quite convenient with this setup rate(openshift_csi_share_mount_failures_total{succeeded="false"}[5m]) / rate(openshift_csi_share_mount_failures_total[5m]), though admittedly not as short as following the best practice.
@alicerum Since I approved the current state, I'd be happy to propose the change in the exporter.
There was a problem hiding this comment.
@jan--f After discussion with colleagues we decided it's better to go along with best practices, so i'm going to split them into total and failed series without labels. Thank you!
There was a problem hiding this comment.
See openshift/csi-driver-shared-resource#78 if you prefer to go with @simonpasquier's recommendation.
| # owners: (@openshift/team-build-api) | ||
| # | ||
| # openshift:openshift_csi_share_configmap_total:sum measures total amount of secrets shared by csi shared resource driver. | ||
| - '{__name__="openshift_csi_share_secret_total"}' |
bb908ed to
cf52b18
Compare
cf52b18 to
55dd2be
Compare
|
@jan--f please take a look at this, I've updated the metrics according to their new names and rebased the PR. |
|
/lgtm |
We need to receive some new metrics from the telemetry, for CSI shared resource driver and operator. Amount of shared resourced (secrets and config maps) and amount of shares mapped to pods, both succeeded and failed.
55dd2be to
becd444
Compare
|
/retest |
1 similar comment
|
/retest |
|
@alicerum: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/skip |
|
/assign @prietyc123 for qe-approved label /assign @rolfedh /label px-approved |
|
@simonpasquier @jan--f @bwplotka given your prior efforts reviewing this, I'm inclined to let one of you do the LGTM, but if you all are otherwise too busy, I think @alicerum has pulled in you comments, and I can do it. thanks |
|
/label docs-approved |
|
/label qe-approved |
|
Thanks, this looks great! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alicerum, bwplotka, jan--f The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/label docs-approved |
Fleet capability choices should make their way up to Red Hat via Insights uploads. But some clusters have Telemetry enabled but Insights disabled [1]. For these clusters, we'll want this data in Telemetry, and getting it into metrics (this commit) is the first step. After this lands, we'll need to update the monitoring operator like [2] to get these shipped up off of cluster. [1]: openshift/enhancements#922 (comment) [2]: openshift/cluster-monitoring-operator#1477
Fleet capability choices should make their way up to Red Hat via Insights uploads. But some clusters have Telemetry enabled but Insights disabled [1]. For these clusters, we'll want this data in Telemetry, and getting it into metrics (this commit) is the first step. After this lands, we'll need to update the monitoring operator like [2] to get these shipped up off of cluster. [1]: openshift/enhancements#922 (comment) [2]: openshift/cluster-monitoring-operator#1477
Fleet capability choices should make their way up to Red Hat via Insights uploads. But some clusters have Telemetry enabled but Insights disabled [1]. For these clusters, we'll want this data in Telemetry, and getting it into metrics (this commit) is the first step. After this lands, we'll need to update the monitoring operator like [2] to get these shipped up off of cluster. [1]: openshift/enhancements#922 (comment) [2]: openshift/cluster-monitoring-operator#1477
We need to receive some new metrics from the telemetry, for CSI shared
resource driver and operator. Amount of shared resourced (secrets and
config maps) and amount of shares mapped to pods, both succeeded and
failed.