Uh oh!
There was an error while loading. Please reload this page.
🌱 Add prometheus to e2e workflow - #1928
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@## main #1928 +/- ##
==========================================
+ Coverage 69.21% 69.26% +0.04%
==========================================
Files 79 79 Lines 7037 7051 +14 ==========================================
+ Hits 4871 4884 +13
Misses 1885 1885 - Partials 281 282 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
tmshort
commented
Apr 18, 2025
So, this adds a new e2e that isn't run downstream? There's no workflow to run it in upstream CI? |
Uh oh!
There was an error while loading. Please reload this page.
dtfranz
commented
Apr 21, 2025
Yes - it currently only adds prometheus to the environment when you run the new e2e target, so I've kept the workflow the same for now. If you'd prefer I'm happy to make that change here - it doesn't add much overhead to the e2e at all. |
6c32ce6 to
b51c814CompareUh oh!
There was an error while loading. Please reload this page.
2daa74b to
e8b18c9Comparebb99737 to
b7e65a7CompareUh oh!
There was an error while loading. Please reload this page.
| egress: | ||
| - {} # Allows all egress traffic for metrics requests | ||
| ingress: | ||
| - {} # Allows us to query prometheus |
There was a problem hiding this comment.
I understand that we need this NP to allow us to get data from Prometheus integrate it with Grafana and etc. So, I am OK with 👍
There was a problem hiding this comment.
Thank you for the nice work. 🎉
I understand that we will need to improve it in the long run and that is just teh first step for we have the targets and quick start.
So, I just added a nit: #1928 (comment) but otherwise I am OK with it. LGTM
We might also want to have a second look and help from @tmshort too
dtfranz
commented
Jun 12, 2025
I reran it and it passed, seems a test flaked 🫤 |
Adds prometheus to the test-e2e Makefile target, which stands up a barebones prometheus scraper to gather metrics from the operator-controller and catalogd pods during the e2e test run. When finished, the prometheus server is queried for a raw output of the metrics and stores it in metrics.out. These metrics will be analyzed in a later PR. Signed-off-by: Daniel Franz <dfranz@redhat.com>
camilamacedo86
commented
Jun 23, 2025
/lgtm |
tmshort
commented
Jun 24, 2025
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tmshort 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 |
Description
Closes#1902 and #1903
Adds prometheus to the
test-e2eMakefile target, which stands up a barebones prometheus scraper to gather metrics from the operator-controller and catalogd pods during the e2e test run. When finished, the prometheus server is queried for a raw output of the metrics and stores it inARTIFACTS_PATH/metrics.out. These metrics will be analyzed in a later PR.Reviewer Checklist