Trace files produced by pulumi --tracing do not show AWS provider calls

[t0yv0]

To reproduce:

1. checkout exampes/aws-go-s3-folder
2. pulumi up --tracing file:./up.trace
3. PULUMI_DEBUG_COMMANDS=1 pulumi view-trace "$1"

Expected:

Visibility into what the AWS provider is doing, in particular spans around the network calls it generates to talk to AWS.

Actual:

No spans coming from the AWS provider.

Discussion:

There might be two issues going on here, first we need to verify that --tracing flag is getting passed correctly to the AWS plugin; second, check that AWS provider has the appropriate span annotations against the opentracing API. This may be broken out into a separate issue.

Workaround:

There is some indirect visibility via spans coming from the engine such as /pulumirpc.ResourceProvider/Create. These are client-side spans produced by the gRPC client talking to the provider's gRPC server.

Affected feature

Performance visibility.

[t0yv0]

This got fixed in #9980 - note that it turns out the fix only affected using file: based AppDash tracing. When using a Jaeger server for tracing as described inhttps://www.pulumi.com/docs/support/troubleshooting/ the traces propagate perfectly already without the fix.

[pulumi-bot]

Cannot close issue without required labels: resolution/