azure - 如何在 NewRelic 中监视 Azure 辅助角色？

Question

我提出了一张票，但一周内没有回复。

有人设法让它工作吗？

Answer 1

New Relic 代理在 worker 角色方面没有太多作用。它可以监控一些东西——CPU、内存、错误、sql、外部接口(interface)——但除此之外就没什么了。肯定不起作用的一件事是代理 api — 因此没有自定义指标或通知错误。

我也遇到了类似的问题，试图从支持中获得答案，但他们最终确认了他们缺乏支持。以下是他们的一些回答。

Azure support by the agent

We believe we have a compelling Azure solution, but it doesn't cover all cases. There is certainly still work to be done and it's on our roadmap. We consider the .NET Agent to be a first class citizen and better support for Azure is a top priority. We are also planning to update the API to provide better support for non web-apps.

Specifically in your case:

While it is possible to instrument worker roles and get valuable data from the instrumentation, the data will not appear in most of our graphs. The reason is that most of the graphs depend on work being done as part of web or database transactions. This is often not the case for the work being done in worker roles. We apologize that our initial doc update updated our docs around instrumenting custom applications (non web-apps): https://newrelic.com/docs/dotnet/instrumenting-custom-applications

rather than the doc that you referenced:

https://newrelic.com/docs/dotnet/AgentApi

...we've now updated this. If you have a moment, we'd love your feedback. I feel this is finally well-documented but would like you to feel the same thing.

以及之前的回复

I looked into your API usage and while you are using the API correctly, the unfortunate reality is that our .NET agent does not actually support our full agent API from many .NET apps that are not webapps, and yours appear to fall into that category. How can I tell? Because your apps have no metrics--response time, database, etc. All you'll likely see are throughput and error rate (which I believe you are seeing). We use our own agent API to report the rest of the metrics, and so they don't show up. Further we record stuff like response time explicitly based on a web entry point right now but we are working to fix this. Unfortuantely this fix is pretty far out--I can't even promise an ETA. While researching what was going on, we found that our own docs fail to call out this known issue

此外，Azure 门户(支持和计费)和 New Relic 之间的集成非常糟糕，因此我建议通过他们自己的网站而不是 Azure 市场订阅 New Relic。

我主要是 New Relic 的粉丝，并认为总体而言它比其他替代方案更好，但它们缺乏辅助角色支持可能会成为 Azure 应用程序的一大障碍。我会密切关注这一点，如果情况发生变化，我会更新这个答案。