[receiver/hostmetrics] docs: correct deprecation notice #16097
Merged
Conversation
This file contains 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
Between v0.64.0 and v0.66.0, the new metrics are not enabled by default.
dmitryax
approved these changes
Nov 7, 2022
andrzej-stencel
deleted the
receiver-hostmetrics-docs-correct-deprecation-notice
branch
6 tasks
dineshg13
pushed a commit
to DataDog/opentelemetry-collector-contrib
that referenced
this pull request
Nov 21, 2022
…ry#16097) Between v0.64.0 and v0.66.0, the new metrics are not enabled by default.
shalper2
pushed a commit
to shalper2/opentelemetry-collector-contrib
that referenced
this pull request
Dec 6, 2022
…ry#16097) Between v0.64.0 and v0.66.0, the new metrics are not enabled by default.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to #14927
Fixing incorrect information in the deprecation notice about the process memory metrics: between v0.64.0 and v0.66.0, the new metrics are not enabled by default.
This must have crept in during a rebase, or I just missed the docs update when changing this.