aws-otel-collector
aws-otel-collector copied to clipboard
Support for the transform processor
Is your feature request related to a problem? Please describe.
I'm using fluentbit to forward the logs to the opentelemetry collector and I want to parse the json from the logs and then transform some of the fields to attributes using the transform procesor. However that processor doesn't seem to be supported by the AWS otel collector.
Describe the solution you'd like
I would like to have support for the transform processor to be able to do advanced transformations using the Opentelemetry Transformation Language.
Describe alternatives you've considered
Use the docker image from opentelemetry instead of using this one from AWS.
Additional context N/A
Thanks for creating this feature request, certainly something we consider @bmbferreira. Please do note that at the moment we do not support logs GA in ADOT (see https://github.com/aws-observability/aws-otel-community/issues/11 for details).
I would like to have transform processor for my trace processing - I would like to rename service.name
attribute if it is not in allowed set, e.g.:
transform:
error_mode: ignore
trace_statements:
- context: resource
statements:
- set(attributes["service.name"], "not-whitelisted-service") where isMatch(["service-a","service-b"], attributes["service.name"])
Thank you, @jangaraj
+1 to getting this processor added to ADOT. We are working with a customer for whom the lack of this processor is causing heartburn.
FWIW, I think this is a dupe of #1869. Very much hope it is picked up soon!
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
is there any update on this? it will be very very useful to have it.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
+1 for this processor, in the context of transforming histogram metrics for Dynatrace