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

New component: Generic Webhook Receiver #18101

Closed
2 tasks
shalper2 opened this issue Jan 30, 2023 · 4 comments
Closed
2 tasks

New component: Generic Webhook Receiver #18101

shalper2 opened this issue Jan 30, 2023 · 4 comments
Assignees
Labels
Accepted Component New component has been sponsored Stale

Comments

@shalper2
Copy link
Contributor

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

receivers:
  genericwebhook:
    tls:
      certfile: '/path/to/cert'
      keyfile: '/path/to/key'
    endpoint: 'webhook/endpoint'

Telemetry data types supported

logs

Is this a vendor-specific component?

  • This is a vendor-specific component
  • If this is a vendor-specific component, I am proposing to contribute this as a representative of the vendor.

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.

@shalper2 shalper2 added the needs triage New item requiring triage label Jan 30, 2023
@jpkrohling
Copy link
Member

This would likely also help with #18098.

@jpkrohling jpkrohling added Sponsor Needed New component seeking sponsor and removed needs triage New item requiring triage labels Jan 30, 2023
@atoulme atoulme added Accepted Component New component has been sponsored and removed Sponsor Needed New component seeking sponsor labels Feb 16, 2023
@atoulme
Copy link
Contributor

atoulme commented Feb 16, 2023

Happy to sponsor this effort.

@github-actions
Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@shalper2
Copy link
Contributor Author

I believe this pr closes out this issue. Component has been merged as the webhook event receiver

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 Stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants