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

Integrate nginxreceiver #9572

Merged
merged 14 commits into from
May 4, 2022
Merged

Integrate nginxreceiver #9572

merged 14 commits into from
May 4, 2022

Conversation

nslaughter
Copy link
Contributor

@nslaughter nslaughter commented Apr 28, 2022

Description:
The nginx receiver was not previously included in the registration of components in internal/components/components.go and therefore was not building in the collector.

Link to tracking Issue:
issue 108 in the releases repo explains.

Testing:
There were pre-existing unit and integration tests of the package which were passing and continue to pass after changes. I also added an entry for this receiver in internal/components/receivers_test.go, which tests the receiver lifecycle. I also used the functionality to send metrics in a live environment.

Documentation:
I have not expanded upon existing documentation.

@nslaughter nslaughter requested review from a team and codeboten April 28, 2022 18:09
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Apr 28, 2022

CLA Signed

The committers listed above are authorized under a signed CLA.

@pmm-sumo
Copy link
Contributor

Thank you for the contribuion @nslaughter, could you sign the CLA per the contributing guidelines?

@nslaughter
Copy link
Contributor Author

Thank you for the contribuion @nslaughter, could you sign the CLA per the contributing guidelines?

Indeed. It's in progress with company approver.

Copy link
Contributor

@codeboten codeboten left a comment

Choose a reason for hiding this comment

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

Looks like something happen during rebase, please fix

This enables using the nginxreceiver in the collector built from this
repo.
First `make tidy` in the cmd/configschema module then add the replace
directive on receiver/nginxreceiver using the relative path.
@nslaughter
Copy link
Contributor Author

Thank you. It's fixed.

@dmitryax
Copy link
Member

dmitryax commented May 2, 2022

Please resolve conflicts

@nslaughter
Copy link
Contributor Author

I'm tending to CI issues blocking now. ty.

go.mod Outdated Show resolved Hide resolved
@dmitryax
Copy link
Member

dmitryax commented May 3, 2022

@nslaughter please also sign CLA to be able to contribute in OTel

@nslaughter nslaughter requested a review from codeboten May 3, 2022 20:34
Copy link
Contributor

@codeboten codeboten left a comment

Choose a reason for hiding this comment

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

Just a minor comment, otherwise this looks good

internal/components/receivers_test.go Outdated Show resolved Hide resolved
@codeboten codeboten merged commit bcbf2db into open-telemetry:main May 4, 2022
djaglowski pushed a commit to djaglowski/opentelemetry-collector-contrib that referenced this pull request May 10, 2022
* Add nginxreceiver factory to components

This enables using the nginxreceiver in the collector built from this
repo.

* Import nginxreceiver in components

* add replace rule for nginxreceiver in go.mod && make tidy

* update go.mod in cmd/configschema

First `make tidy` in the cmd/configschema module then add the replace
directive on receiver/nginxreceiver using the relative path.

* Add nginx check to receivers_test.go

* gofmt components.go

* Add nginx-receiver to go.mod in root and configcshema

* Add bug fix to CHANGELOG

* Remove errant linespace in receivers_test

* Require nginxreceiver v0.50.0 in go.mod

Co-authored-by: Alex Boten <aboten@lightstep.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants