Engineering
How a broken release name overloaded our symbolication database
An environment variable that was never expanded turned a single release into a 44-million-row database liability, sending symbolication CPU to 76%. Here's how we investigated and fixed it.
