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/libhoney] New receiver for libhoney #36706

Merged
merged 12 commits into from
Dec 11, 2024

Conversation

mterhar
Copy link
Member

@mterhar mterhar commented Dec 6, 2024

Description

Creates a new receiver that accepts libhoney traffic as either logs or traces.

This PR doesn't do the conversion yet. Just contains configurations and some factory components.

Link to tracking issue

#36693

@mterhar mterhar requested a review from a team as a code owner December 6, 2024 15:26
@mterhar
Copy link
Member Author

mterhar commented Dec 6, 2024

sorry for the noise @bogdandrutu with all the rebuilds. Was having some trouble with the linter running locally and had to rely on CI 😬

This is just the scaffolding for the new receiver. Is there anything else to do on this PR?

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.

thanks @mterhar, just a couple of comments

receiver/libhoneyreceiver/README.md Outdated Show resolved Hide resolved
receiver/libhoneyreceiver/README.md Outdated Show resolved Hide resolved
@mterhar mterhar force-pushed the new-libhoney-receiver branch from bf5729f to d987e08 Compare December 9, 2024 18:34
@mterhar mterhar force-pushed the new-libhoney-receiver branch from d987e08 to 78f21aa Compare December 10, 2024 17:15
return nil
}

if r.nextTraces != nil {
Copy link
Contributor

Choose a reason for hiding this comment

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

not sure if this log is needed here

Copy link
Member Author

Choose a reason for hiding this comment

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

I just needed something there so it wouldn't complain about a useless if statement. It'll be removed when the handler code is added.

receiver/libhoneyreceiver/go.mod Outdated Show resolved Hide resolved
},
AuthAPI: "",
Resources: ResourcesConfig{
ServiceName: "service.name",
Copy link
Contributor

Choose a reason for hiding this comment

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

could these strings be pulled from semconv packages?

Copy link
Member Author

Choose a reason for hiding this comment

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

The point of these is to be able to map non-semconv service name strings into a the semconv named string.

The use of service.name here as a default is just because people may have already changed their service name fields to match what OTEL uses and we want to honor that unless they want to configure an override.

@TylerHelmuth TylerHelmuth merged commit ab0f6a2 into open-telemetry:main Dec 11, 2024
160 checks passed
@github-actions github-actions bot added this to the next release milestone Dec 11, 2024
sbylica-splunk pushed a commit to sbylica-splunk/opentelemetry-collector-contrib that referenced this pull request Dec 17, 2024
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

Creates a new receiver that accepts libhoney traffic as either logs or
traces.

This PR doesn't do the conversion yet. Just contains configurations and
some factory components.

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue

open-telemetry#36693
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