-
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: processor for external/remote processing #32664
Comments
This would be very helpful. 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 |
Why not just feed it the output of an exporter and have it feed back in a receiver? |
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 |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
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
Telemetry data types supported
All types of telemetry
Is this a vendor-specific component?
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 pipelineI drew a diagram of an example of interaction to make it easier to understand.
The text was updated successfully, but these errors were encountered: