Lann

We could certainly add it at a non-default log level but I personally prefer to keep default logging as actionable as possible.

> the spin.exe binary for Windows is not a statically linked binary, but depends on the vcruntime140.dll from VC++ 2015 from Microsoft. This library is not installed by default on...

On naming: I think it could be nice to choose a different convention for host components specifically where span names better reflect the guest's perspective. We could also (mostly) set...

OTEL conventions: I do think its worth _some_ effort to stick with these conventions as it will help with familiarity and integration with other tooling. That said, I think everyone...

> don't know how to square it with the OTEL conventions I would suggest preferring OTEL conventions where they are clear and come up with a nice convention that we...

> > We could also (mostly) set the otel.name, giving us more flexibility in naming without clashing with tracing span name conventions. > > I'm not sure what you're driving...

> Is it worth doing the work of manually emitting an event! on the inner result so that the span is marked as an error if the inner result contains...

> in your opinion @lann am I just getting to hung up here on consistency? Yep! :slightly_smiling_face:

> Ack. Part of me wants to just do it statically in the instrument though if we don't need to do it dynamically so that we don't have to clutter...

> it seems this was done to support the --allow-transient flag in spin up Not exactly. The files are copied to create the directory structure to be mounted into the...