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: processor for external/remote processing #32664

Closed
2 tasks
aofodo opened this issue Apr 24, 2024 · 4 comments
Closed
2 tasks

New component: processor for external/remote processing #32664

aofodo opened this issue Apr 24, 2024 · 4 comments
Labels
closed as inactive needs triage New item requiring triage Sponsor Needed New component seeking sponsor Stale

Comments

@aofodo
Copy link

aofodo commented Apr 24, 2024

The purpose and use-cases of the new component

Sometimes need very flexible telemetry processing capabilities. For example, for greater security, it is necessary to analyze and mask some data from the logs using neural network processing or other various methods that are difficult to account for within standard collector components.

Example configuration for the component

remoteprocessor:
  protocol: http
  url: localhost:6060
  secure: true
  timeout: 10s

Telemetry data types supported

All types of telemetry

Is this a vendor-specific component?

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

Code Owner(s)

No response

Sponsor (optional)

No response

Additional context

Unlike processor/remotetapprocessor, for this component, the external application must return the processed telemetry, and then it will then go further along the pipeline

I drew a diagram of an example of interaction to make it easier to understand.
remoteproccc

@aofodo aofodo added needs triage New item requiring triage Sponsor Needed New component seeking sponsor labels Apr 24, 2024
@thiagogcm
Copy link

This would be very helpful.
some prior related discussion: open-telemetry/opentelemetry-collector#7961

I think the offload to an external processor instance could be inspired by the Envoy solution: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/ext_proc/v3/ext_proc.proto

@seankhliao
Copy link
Contributor

Why not just feed it the output of an exporter and have it feed back in a receiver?

Copy link
Contributor

github-actions bot commented Jul 3, 2024

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.

Copy link
Contributor

github-actions bot commented Sep 1, 2024

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed as inactive needs triage New item requiring triage Sponsor Needed New component seeking sponsor Stale
Projects
None yet
Development

No branches or pull requests

3 participants