Secure Error Handling: Stack Trace Leak vs. Sanitized Response

Requests stream through a client → gateway → service → database pipeline rendered in real 3D, and a fraction of them fail at the service node. This simulator lets you flip the error handler between two real-world contracts: a verbose one that returns the raw exception — stack trace, connection strings, query text — straight to the caller, and a sanitized one that returns a generic message plus a correlation ID while the real detail is written only to a centralized log store. Watch leaked-secret packets (red) fly all the way back to the client under the insecure mode, versus sanitized packets (green) paired with a log entry (yellow) under the secure mode, while live counters track requests handled, errors triggered, secrets leaked, correlation IDs logged, and the resulting exposure score.