-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Integrate nginxreceiver #9572
Conversation
Thank you for the contribuion @nslaughter, could you sign the CLA per the contributing guidelines? |
Indeed. It's in progress with company approver. |
There was a problem hiding this 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.
Thank you. It's fixed. |
Please resolve conflicts |
I'm tending to CI issues blocking now. ty. |
@nslaughter please also sign CLA to be able to contribute in OTel |
There was a problem hiding this 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
* 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>
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.