Fix lifecycle late scan alerts - #2488
Conversation
Adding a label is needed to prevent automatic creation of a serie with value 0 on startup, in every pod which import LifecycleMetrics. We thus add the `origin` label, which may also be useful on S3C. Issue: BB-479
That metric is in seconds, like `time()`, and thus does not need to be divided by 1000 like s3_lifecycle_latest_batch_start_time. Issue: BB-479
The `s3_lifecycle_latest_batch_start_time` metric sometimes gets reset on shutdown, which breaks `last_over_time`: use `max_over_time` for now instead, as it should have roughly the same behavior, possibly with a slighly higher load, but avoids this issue. Issue: BB-479
Issue: BB-479
Hello francoisferrand,My role is to assist you with the merge of this Status report is not available. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
... and 1 file with indirect coverage changes
@@ Coverage Diff @@
## development/8.6 #2488 +/- ##
===================================================
- Coverage 63.13% 63.12% -0.01%
===================================================
Files 191 191
Lines 12619 12619
===================================================
- Hits 7967 7966 -1
- Misses 4642 4643 +1
Partials 10 10
Flags with carried forward coverage won't be shown. Click here to find out more. |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
|
/approve |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue BB-479. Goodbye francoisferrand. |
kube_service_createdin LifecycleLateScanmax_over_timefor LifecycleLateScan instead oflast_over_timeIssue: BB-479