Envoy Proxy Crash: Assertion Failure

Detects critical Envoy proxy crashes caused by assertion failures (e.g., invalid configurations, filter initialization errors, or runtime invariant violations). Assertion failures in Envoy typically include log entries containing critical][assert] followed by critical][backtrace] and ultimately lead to process termination. This high-severity failure often requires immediate intervention to restore traffic flow.

This rule helps identify problems such as:

• Misconfigured listener or filter definitions that trigger internal assertions
• Runtime invariant violations leading to aborts and backtraces
• Filter or extension bugs causing Envoy to crash during startup or runtime
• Cascading outages in edge or sidecar deployments due to sudden Envoy termination
• Repeated crash loops that block traffic until manual restart or configuration fix

✅ Use Case:

This CRE rule is perfect for:

• SREs and platform teams overseeing Envoy sidecars or gateways
• Service mesh operators detecting proxy crashes in CI/CD or production
• Incident responders who need automated detection of assertion failures before outages spread

Reproducible test setup (Maintainers invited): envoy-proxy-crash
Live CRE Link: CRE playground

/claim #97
/close #97