Why do my WebAssembly modules go dark the moment they enter production?
机会
WASM is now a real deployment target at the edge, in serverless, and in plugin sandboxes. Container workloads have had OpenTelemetry, Prometheus, and structured logging for years; WASM workloads running under WASIp3 hosts do not emit guest-level spans by default and require deliberate instrumentation wiring that most frameworks omit. Stack traces in production failures reduce to binary addresses because DWARF debug info is stripped at build time and source maps do not survive most deployment pipelines. Operators cannot set up the same alerting and dashboards they use for containers because there is no standard way to get telemetry out of a running WASM module without modifying the guest code itself.
为什么重要
Without native production observability, WASM cannot displace containers in any workload where on-call engineers need to diagnose a live incident.
我如何评估机会
机会评分是我的个人判断，而非量化指标：痛苦程度、发生频率，以及当前解决方案的匮乏程度。分数越高，意味着我认为越值得去构建。
出现时造成的痛苦程度。
人们实际遇到它的频率。
当前针对它的优质工具有多匮乏。