-
Notifications
You must be signed in to change notification settings - Fork 545
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
Add experimental metrics to e2e runs #2435
Add experimental metrics to e2e runs #2435
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awgreene 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 |
Wanted to get a basic implementation up quickly, will be working on the variable names and the structure of the code. |
10277d3
to
eac4737
Compare
e734678
to
41d0002
Compare
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.
Just a quick review + played around with this locally and was able to extract the metrics during an e2e run from the olm-operator deployment, and I think the build tag implementation is the right approach.
I had a couple of quick thoughts and comments:
- Do we need to update the tes/e2e/README.md for how to interact with these metrics?
- Should we scope down the introduction of these metrics to only CI until we have a need for them outside of ephemeral environments?
Makefile
Outdated
@@ -84,6 +85,7 @@ build-coverage: clean $(CMDS) | |||
|
|||
build-linux: build_cmd=build | |||
build-linux: arch_flags=GOOS=linux GOARCH=386 | |||
build-linux: BUILD_TAGS="json1 experimental_metrics" |
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.
Any idea on why we need to update the build-linux target as well? At a glance locally, it doesn't look like this is used anywhere to drive CI.
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 believe the e2e test relies on the e2e-kind GitHub Workflow, which calls therun-local
target here, which calls the build-linux target here.
This change might be better placed in the run-local
target, thoughts?
d70ab6e
to
2fb92a2
Compare
2fb92a2
to
4dfb244
Compare
6f20711
to
9220e09
Compare
/retest |
1 similar comment
/retest |
@awgreene It looks like the the DCO check still needs to be addressed. |
/retest |
eb5e80c
to
00c9430
Compare
1f647b7
to
a8bfed0
Compare
This commit introduces a series of metrics that are only recorded when OLM is built with the experimental_metrics build tag. The metrics introduced in this commit includes namespace/name information of the request being reconciled by a series of controllers. These experimental metrics are enabled by default in the e2e-local target defined in the project's Makefile. Signed-off-by: Alexander Greene <greene.al1991@gmail.com>
a8bfed0
to
7650b0a
Compare
/lgtm |
Adds counter metric for each sync performed by controller. Example: