[FEATURE] OTEL over NATS

[hwinkel]

OTEL Traces and Metrics over NATS

Can the NATS Connectivity used to encapsulate the transport of the OTEL trace and later metrics data?
It would be good to use the NATS lattice to forward the telemetry data regardless of the topology and
not rely on 1:1 HTTP connections.

[thomastaylor312]

Hi @hwinkel! So for many of the things inside of the wasmcloud host we use this crate to put the otel data in the NATS headers. However, we were planning on removing it from everything except for the NATS provider as we use a field in our Invocation type to send the trace data. Can you give me a little more info on your use case? If there are some good reasons why we shouldn't remove it, it would be great to know!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!

[thomastaylor312]

So we will likely be adding support back for otel NATS headers via our forthcoming wRPC work in #1128

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!

[thomastaylor312]

@brooksmtownsend We can mark this as closed now, right?

[brooksmtownsend]

Yes! We did this, logging support is in v0.82 and metrics supports comes with 1.0 😄