OTel instrumentation

[mconflitti-pbc]

Description

As we begin to add otel instrumentation to Connect, we have found that it is helpful/useful to pass the traceparent context into apps/rendered content that is spun up so the app can continue logging spans within the same trace context. This is great to be able to inspect/troubleshoot long running processes to determine what is taking the most time to complete all in one place.

The idea would be to add otel instrumentation into quarto renders such that each execution block of code could be a span that is appended to the traceparent or create its own trace.

This is technically possible today just by manually instrumenting within the qmd file, but it would be great to have that OOTB for people using quarto for long running jobs on Connect.

[cderv]

We haven't yet discussed and considered OTEL instrumentation of Quarto but work has been happening at some engine level already as part of R packages work with otel.

For example, it just has been added into knitr dev version:

• http://github.com/yihui/knitr/pull/2422

each execution block of code

This means for document using engine: knitr, you should have some informations already when using this version of knitr.

It would be interesting to discuss what more would be useful to connect. Please feel free to reach out on Slack for further discussions.