-
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: Generic Webhook Receiver #18101
Comments
This would likely also help with #18098. |
Happy to sponsor this effort. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
I believe this pr closes out this issue. Component has been merged as the webhook event receiver |
The purpose and use-cases of the new component
Create a receiver which can take generic push based data. This would expose similar functionality as the SplunkHEC receiver when configured to receive raw inputs but would not support vendor specific data formats and would simplify the ingestion of webhook data.
This would allow people to leverage otel's pipelines, processors, and exporters to broaden the applications that webhook data can be applied to. Additionally it could allow a user to take a single webhook input and fan it out to multiple upstream consumers.
Example configuration for the component
Telemetry data types supported
logs
Is this a vendor-specific component?
Sponsor (optional)
No response
Additional context
The idea here is really to separate the general use case of ingesting push based data from the vendor specific implementation that is the SplunkHEC receiver. This will hopefully reduce confusion and allow for quicker adoption when this use case arises for a user who is not experienced with or is not using Splunk HEC.
The text was updated successfully, but these errors were encountered: