Yes, I would agree. As for the deferred tasks, I believe the Otel should create 'spans' when the task instances are actually 'running' during their deferred tasks were running - so even though the task id would be the same, we would have multiple 'spans' on the course of its lifetime.
On Fri, May 27, 2022 at 1:56 PM Chris Redekop <ch...@replicon.com.invalid> wrote: > On Sat, May 21, 2022 at 1:22 AM Malthe <mbo...@gmail.com> wrote: > >> But isn't the span uniquely identified by the task instance and attempt >> number? >> >> I would think that you've already got all the information without >> persisting any additional data. >> > > This doesn't seem quite right for deferred tasks, does it? Ideally each > "execution" would get its own span - for deferred tasks the same task > instance + try number will have execution spans on multiple workers (and > triggerers)....so for tracing purposes you would ideally want to be able to > trace each one of those executions independently, no? >
