-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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] Move scraper packages into scraper module #11003
Comments
As an example of a PR adding a new module, see #11000. |
Hi @mx-psi , i would like to try. |
@zzzk1 Please give it a try! :) |
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Migrates existing scrapererror code to new scraper package. Sets aliases for receiver/scrapererror so that dependent code in contrib and elsewhere can be updated <!-- Issue number if applicable --> #### Link to tracking issue Relates to #11003 <!--Describe what testing was performed and which tests were added.--> #### Testing included unit/integration tests should suffice <!--Describe the documentation added.--> #### Documentation changelog yaml <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Pablo Baeyens <[email protected]> Co-authored-by: Pablo Baeyens <[email protected]>
One of the next steps would be to remove |
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Remove references of `receiver/scrapererror` and replace with `scraper/scrapererror` <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Relates to open-telemetry/opentelemetry-collector#11003 <!--Describe what testing was performed and which tests were added.--> #### Testing None <!--Describe the documentation added.--> #### Documentation None <!--Please delete paragraphs that you did not use before submitting.-->
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Remove receiver/scrapererror alias <!-- Issue number if applicable --> #### Link to tracking issue Relates to #11003 <!--Describe what testing was performed and which tests were added.--> #### Testing None <!--Describe the documentation added.--> #### Documentation Added <!--Please delete paragraphs that you did not use before submitting.-->
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Remove references of `receiver/scrapererror` and replace with `scraper/scrapererror` <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Relates to open-telemetry/opentelemetry-collector#11003 <!--Describe what testing was performed and which tests were added.--> #### Testing None <!--Describe the documentation added.--> #### Documentation None <!--Please delete paragraphs that you did not use before submitting.-->
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Remove references of `receiver/scrapererror` and replace with `scraper/scrapererror` <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Relates to open-telemetry/opentelemetry-collector#11003 <!--Describe what testing was performed and which tests were added.--> #### Testing None <!--Describe the documentation added.--> #### Documentation None <!--Please delete paragraphs that you did not use before submitting.-->
#11800 removed scrapererror aliases; looks like |
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Remove references of `receiver/scrapererror` and replace with `scraper/scrapererror` <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Relates to open-telemetry/opentelemetry-collector#11003 <!--Describe what testing was performed and which tests were added.--> #### Testing None <!--Describe the documentation added.--> #### Documentation None <!--Please delete paragraphs that you did not use before submitting.-->
…metry#11733) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Migrates existing scrapererror code to new scraper package. Sets aliases for receiver/scrapererror so that dependent code in contrib and elsewhere can be updated <!-- Issue number if applicable --> #### Link to tracking issue Relates to open-telemetry#11003 <!--Describe what testing was performed and which tests were added.--> #### Testing included unit/integration tests should suffice <!--Describe the documentation added.--> #### Documentation changelog yaml <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Pablo Baeyens <[email protected]> Co-authored-by: Pablo Baeyens <[email protected]>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Remove receiver/scrapererror alias <!-- Issue number if applicable --> #### Link to tracking issue Relates to open-telemetry#11003 <!--Describe what testing was performed and which tests were added.--> #### Testing None <!--Describe the documentation added.--> #### Documentation Added <!--Please delete paragraphs that you did not use before submitting.-->
We have two packages,
scrapererror
andscraperhelper
that are part of the receiver module, but are not necessary for Collector v1 (we only intend to stabilize the OTLP receiver at first).We can make a new
receiver/scraper
module that has these two as packages. This would reduce the API surface that we have to stabilize.The text was updated successfully, but these errors were encountered: