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

Add statsd receiver #364

Merged
merged 2 commits into from
Aug 19, 2021
Merged

Add statsd receiver #364

merged 2 commits into from
Aug 19, 2021

Conversation

VineethReddy02
Copy link
Contributor

@VineethReddy02 VineethReddy02 commented Jul 28, 2021

Statsd receiver
As part of #128

@VineethReddy02 VineethReddy02 requested review from a team and bogdandrutu July 28, 2021 20:42
Copy link
Member

@jpkrohling jpkrohling left a comment

Choose a reason for hiding this comment

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

LGTM, just changed the wording on the contributing guide a bit.

CONTRIBUTING.md Outdated
@@ -85,6 +85,8 @@ For a general overview of the directories from this operator and what to expect

Your contribution is welcome! For it to be accepted, we have a few standards that must be followed.

If you are contributing to sync the receivers from [otel-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib). Operator only syncs receivers that aren't scrapers. As operator has nothing to do with scrapers. whereas with general receivers, operator exposes the port in kubernetes service object as specified in the receiver's config.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
If you are contributing to sync the receivers from [otel-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib). Operator only syncs receivers that aren't scrapers. As operator has nothing to do with scrapers. whereas with general receivers, operator exposes the port in kubernetes service object as specified in the receiver's config.
If you are contributing to sync the receivers from [otel-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib), note that the operator only synchronizes receivers that aren't scrapers, as there's no need to open ports in services for this case. In general, receivers would open a UDP/TCP port and the operator should be adding an entry in the Kubernetes Service resource accordingly.

@jpkrohling
Copy link
Member

@VineethReddy02 what's the status of this one?

@VineethReddy02
Copy link
Contributor Author

I will update the suggested change and will rebase the PR. :)

@jpkrohling jpkrohling merged commit a5bdca1 into open-telemetry:main Aug 19, 2021
shree007 pushed a commit to shree007/opentelemetry-operator that referenced this pull request Dec 12, 2021
* add statsd receiver

* update notes on syncing up receivers in CONTRIBUTING.md
ItielOlenick pushed a commit to ItielOlenick/opentelemetry-operator that referenced this pull request May 1, 2024
* add statsd receiver

* update notes on syncing up receivers in CONTRIBUTING.md
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.

2 participants