Skip to content

docs: update metrics README to reflect current migration status#677

Merged
tgross merged 1 commit intohashicorp:mainfrom
goingforstudying-ctrl:fix/update-metrics-readme
Apr 24, 2026
Merged

docs: update metrics README to reflect current migration status#677
tgross merged 1 commit intohashicorp:mainfrom
goingforstudying-ctrl:fix/update-metrics-readme

Conversation

@goingforstudying-ctrl
Copy link
Copy Markdown
Contributor

Summary

Updates the README to accurately reflect the current state of the metrics library migration.

Changes

  • Added a note explaining that as of mid-2026, the default behavior has not yet changed to hashicorp/go-metrics
  • Clarified that the hashicorpmetrics build tag is still required to use hashicorp/go-metrics
  • Removed the outdated mid-2025 timeline reference that was misleading users

Motivation

The README stated that the default would change by mid-2025 and that the hashicorpmetrics build tag could be dropped at that point. However, as noted in #676, this migration has not been completed. This documentation update prevents confusion for users who expect the default to have changed.

Fixes #676

@goingforstudying-ctrl goingforstudying-ctrl requested review from a team as code owners April 23, 2026 09:14
@hashicorp-cla-app
Copy link
Copy Markdown

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

Comment thread README.md Outdated
Comment on lines +134 to +136
Emitting metrics to `armon/go-metrics` is officially deprecated. Usage of `armon/go-metrics` will remain the default until mid-2025 with opt-in support continuing to the end of 2025.

**Note:** As of mid-2026, the default behavior has not yet changed to `hashicorp/go-metrics`. The `hashicorpmetrics` build tag is still required to use `hashicorp/go-metrics`. We are actively working on completing this migration and will update this documentation when the default changes. Please continue to use the `hashicorpmetrics` build tag if you want to opt into `hashicorp/go-metrics`.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leaving the note about 2025 above doesn't make sense. I'd probably just change this to something like:

Emitting metrics to armon/go-metrics is officially deprecated, but usage of armon/go-metrics is still the default. Please continue to use the hashicorpmetrics build tag if you want to opt into hashicorp/go-metrics. #676 will have status updates on the migration.

- Add note explaining that the default behavior has not yet changed
to hashicorp/go-metrics as of mid-2026
- Clarify that hashicorpmetrics build tag is still required
- Remove outdated mid-2025 timeline reference
- Fixes hashicorp#676
@goingforstudying-ctrl
Copy link
Copy Markdown
Contributor Author

@tgross Thanks for the review! I've updated the text to be more concise as you suggested. Removed the redundant mid-2025/mid-2026 timeline references and linked directly to #676 for migration status updates. Please take another look when you have a chance.

@goingforstudying-ctrl
Copy link
Copy Markdown
Contributor Author

@tgross Done! Updated the text to exactly match your suggestion. Removed the mid-2025 timeline references and linked directly to #676 for migration status. Let me know if anything else needs adjustment.

@tgross tgross merged commit ce1d06b into hashicorp:main Apr 24, 2026
1 check was pending
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.

hashicorpmetrics build tag required passed mid-2025 deadline

2 participants