[chore][hostmetricsreceiver] Fix example config: uptime scraper renamed to system#46149
Merged
dmitryax merged 2 commits intoFeb 18, 2026
Conversation
The hostmetricsreceiver uptime scraper was renamed to system awhile ago. However, the sample config was never updated to match this, if the users uses `uptime` in their config the collector will not run as the `uptime` scraper is no longer present, this scraper has been renamed to system.
osullivandonal
requested review from
a team,
braydonk and
dmitryax
as code owners
paulojmdias
approved these changes
Feb 17, 2026
rogercoll
approved these changes
Feb 18, 2026
dmitryax
approved these changes
Feb 18, 2026
geekdave
pushed a commit
to oso-team/opentelemetry-collector-contrib
that referenced
this pull request
Feb 20, 2026
…ed to system (open-telemetry#46149) #### Description The hostmetricsreceiver `uptime` scraper was renamed to system awhile ago, see open-telemetry#36123 . However, the sample config was never updated to match this, if the users uses `uptime` in their config the collector will not run as the `uptime` scraper is no longer present, this scraper has been renamed to system. #### Using uptime ##### Config ```yaml extensions: zpages: endpoint: 0.0.0.0:55679 receivers: hostmetrics: collection_interval: 1m scrapers: ... uptime: exporters: debug: prometheus: endpoint: 0.0.0.0:8889 service: pipelines: metrics: receivers: [hostmetrics] exporters: [prometheus, debug] extensions: [zpages] ``` ##### Output ```bash opentelemetry-collector-contrib main ✗ make run otelcontribcol cd ./cmd/otelcontribcol && GO111MODULE=on go run --race . --config ../../local/config.yaml Error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s): 'receivers' error reading configuration for "hostmetrics": '' invalid scraper key: uptime exit status 1 make: *** [Makefile:359: run] Error 1 ``` #### Fix Use `system` instead of uptime, this is only an issue with the [example-config.yaml](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/hostmetricsreceiver/example_config.yaml?plain=1#L18) for hostmetrics, this work just renames `uptime` to `system`.
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
5 participants
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.
Description
The hostmetricsreceiver
uptimescraper was renamed to system awhile ago, see #36123 . However, the sample config was never updated to match this, if the users usesuptimein their config the collector will not run as theuptimescraper is no longer present, this scraper has been renamed to system.Using uptime
Config
Output
Fix
Use
systeminstead of uptime, this is only an issue with the example-config.yaml for hostmetrics, this work just renamesuptimetosystem.