I'm really impressed with the way Heroku has been communicating with their customers and the quick action they have been taking. It goes a long way to restore my faith in their long term plans to make this better.
You're absolutely right about not addressing it for years part but I think that the way they are responding to it now indicates that they take it seriously and are wanting to make it right.
It sounds as though they are keeping the routing but giving users more info about it so they can make better decisions when designing their apps for the platform.
I'm an engineer at New Relic. A fix for the Python agent will follow within the next day or two.
Asking around, it sounds like only the Python & Ruby agents are affected by the queue time reporting issue (with the exception of Java, which apparently doesn't report the queue time at all -- but I believe this is a known limitation).
Any word on the status of the gem on the Bamboo stack? We have deployed a couple time today, but our NewRelic gem version is still 3.5.3 and being on Bamboo, have no control over which version is used.
17 comments
[ 3.5 ms ] story [ 50.3 ms ] thread- http://news.ycombinator.com/item?id=5226117 - http://news.ycombinator.com/item?id=5230585
1700+ karma in 16 days and you complain? Come on now.
By "communicating with customers" and "quick action" You mean how they hid it for years?
I'm all for quick responses to sudden issues, but this is a bandaid for something they didn't address until getting called out publicly.
Does this also apply to other non-Ruby frameworks (eg. Django)?
Asking around, it sounds like only the Python & Ruby agents are affected by the queue time reporting issue (with the exception of Java, which apparently doesn't report the queue time at all -- but I believe this is a known limitation).