[processor/transform] Instrument the transform processor to emit traces

evan-bradley commented 5 months ago

Component(s)

processor/transform

Is your feature request related to a problem? Please describe.

When working with complex data and/or a complex sequence of statements, it can be difficult to debug the transform processor to determine why data doesn't look like it should when coming out. The Collector has an OTel SDK that supports tracing, so we should take advantage of it.

Describe the solution you'd like

Instrument the transform processor so it emits traces. We should have traces for each statement that records whether the statement ran, and if it ran, what the invocation was.

We should ensure that the logs emitted from https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33274 are associated with the traces so we can associate payloads with executions.

Describe alternatives you've considered

No response

Additional context

Some of this functionality may need to be implemented directly in OTTL.

github-actions[bot] commented 5 months ago

Pinging code owners for processor/transform: @TylerHelmuth @kentquirk @bogdandrutu @evan-bradley. See Adding Labels via Comments if you do not have permissions to add labels yourself.

bacherfl commented 5 months ago

@evan-bradley I would like to pick to pick this one up :)

github-actions[bot] commented 3 months ago

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.

Pinging code owners:

processor/transform: @TylerHelmuth @kentquirk @bogdandrutu @evan-bradley

See Adding Labels via Comments if you do not have permissions to add labels yourself.

TylerHelmuth commented 3 months ago

Closed by https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33508

TylerHelmuth commented 2 months ago

Adding tracing caused performance issues, we need to look into why.

github-actions[bot] commented 2 months ago

Pinging code owners for pkg/ottl: @TylerHelmuth @kentquirk @bogdandrutu @evan-bradley. See Adding Labels via Comments if you do not have permissions to add labels yourself.

github-actions[bot] commented 2 weeks ago

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.

Pinging code owners:

processor/transform: @TylerHelmuth @kentquirk @bogdandrutu @evan-bradley
pkg/ottl: @TylerHelmuth @kentquirk @bogdandrutu @evan-bradley

See Adding Labels via Comments if you do not have permissions to add labels yourself.

open-telemetry / opentelemetry-collector-contrib