衡量 Heroku 由于 Backlog 太深而拒绝多少请求的最佳方法是什么？
我正在 Heroku 上的竹子-mri-1.9.2 堆栈上运行 Rail 2.3。但是我遇到了一些缩放问题。在流量高峰时段，我看到一些错误 H11（积压太深），并且我可以通过 New Relic 监控看到我已退出高积压日志。然而，我现在想知道的不是队列的长度，而是被 Heroku 拒绝的传入请求的数量（这将导致 Heroku 日志中出现“错误 H11（Backlog 太深）”）。
简而言之，我想知道被拒绝的传入请求占传入请求总数的比率。
正如 Heroku 所说，日志文件主要用于调试目的，而不是用于分析真实的实时指标，有没有简单/免费的方法可以做到这一点？
谢谢！
PS 对这篇文章的评论How to keep log tail live on Heroku using ssh? 建议使用 papertrailapp.com 网站（显然与 papertrail gem 无关），但我无法确定它是否可以给我指示 H11 backlog 太深错误的比率。
I am running Rail 2.3 on bamboo-mri-1.9.2 stack on Heroku. However I am encountering some scaling issue. During peak hours of my traffic, I am seeing some Error H11 (Backlog too deep) and I can see that via New Relic monitoring that I am having quit a high back log. However, what I would like to know now, is not the length of the queue, but the number of incoming request that are rejected by Heroku (which would result in "Error H11 (Backlog too deep)" in the Heroku log).
In short, I would like to know the ratio of incoming requests being reject to the total number of incoming requests.
As Heroku said, the log file is mainly used for debugging purpose but not for analysing real live metric, is there easy/free way to do that?
Thanks!
P.S. Comment on this post How to keep log tail alive on Heroku using ssh? suggested using the papertrailapp.com website (not related to the papertrail gem apparently), but I couldn't determine whether it can give me indication of the ratio of H11 backlog too deep error.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
据我所知，无法查看拒绝的数量，因为它们早在您在应用程序附近看到请求之前就被路由网格拒绝了。
更重要的是，为什么您不扩展测功机来处理流量，也不因错误而拒绝用户？
There is no way to see the number of rejections as far as I am aware as they are turned away by the routing mesh - long before you see the request near your app.
More importantly, why are you not scaling the dynos to handle the traffic and not be turning away users with errors?