Heroku Timeouts Not Being Monitored in Scout APM
berniechiu opened this issue · comments
Application
Rails: 7.0.8
Rack: 2.2.9
Scout: 5.3.5
Description
Hi Scout Team,
We're experiencing Heroku timeouts events occassionly, spotted on basic metrics on Heroku, but we've never seen those timeouts recorded in Scout. I think it's hard to investigate the root cause if Scout is not properly monitoring here.
Screenshots
This is true. We have not generalized the handling of these. Are you using rack-timeout by chance? That puts the signal back in a place where we can more easily deal with it and do cleanup in our instrumentation, close spans and send them before everything exits. We have some ideas around middleware for this situation. I'll see what we can share.
This is true. We have not generalized the handling of these. Are you using [rack-timeout]....(https://github.com/zombocom/rack-timeout) by chance?
Nope, not really since Heroku has a hard timeout 30s. So we don't have it installed, it is less beneficial under Heroku deployments at the moment.