Caleb Schoepp

If possible I'd like us to land on using `tracing`. Downstream in `containerd-shim-spin` I'm trying to integrate some observability work and it is failing b/c we're trying to globally initialize...

> That's totally fair, using just `tracing` crate would be more convenient and easier. However also I'd want to keep rust-extensions generic and unopinionated when possible. We don't want tracing...

What would the end goal of this be, supporting something like a `spin test` top level command?

> Users who want to interact with localhost will have to allow both *://localhost:* and *://127.0.0.1:* if they want either the IP address or the domain name to be used...

> - [ ] Merge pre-factor crates with their factor equivalents @lann I'm picking up this work for `factor-key-value`. A quick search in the codebase suggests this is also needed...

Not yet. #2353 is the issue tracking that work. Currently we aren't actively working on adding gRPC support, but it is definitely something we want to support. For anyone looking...

#3346 will complete this.

@ThorstenHans please try setting `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://localhost:4318/v1/traces` instead of `OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318`. This disables metrics which is the issue I believe.

Thanks @ThorstenHans. Turns out we don't even need aspire to repro this. The following app repros the issue: ```rust use spin_sdk::http::{IntoResponse, Request, Response}; use spin_sdk::http_component; use spin_sdk::key_value::Store; #[http_component] fn handle_api(req:...

Small update: This is not an issue on the old Go and JS SDKs. No clue why it isn't an issue there, but maybe this is a hint that can...