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
MON-3231: add metric for the configured profile #2030
Conversation
rexagod
commented
Jul 2, 2023
- I added CHANGELOG entry for this change.
- No user facing changes, so no entry in CHANGELOG was needed.
@rexagod: No Jira issue with key MON-2301 exists in the tracker at https://issues.redhat.com/. In response to this:
Instructions 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. |
@rexagod: This pull request references MON-3231 which is a valid jira issue. In response to this:
Instructions 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. |
f254d61
to
700ac82
Compare
/test e2e-aws-ovn-single-node |
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.
Since collection profiles are gated via TechPreview, I would only expose the metric if tech preview is explicitly enabled.
I'd also recommend exposing all collection profile values, e.g.
cluster_monitoring_operator_collection_profile{..., collection_profile="full"} 1
cluster_monitoring_operator_collection_profile{..., collection_profile="minimal"} 0
Having 0 for all series would mean that the collection profile is misconfigured.
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.
Generally this looks good to me. Can you please add separate commits for the lint fix, the metrics refactor and for adding the new metric? This will make future change archeology much easier.
Also this does not add the telemetry config yet, we could add the CMO side for this here too?
One thing I'd like to raise for discussion: Should we maybe add a cluster_monitoring_operator_configuration
metric instead of single metrics for config options we're interested in? We're mostly interested in the label we set anyway and I think such a metadata metric can make it easier to add additional signals and send them to telemetry.
Briefly discussed in slack, individual metrics have clear benefits. |
@jan--f Does it sound good if do this once the PR is LGTM'd and good to merge? That way I can keep adding any lint fixes or refactors during further reviews and split them all in the end. |
ae68b0e
to
3538917
Compare
/lgtm |
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.
one last nit :)
* Allow govet on `Main()`. * Remove trailing whitespaces for telemetry metrics. * Reword description for `manifests.NewConfigFromString`.
move meta metrics under the `metrics` package.
add meta metric and telemeter signal that depicts the current state of the various collection profiles and the one that is active, respectively.
@rexagod: all tests passed! Full PR test history. Your PR dashboard. Instructions 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. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jan--f, rexagod The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold |