Skip to content

docs: fix typo in OpenMetrics 2.0 migration guide #3125

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

Merged
bwplotka merged 2 commits into from
Oct 28, 2026
Merged

docs: fix typo in OpenMetrics 2.0 migration guide #3125

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8fc5eb3
docs: fix typo in OpenMetrics 2.0 migration guide
Rohit-Singh-01 Oct 4, 2026
8ce8002
docs: keep the trailing blank line at end of file
Rohit-Singh-01 Oct 4, 2026
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
Next Next commit
docs: fix typo in OpenMetrics 2.0 migration guide 
Signed-off-by: rohit singh <145866377+Rohit-Singh-01@users.noreply.github.com>
  • Loading branch information
@Rohit-Singh-01
Rohit-Singh-01 authored Oct 4, 2026
commit 8fc5eb3a40352aa28ac535567fbe5a554627243f
3 changes: 1 addition & 2 deletions docs/guides/open_metrics_2_0_migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ There are also references to the relevant section of the specification if more d

## Quick Reference

OpenMetrics 2.0 contains many changes. Some of those changes are a loosening of previously-strict requirements, like the way metric names are constructed or character limits. Some of these changes are in service of allowing OpenTelemetry metric data to be encoded in OpenMetrics without violating the specification. Other changes improve scraper (e.g. Prometheus) efficiency and reliablity on various cases. Changes introduce new syntaxes, mostly focused on allowing metric data to be encoded into a single line rather than requiring multiple lines to describe one cohesive piece of information. Lastly, some changes add new features and data types, like Native Histograms.
OpenMetrics 2.0 contains many changes. Some of those changes are a loosening of previously-strict requirements, like the way metric names are constructed or character limits. Some of these changes are in service of allowing OpenTelemetry metric data to be encoded in OpenMetrics without violating the specification. Other changes improve scraper (e.g. Prometheus) efficiency and reliability on various cases. Changes introduce new syntaxes, mostly focused on allowing metric data to be encoded into a single line rather than requiring multiple lines to describe one cohesive piece of information. Lastly, some changes add new features and data types, like Native Histograms.

| Change | 1.0 | 2.0 | Breaking? |
| -------------------------------------------------------------------------------- | ---------------------------------------- | -------------------------------------------------- | --------- |
Expand Down Expand Up @@ -603,4 +603,3 @@ In OM 1.0, a Sample in a Metric with the Unknown type could only have a Number v
Since the Unknown type should not be used in general (it exists for third-party metrics where the type is indeterminate), this is a minor change. It primarily affects ingestors and libraries that need to handle arbitrary Unknown-typed data.

See: [Unknown](../specs/om/open_metrics_spec_2_0.md#unknown) in the OM 2.0 spec.