Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heroku Timeouts Not Being Monitored in Scout APM #499

Open
berniechiu opened this issue May 7, 2024 · 2 comments
Open

Heroku Timeouts Not Being Monitored in Scout APM #499

berniechiu opened this issue May 7, 2024 · 2 comments

Comments

@berniechiu
Copy link

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

@lancetarn
Copy link
Contributor

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.

@berniechiu
Copy link
Author

berniechiu commented May 8, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants