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

Backport of VAULT-17555: Secret sync client metrics into release/1.16.x #25741

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #25713 to be assessed for backporting due to the inclusion of the label backport/1.16.x.

The below text is copied from the body of the original PR.


This PR refactors the metrics reporting from the activity log to move it to a separate function. I've also added a test and two new metrics for secret sync.

The documentation for the new metrics will be in a separate PR, along with the rest of the secret sync client count documentation.


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/miagilepner/activity-secret-sync-metrics/separately-wise-shrimp branch from 8fbea0c to cf47477 Compare March 1, 2024 09:42
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Mar 1, 2024
@miagilepner miagilepner enabled auto-merge (squash) March 1, 2024 09:43
Copy link

github-actions bot commented Mar 1, 2024

CI Results:
All Go tests succeeded! ✅

Copy link

github-actions bot commented Mar 1, 2024

Build Results:
All builds succeeded! ✅

@miagilepner miagilepner merged commit e25d4a9 into release/1.16.x Mar 1, 2024
74 of 76 checks passed
@miagilepner miagilepner deleted the backport/miagilepner/activity-secret-sync-metrics/separately-wise-shrimp branch March 1, 2024 10:03
@miagilepner miagilepner added this to the 1.16.0-rc3 milestone Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants