-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
New component: Libhoney Receiver #36693
Labels
Accepted Component
New component has been sponsored
Vendor-Specific Component
New component that interfaces with a vendor API and will be maintained by the vendor.
Comments
mterhar
added
needs triage
New item requiring triage
Sponsor Needed
New component seeking sponsor
labels
Dec 5, 2024
I'll sponsor |
TylerHelmuth
added
Accepted Component
New component has been sponsored
Vendor-Specific Component
New component that interfaces with a vendor API and will be maintained by the vendor.
and removed
Sponsor Needed
New component seeking sponsor
needs triage
New item requiring triage
labels
Dec 6, 2024
TylerHelmuth
pushed a commit
that referenced
this issue
Dec 11, 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. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue #36693
sbylica-splunk
pushed a commit
to sbylica-splunk/opentelemetry-collector-contrib
that referenced
this issue
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
TylerHelmuth
pushed a commit
that referenced
this issue
Dec 19, 2024
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR is the implementation for the logs signal related to the new libhoney receiver. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue #36693
TylerHelmuth
pushed a commit
that referenced
this issue
Dec 20, 2024
This was referenced Dec 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Accepted Component
New component has been sponsored
Vendor-Specific Component
New component that interfaces with a vendor API and will be maintained by the vendor.
The purpose and use-cases of the new component
The Libhoney receiver will accept data for either Trace or Logs signals that are emitted from applications that were instrumented using Libhoney libraries.
The configuration has 2 parts, One is the HTTP receiver configuration and the rest is about mapping attributes from the freeform libhoney format into the more structured OpenTelemetry objects.
Example configuration for the component
Telemetry data types supported
It will subscribe to the Traces and Logs signals but accept traffic destined for either pipeline using one http receiver component. Libhoney does not differentiate between the two so the receiver will identify which pipeline to deliver the spans or log records to.
No support for metrics since they'd look just like logs.
Code Owner(s)
Tyler Helmuth, Mike Terhar
Sponsor (optional)
Tyler Helmuth
Additional context
No response
The text was updated successfully, but these errors were encountered: