Skip to content
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 lifecycle latency alerts #2480

Merged
merged 5 commits into from
Dec 7, 2023
Merged

Add lifecycle latency alerts #2480

merged 5 commits into from
Dec 7, 2023

Conversation

francoisferrand
Copy link
Contributor

  • Add transition processor alerts
  • Add late conductor scan alerts
  • Add lifecycle latency alert
  • Update tests
  • Release 8.6.31

Issue: BB-475

@bert-e
Copy link
Contributor

bert-e commented Dec 6, 2023

Hello francoisferrand,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Dec 6, 2023

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

Copy link

codecov bot commented Dec 6, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (4ff27cc) 63.12% compared to head (75f3691) 63.11%.

Additional details and impacted files

Impacted file tree graph

see 1 file with indirect coverage changes

Components Coverage Δ
Bucket Notification 65.61% <ø> (ø)
Core Library 62.14% <ø> (-0.02%) ⬇️
Ingestion 68.97% <ø> (ø)
Lifecycle 71.99% <ø> (ø)
Oplog Populator 73.87% <ø> (ø)
Replication 57.34% <ø> (ø)
Bucket Scanner 85.60% <ø> (ø)
@@                 Coverage Diff                 @@
##           development/8.6    #2480      +/-   ##
===================================================
- Coverage            63.12%   63.11%   -0.01%     
===================================================
  Files                  191      191              
  Lines                12616    12616              
===================================================
- Hits                  7964     7963       -1     
- Misses                4642     4643       +1     
  Partials                10       10              
Flag Coverage Δ
bucket-scanner 85.60% <ø> (ø)
ingestion 12.73% <ø> (ø)
lib 7.53% <ø> (-0.01%) ⬇️
lifecycle 19.31% <ø> (+0.01%) ⬆️
notification 0.90% <ø> (ø)
replication 19.66% <ø> (ø)
unit 40.94% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@francoisferrand
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Dec 7, 2023

Integration data created

I have created the integration data for the additional destination branches.

  • this pull request will merge improvement/BB-475 into
    development/8.6
  • w/8.7/improvement/BB-475 will be merged into development/8.7

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.5

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Dec 7, 2023

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/8.6

  • ✔️ development/8.7

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.5

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Dec 7, 2023

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/8.6

  • ✔️ development/8.7

The following branches have NOT changed:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.5

Please check the status of the associated issue BB-475.

Goodbye francoisferrand.

@bert-e bert-e merged commit 75f3691 into development/8.6 Dec 7, 2023
@bert-e bert-e deleted the improvement/BB-475 branch December 7, 2023 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants