docs(metrics): fix object-storage exporter URI examples - #3525
Open
hachiwar wants to merge 1 commit into
Open
Conversation
hachiwar
marked this pull request as ready for review
August 14, 2026 09:58
hachiwar
requested review from
1sonofqiu,
Gezi-lzq,
superhx and
woshigaopp
as code owners
August 14, 2026 09:58
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The metrics README documents the object-storage exporter with an
s3://URI containing credentials. The parser recognizes this built-in exporter by theopsscheme and obtains object-storage access fromMetricsExportConfig.objectStorage().What
s3://examples withops://?How
The examples now match
MetricsExporterType.OPSand the existingMetricsExporterURIdispatch path.Reviewer notes
Documentation-only change. No runtime behavior changes.
Testing
ops://?s3://access-keyexample