feat: Opentelemetry Setup

[lxfontes]

Sets up OTEL for logs / traces ( no metrics yet ).

OTEL configuration is driven by SDK environment variables.

We are tracking:

• Scheduling: Workload start / status / stop
• Wasm Entrypoints: http server and wasmcloud messaging
• Plugins lifecycle: bind / unbind operations

For Plugin Authors: Any HostApi interaction is observed by the runtime, so no need to instrument those unless you're enriching context.

An example setup would look like:

Start Aspire Dashboard ( Otel receiver ) with

docker run --rm -it \
    -p 18888:18888 -p 5318:18889 \
    --name aspire-dashboard \
    -e DOTNET_DASHBOARD_UNSECURED_ALLOW_ANONYMOUS="true" \
    -e ASPIRE_ALLOW_UNSECURED_TRANSPORT=true \
    mcr.microsoft.com/dotnet/aspire-dashboard:9.1

Configure Otel:

export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:5318
export OTEL_EXPORTER_OTLP_PROTOCOL=grpc

Start wash:

cargo run --  -C ./examples/blobby dev

You should be able to see:

• Aspire on http://localhost:18888/
• Blobby on http://localhost:8000/

[if0ne]

I've been waiting for this. Could you add support for passing metadata map values from cli/env? https://docs.rs/tonic/latest/tonic/metadata/struct.MetadataMap.html

I want to use OpenObserve for observability, and it requires basic authentication headers.

[lxfontes]

@if0ne metadata as in http headers or host/workload attributes?

for headers: the current code will respect https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/#otel_exporter_otlp_headers so basic auth is `export OTEL_EXPORTER_OTLP_HEADERS="Authorization: Bearer xxxx"

for metadata, was thinking of surfacing all or a subset of workloads' annotations as they can be enriched at many layers ( kube crd, operator itself, host ).

[if0ne]

@if0ne metadata as in http headers or host/workload attributes?

for headers: the current code will respect https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/#otel_exporter_otlp_headers so basic auth is `export OTEL_EXPORTER_OTLP_HEADERS="Authorization: Bearer xxxx"

for metadata, was thinking of surfacing all or a subset of workloads' annotations as they can be enriched at many layers ( kube crd, operator itself, host ).

As http headers. Thanks, I didn’t notice this env.