Tyler Helmuth
Tyler Helmuth
@djaglowski is correct. When using the logs context in the transformprocessor it will cycles through each log, executing each statement in order. When you use a value from a log...
If all the spans in the resource don't have the same `upstream_cluster.name` and `_k8s_namespace` you'll experience the behavior from this issue. We are open to better documentation around this behavior...
> I think there is a contradiction here. The design cannot consider modifications to a resource or scope to be "only within the TransformContext" of a log record when we...
The `flatten_data` config option and associated feature gate have been in place for a while now and I've seen it solve end-user problems on multiple occasions. I would be ok...
> Maybe there's a general rule that it is possible to flatten down to any context? Ya this is what I had in mind. Given `flatten_data` is enabled, the data...
@djaglowski I think there has been enough requests for these features that I am open to more fine-grained control via functions. We also have the proper testing framework in place...
I still like the solution that implemented it in consumer so it automatically happened everywhere: https://github.com/open-telemetry/opentelemetry-collector/pull/8833
@jvoravong would this make it so that contributors wouldnt need to run `make generate-examples` themselves? That would be wonderful
I don't think so, as that commit didn't do anything with example generation.