Repository navigation
Fix oplog populator alerts and panels that never fire - #2889
Conversation
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
@@ Coverage Diff @@
## development/9.6 #2889 +/- ##
===================================================
+ Coverage 81.80% 81.93% +0.13%
===================================================
Files 216 216
Lines 45313 45313
===================================================
+ Hits 37067 37127 +60
+ Misses 8246 8186 -60
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
63d0d53 to
953073a
Compare
953073a to
34584ac
Compare
34584ac to
9c4d376
Compare
9c4d376 to
f299383
Compare
f299383 to
b454c2e
Compare
b454c2e to
55b29bb
Compare
55b29bb to
8916382
Compare
fc7e518 to
a3f8931
Compare
a3f8931 to
f92143b
Compare
|
Requesting @benzekrimaha since Francois Ferrand is on PTO |
a15cbaf to
c0f6861
Compare
c0f6861 to
6115700
Compare
6115700 to
38d40a3
Compare
38d40a3 to
7d4c0f0
Compare
7d4c0f0 to
578914d
Compare
Found while exercising the dashboard on a dev ARTESCA: - KafkaConnectFailedConnectors, KafkaConnectFailedConnectorConfiguration and OplogPopulatorMetastoreChangeStreamLagThreshold used 1m windows, which hold a single sample with the 60s scrape interval: rate and increase were always empty. KafkaConnectFailedConnectorConfiguration also queried a metric that does not exist. - OplogPopulatorUnavailable fired on a single failed scrape: the up=0 sample remains for the 60s scrape interval, longer than its 30s for. The alert tests now evaluate every 30s, as deployed. - The instance stats kept showing their last value when no pod exists. Issue: BB-906
Issue: BB-906
578914d to
9ab331d
Compare
|
/approve |
|
!done 5d |
|
!release |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
This pull request did not target the following hotfix branch(es) so they
Please check the status of the associated issue BB-906. Goodbye delthas. The following options are set: approve |
|
Release summary:
|
|
|
All preexisting issues, found when testing the oplog populator dashboard:
up=0sample stays for the 60s scrape interval, longer than its 30sfor. It now waits 2m.The last commit releases 9.6.0, which closes the hashed oplog ingestion stack.
Part of the hashed oplog ingestion stack, overview in #2869.
Issue: BB-906