Skip to content
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.

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

[receiver/hostmetrics]: change uptime scraper to system scraper #36123

Merged
merged 5 commits into from
Nov 5, 2024

Conversation

braydonk
Copy link
Contributor

Description

This PR makes some changes that I had hoped to suggest on #35954, however I was unable to make my comment in time before the PR was merged.

The changes this PR makes are:

  • The uptime scraper is changed to be named system
  • The scraper is registered using the scraper name when adding to the scrapercontroller

Link to tracking issue

Amends the fix to #31627 (following a comment I made on #35932)

Testing

Documentation

The documentation that was added for the uptime scraper was renamed accordingly, and the description adjusted.

This PR makes some changes that I had hoped to suggest on the PR that
introduced the uptime scraper, however I was unable to make my comment
in time before the PR was merged.

* The `uptime` scraper is changed to be named `system`
* The scraper is registered using the scraper name when adding to the
  scrapercontroller
@braydonk
Copy link
Contributor Author

I am ideally hoping that this change makes it in before a new OTel Collector is tagged so that no users start using uptime scrapers in their configs.

@braydonk
Copy link
Contributor Author

I would like to skip changelog, because in this case what I did was modified the existing changelog to reflect this new change.

@braydonk
Copy link
Contributor Author

@kevinnoel-be I am unable to officially add you as a reviewer on this PR, but if you have a second to take a look I would appreciate it!

@kevinnoel-be
Copy link
Contributor

@braydonk looks good to me except for the use of one (test) module where I think it should be testify instead?

@atoulme atoulme added the Skip Changelog PRs that do not require a CHANGELOG.md entry label Nov 1, 2024
Copy link
Contributor

@atoulme atoulme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, LGTM

@djaglowski djaglowski merged commit 219011b into open-telemetry:main Nov 5, 2024
158 checks passed
@github-actions github-actions bot added this to the next release milestone Nov 5, 2024
michael-burt pushed a commit to michael-burt/opentelemetry-collector-contrib that referenced this pull request Nov 7, 2024
…-telemetry#36123)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
This PR makes some changes that I had hoped to suggest on open-telemetry#35954,
however I was unable to make my comment in time before the PR was
merged.

The changes this PR makes are:
* The `uptime` scraper is changed to be named `system`
* The scraper is registered using the scraper name when adding to the
scrapercontroller

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Amends the fix to open-telemetry#31627 (following a comment I made on open-telemetry#35932)

<!--Describe what testing was performed and which tests were added.-->
#### Testing

<!--Describe the documentation added.-->
#### Documentation

The documentation that was added for the `uptime` scraper was renamed
accordingly, and the description adjusted.

<!--Please delete paragraphs that you did not use before submitting.-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
receiver/hostmetrics Skip Changelog PRs that do not require a CHANGELOG.md entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants