Hacker News Reader

I was wondering that too. Why wouldn’t the error be in the logs?

Guess: the logs were on an ec2 instance that was thrown away regularly, and the overnight reports didn't give reproduce steps or timestamps; so when they checked it "works fine".

There's value in having your backtrace surfaced to end users rather than swallowing an exception and displaying "didn't work".

it was on some temporary AWS service like lambda or something? (We had eight ECS tasks on AWS, all running five instances of our backend), but, regardless logs should be somewhere persistent.

If they weren't, that should be the first thing you fix.

I don't think showing stack traces to users is good practice? Every time one of my users gets a didn't work message I log the stack trace instead.

Why would you show them a stack trace? This should be logged.

That's what I said. Parent said

> There's value in having your backtrace surfaced to end users

Reply on news.ycombinator.com