scout_apm_ruby icon indicating copy to clipboard operation
scout_apm_ruby copied to clipboard

Heroku Timeouts Not Being Monitored in Scout APM

Open berniechiu opened this issue 1 year ago • 2 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

Screen Shot 2024-05-07 at 10 36 06 AM Screen Shot 2024-05-07 at 10 36 47 AM

berniechiu avatar May 07 '24 02:05 berniechiu

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.

lancetarn avatar May 07 '24 15:05 lancetarn

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.

berniechiu avatar May 08 '24 01:05 berniechiu