python - 如何在 Heroku 上使用 New Relic 记录部署

Question

我在 Django/Python Heroku 应用程序上使用 New Relic 插件，我想记录部署，但我不知道该怎么做。

Heroku 提供 an HTTP POST deploy hook ，但它似乎过于严格，无法满足 New Relic REST API 的要求:它需要一个 x-api-key header 并且参数名称不匹配(see here for details)。

我在任何地方都找不到有关此的任何信息。我错过了什么吗？还有其他方法吗？

谢谢。

Answer 1

这应该会自动发生，但 NewRelic 部署跟踪与 Heroku 的集成自大约 11 月 1 日起就已中断。

我有一个关于这个问题的支持票，它应该会在下周左右的某个时间得到解决。

编辑(2013 年 11 月 23 日):

Heroku 承认这是由 NewRelic 插件的大修引起的错误。以下是他们在我的支持票上所说的根本原因:

I've got an update on this, but no resolution yet. To give you some context (given you've asked how this has happened 3 times) New Relic were the very first add-on in the Marketplace and as a result there has been a lot of gnarly code very specific to their implementation. On their side they've also had to . And as you've gathered unfortunately much of it was not well tested. We've been working with New Relic all year to finally fix that, and we've moved them across to the standard API that all other add-ons and most PaaS providers now adhere to. Any new customers since May have been on that new integration so we've been testing it out for 6 months. The final part of that process was to remove customers on the legacy integration and that occurred as part of the migration onto the new pricing we announced at the start of this month.

It's only after this migration we realized there was no support for deploy notifications. New customers since may had never been exposed to the feature so didn't notice it was missing, and it appears none of the legacy customers we tested with in October noticed it was missing either. To rectify the situation we've had to try and build this feature out in the Add-ons API. That's been documented and deployed, and we're now working with New Relic to help their engineers implement it as soon as they possibly can.

我认为您无法查看我的支持票，但如果您提交自己的票，欢迎您使用 Heroku 引用它:

https://help.heroku.com/tickets/102722

编辑(01/06/2014):

NewRelic/Heroku 似乎已经修复了它们的集成，因此现在可以成功跟踪部署。这似乎已在 2014 年 1 月 2 日/之前的某个时间生效。