From ea54710d56ba71e346f3b1a27bab52c86b8b2d26 Mon Sep 17 00:00:00 2001 From: Luke Valenta Date: Wed, 2 Apr 2025 11:44:52 -0400 Subject: [PATCH] Add documentation for persisting Rust coredumps This was written about in the linked blog post. It seems like this should in theory work for Javascript workers, but I'm not sure (e.g., https://github.com/cloudflare/wasm-coredump/issues/5). --- src/content/docs/workers/observability/errors.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/docs/workers/observability/errors.mdx b/src/content/docs/workers/observability/errors.mdx index 670557de0c50b9..e9983627fd16b2 100644 --- a/src/content/docs/workers/observability/errors.mdx +++ b/src/content/docs/workers/observability/errors.mdx @@ -302,6 +302,10 @@ function postLog(data) { +## Collect and persist Wasm core dumps + +Configure the [Wasm Coredump Service](https://github.com/cloudflare/wasm-coredump) to collect coredumps from your Rust Workers applications and persist them to logs, Sentry, or R2 for analysis with [wasmgdb](https://github.com/xtuc/wasm-coredump/tree/main/bin/wasmgdb). Read the [blog post](https://blog.cloudflare.com/wasm-coredumps/) for more details. + ## Go to origin on error By using [`event.passThroughOnException`](/workers/runtime-apis/context/#passthroughonexception), a Workers application will forward requests to your origin if an exception is thrown during the Worker's execution. This allows you to add logging, tracking, or other features with Workers, without degrading your application's functionality.