Skip to content

Update links to openmetrics to reference the v1.0.0 release #2426

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.

Sign up for GitHub

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

Closed
dashpole wants to merge 1 commit into from
Closed

Update links to openmetrics to reference the v1.0.0 release #2426

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions opentelemetry-proto/src/proto/tonic/opentelemetry.proto.metrics.v1.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -437,7 +437,7 @@ pub struct HistogramDataPoint {
/// events, and is assumed to be monotonic over the values of these events.
/// Negative events *can* be recorded, but sum should not be filled out when
/// doing so. This is specifically to enforce compatibility w/ OpenMetrics,
/// see: <https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#histogram>
/// see: <https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#histogram>
#[prost(double, optional, tag = "5")]
pub sum: ::core::option::Option<f64>,
/// bucket_counts is an optional field contains the count values of histogram
Expand Down Expand Up @@ -520,7 +520,7 @@ pub struct ExponentialHistogramDataPoint {
/// events, and is assumed to be monotonic over the values of these events.
/// Negative events *can* be recorded, but sum should not be filled out when
/// doing so. This is specifically to enforce compatibility w/ OpenMetrics,
/// see: <https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#histogram>
/// see: <https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#histogram>
#[prost(double, optional, tag = "5")]
pub sum: ::core::option::Option<f64>,
/// scale describes the resolution of the histogram. Boundaries are
Expand Down Expand Up @@ -643,7 +643,7 @@ pub struct SummaryDataPoint {
/// events, and is assumed to be monotonic over the values of these events.
/// Negative events *can* be recorded, but sum should not be filled out when
/// doing so. This is specifically to enforce compatibility w/ OpenMetrics,
/// see: <https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#summary>
/// see: <https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#summary>
#[prost(double, tag = "5")]
pub sum: f64,
/// (Optional) list of values at different quantiles of the distribution calculated
Expand Down
2 changes: 1 addition & 1 deletion opentelemetry-semantic-conventions/src/metric.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1836,7 +1836,7 @@ pub const HW_POWER: &str = "hw.power";
///
/// ## Notes
///
/// `hw.status` is currently specified as an *UpDownCounter* but would ideally be represented using a [*StateSet* as defined in OpenMetrics](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#stateset). This semantic convention will be updated once *StateSet* is specified in OpenTelemetry. This planned change is not expected to have any consequence on the way users query their timeseries backend to retrieve the values of `hw.status` over time
/// `hw.status` is currently specified as an *UpDownCounter* but would ideally be represented using a [*StateSet* as defined in OpenMetrics](https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#stateset). This semantic convention will be updated once *StateSet* is specified in OpenTelemetry. This planned change is not expected to have any consequence on the way users query their timeseries backend to retrieve the values of `hw.status` over time
/// ## Metadata
/// | | |
/// |:-|:-
Expand Down
Loading