We log runtime errors in Slack using a webhook (have an #errors channel which receives a post with a stack trace and useful metadata), then notice patterns in e

We log runtime errors in Slack using a webhook (have an #errors channel which receives a post with a stack trace and useful metadata), then notice patterns in error generation manually, discuss the errors and why they might be happening in Slack, and eventually funnel urgent or important ones into our task management system. Right now, we don't have a ton of traffic so the errors channel receives a very manageable volume. I imagine this sort of approach would get overwhelming for a product with more concurrent users or more runtime-error-generating code paths.