-
Notifications
You must be signed in to change notification settings - Fork 731
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
deprecate request_count/request_duration_seconds and document in release notes #1010
Comments
Per this comment thread, I believe we can narrow the scope of this bug to only adding the following metrics:
Per @sozercan's initial comment, these will live alongside The As the |
SGTM. Just want to make sure it's visible so we call out in the release notes. Then in a future release we can remove |
I now realize that I misunderstood this bug. Both All that's left to do to close out this bug is remove the
All of which are already implemented in @sozercan, do you know when the "deprecation period" ends? Can we remove |
Looks like we already announced this in v3.4.0 notes: https://github.com/open-policy-agent/gatekeeper/releases/tag/v3.4.0 I think it's okay to remove them in next release (v3.6). @maxsmythe thoughts? |
SGTM! |
As g8r once had only a validation webhook, certain metrics (request_count, request_count_duration_seconds) were implemented without qualifiers. i.e., the fact that they applied to the validation webhook was _assumed_. As g8r now has both validation and mutation webhooks, separate metrics for both are required. These metrics have already been implemented, and have been released since v3.4.0. The original metrics were deprecated (but retained) at the time of that release. As we are approaching v3.6, it is finally time to remove these metrics. This PR removes the code and updates the metrics README. Fixes open-policy-agent#1010 Signed-off-by: juliankatz <juliankatz@google.com>
@sozercan @maxsmythe I've put up a PR to remove these. PTAL |
As g8r once had only a validation webhook, certain metrics (request_count, request_count_duration_seconds) were implemented without qualifiers. i.e., the fact that they applied to the validation webhook was _assumed_. As g8r now has both validation and mutation webhooks, separate metrics for both are required. These metrics have already been implemented, and have been released since v3.4.0. The original metrics were deprecated (but retained) at the time of that release. As we are approaching v3.6, it is finally time to remove these metrics. This PR removes the code and updates the metrics README. Fixes #1010 Signed-off-by: juliankatz <juliankatz@google.com>
As g8r once had only a validation webhook, certain metrics (request_count, request_count_duration_seconds) were implemented without qualifiers. i.e., the fact that they applied to the validation webhook was _assumed_. As g8r now has both validation and mutation webhooks, separate metrics for both are required. These metrics have already been implemented, and have been released since v3.4.0. The original metrics were deprecated (but retained) at the time of that release. As we are approaching v3.6, it is finally time to remove these metrics. This PR removes the code and updates the metrics README. Fixes open-policy-agent#1010 Signed-off-by: juliankatz <juliankatz@google.com>
Describe the solution you'd like
As discussed in https://github.com/open-policy-agent/gatekeeper/pull/976/files#r529165013, we will be deprecating
request_count
andrequest_duration_seconds
metrics (which is validation only) tovalidation_request_count
/validation_request_duration_seconds
andmutation_request_count
/mutation_request_duration_seconds
.We will publish all 3 metrics initially (no prefix,
validation_
andmutation_
prefixes). No prefix andvalidation_
prefixes will be reporting same values. After deprecation period ends,request_count
andrequest_duration_seconds
metrics will be removed.Document this in next release notes and metrics docs.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: