mirror of https://github.com/pulumi/pulumi.git
4ce02a7163
When tracing to a file, serve a Zipkin tracing endpoint from the CLI as well. This allows us to hand plugins an endpoint they can use to report traces during the execution of a Pulumi program. There is a little bit of accidental complexity here: - In order for trace data to flow across gRPC, we need to ensure that a trace that is injected into a gRPC request is injected as something the other side understands. In our case, this means we need to inject a Jaeger SpanContext as well as/instead of a native (AppDash) SpanContext. - In order to play nicely with the local tracer, we need to convert Zipkin spans into native spans. I couldn't find any pre-existing code to do this, so this is all our own. |
||
|---|---|---|
| .. | ||
| apitype | ||
| backend | ||
| codegen/python | ||
| diag | ||
| encoding | ||
| engine | ||
| graph | ||
| npm | ||
| operations | ||
| resource | ||
| secrets | ||
| testing | ||
| tokens | ||
| tools | ||
| util | ||
| version | ||
| workspace | ||