7 ms·

Better Queuing Metrics With Updated New Relic Add-On

55 points by jsomers 14y ago

deleted 14y ago
[deleted]
- Whitespace 14y ago
  You should know: - http://news.ycombinator.com/item?id=5226117 http://news.ycombinator.com/item?id=5226117 - http://news.ycombinator.com/item?id=5230585 http://news.ycombinator.com/item?id=5230585 1700+ karma in 16 days and you complain? Come on now.
  - deleted 14y ago
    [deleted]
- dkroy 14y ago
  Yeah, that isn't right this one should be deleted.
yuvadam 14y ago
Unrelated: the kerning on the Heroku blog titles is horrible.
- whalesalad 14y ago
  Absolutely. I tweeted them a few hours ago. It's bothered me forever!
  - liampmccabe 14y ago
    It's actually the tracking (letter-spacing: 1px), a slight difference. http://www.mmprint.com/blog/2011/typography-kerning-leading-tracking/ http://www.mmprint.com/blog/2011/typography-kerning-leading-...
dantiberian 14y ago
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.
- mikeryan 14y ago
  I'm really impressed with the way Heroku has been communicating with their customers and the quick action they have been taking. 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.
  - dantiberian 14y ago
    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.
mparlane 14y ago
Are they going to update their routing? Or just make sure their customers know it's doing it the naive random way.
- omfg 14y ago
  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.
beambot 14y ago
"Today our partner, New Relic, released an update to the Ruby New Relic agent" Does this also apply to other non-Ruby frameworks (eg. Django)?
- thomaslee 14y ago
  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).
- friism 14y ago
  New Relic has a fixed Python agent out: https://newrelic.com/docs/releases/python https://newrelic.com/docs/releases/python
simpletouch 14y ago
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.
- friism 14y ago
  On Bamboo, you can still specify newrelic_rpm at a particular version in your Gemfile. The agent is only injected if Heroku detected that you haven't added the agent yourself: https://devcenter.heroku.com/articles/newrelic#bamboo-configuration https://devcenter.heroku.com/articles/newrelic#bamboo-config...

55 points by jsomers 14y ago

deleted 14y ago

[deleted]

Whitespace 14y ago
You should know: - http://news.ycombinator.com/item?id=5226117 http://news.ycombinator.com/item?id=5226117 - http://news.ycombinator.com/item?id=5230585 http://news.ycombinator.com/item?id=5230585 1700+ karma in 16 days and you complain? Come on now.
- deleted 14y ago
  [deleted]
dkroy 14y ago
Yeah, that isn't right this one should be deleted.

yuvadam 14y ago

Unrelated: the kerning on the Heroku blog titles is horrible.

whalesalad 14y ago
Absolutely. I tweeted them a few hours ago. It's bothered me forever!
- liampmccabe 14y ago
  It's actually the tracking (letter-spacing: 1px), a slight difference. http://www.mmprint.com/blog/2011/typography-kerning-leading-tracking/ http://www.mmprint.com/blog/2011/typography-kerning-leading-...

dantiberian 14y ago

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.

mikeryan 14y ago
I'm really impressed with the way Heroku has been communicating with their customers and the quick action they have been taking. 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.
- dantiberian 14y ago
  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.

mparlane 14y ago

Are they going to update their routing? Or just make sure their customers know it's doing it the naive random way.

omfg 14y ago
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.

beambot 14y ago

"Today our partner, New Relic, released an update to the Ruby New Relic agent" Does this also apply to other non-Ruby frameworks (eg. Django)?

thomaslee 14y ago
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).
friism 14y ago
New Relic has a fixed Python agent out: https://newrelic.com/docs/releases/python https://newrelic.com/docs/releases/python

simpletouch 14y ago

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.

friism 14y ago
On Bamboo, you can still specify newrelic_rpm at a particular version in your Gemfile. The agent is only injected if Heroku detected that you haven't added the agent yourself: https://devcenter.heroku.com/articles/newrelic#bamboo-configuration https://devcenter.heroku.com/articles/newrelic#bamboo-config...