Skip to content

Commit e3926e2

Browse files
committed
update links to openmetrics to reference the v1.0.0 release
Signed-off-by: David Ashpole <[email protected]>
1 parent d88ee1f commit e3926e2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

expfmt/openmetrics_create.go

+2-2
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ type EncoderOption func(*encoderOption)
3838

3939
// WithCreatedLines is an EncoderOption that configures the OpenMetrics encoder
4040
// to include _created lines (See
41-
// https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#counter-1).
41+
// https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#counter-1).
4242
// Created timestamps can improve the accuracy of series reset detection, but
4343
// come with a bandwidth cost.
4444
//
@@ -102,7 +102,7 @@ func WithUnit() EncoderOption {
102102
//
103103
// - According to the OM specs, the `# UNIT` line is optional, but if populated,
104104
// the unit has to be present in the metric name as its suffix:
105-
// (see https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#unit).
105+
// (see https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#unit).
106106
// However, in order to accommodate any potential scenario where such a change in the
107107
// metric name is not desirable, the users are here given the choice of either explicitly
108108
// opt in, in case they wish for the unit to be included in the output AND in the metric name

0 commit comments

Comments
 (0)