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 Raft/fix raft telemetry metric unit into release/1.8.x #13761

Conversation

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

Backport

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

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

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


This PR is to update the Units being reported for the following Telemetry Metrics from Nanoseconds to Milliseconds to match documentation:

  1. vault.raft_storage.bolt.rebalance.time
  2. vault.raft_storage.bolt.spill.time
  3. vault.raft_storage.bolt.write.time

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/raft/fix-raft-telemetry-metric-unit/socially-funky-mayfly branch from 4946dee to af2daee Compare January 24, 2022 15:52
@vercel vercel bot temporarily deployed to Preview – vault January 24, 2022 15:53 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook January 24, 2022 16:01 Inactive
@vercel vercel bot temporarily deployed to Preview – vault January 24, 2022 16:02 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook January 24, 2022 16:05 Inactive
@ncabatoff ncabatoff merged commit 118bce8 into release/1.8.x Jan 24, 2022
@ncabatoff ncabatoff deleted the backport/raft/fix-raft-telemetry-metric-unit/socially-funky-mayfly branch January 24, 2022 16:57
@mladlow mladlow added this to the 1.8.8 milestone Jan 24, 2022
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.

None yet

4 participants