envoyproxy/envoy

Exposing Wasm VM state in a health check endpoint

Open

#34.881 aberto em 25 de jun. de 2024

Ver no GitHub
 (3 comments) (2 reactions) (0 assignees)C++ (5.373 forks)batch import
area/wasmhelp wanted

Métricas do repositório

Stars
 (27.997 stars)
Métricas de merge de PR
 (Mesclagem média 8d) (378 fundiu PRs em 30d)

Description

Title: Exposing Wasm VM state in a health check endpoint

Description: Any unrecoverable error in the Wasm VM will panic it, and all coming requests will get 503. Users have to reload the wasm filter or restart the envoy process to eliminate the issue.

I didn't find any specific mechanism/API from Envoy documents that can help users identify the status of the Wasm VM. This is useful for building a liveness probe to have the envoy process restart without any human interaction.

Thank you!

Guia do colaborador