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

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

Heroku提供了an HTTP POST deploy hook,但是似乎对新Relic REST API的要求太严格了：它需要一个x-api-key标头,并且参数名称不匹配(see here for details).

我无法在任何地方找到有关此的任何信息.我想念什么吗？还有另一种方法吗？

谢谢.

解决方法:

这应该是自动发生的,但是自11月1日起,NewRelic部署跟踪与Heroku的集成已中断.

我有关于此问题的支持票,应该在下周左右的某个时间修复.

编辑(11/23/2013)：

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

编辑(2014年1月6日)：

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

标签：newrelic,heroku,python,django
来源： https://codeday.me/bug/20191030/1966098.html