[mbell]

> 4. They helped a third party service to adapt their offering to better help their customers (NewRelic)

Unless I misunderstand the situation, NewRelic's heroku reporting isn't some one sided third party service but rather something that at least seems to be jointly produced by Heroku and NewRelic.

NewRelic can't report something that isn't offered up and it would seem to me that Heroku needs to deliberately expose metrics to the NewRelic plugin for it to be able to pick them up.

As it seems to be that these queue times weren't reported anywhere developer accessible it also stands to reason that they weren't exposed to NewRelic.

So no heroku didn't fix some third party service, they fixed their own service (in this regard).

[Sujan]

I'm not entirely sure if the headers the new version of the plugin uses were available before, but it sounded like they were. NR wasn't aware that the one they were using didn't report the queueing time before the dynos and Heroku now helped them to fix that.

So yeah, probably Heroku fixed their part and made sure NewRelic reflected that.