NewRelic 总是说我的应用程序已关闭

发布于 2024-12-01 15:21:56 字数 466 浏览 0 评论 0原文

我在我的 Heroku 应用程序上安装了 NewRelic 插件,并且我正在尝试使用他们的“可用性”功能,但它总是说我的应用程序已关闭。另外,如果我尝试更改要 ping 的 URL,我总是会得到:

New Relic 已保存您的更改,但 http://skateparks.co/uptime 在 10 秒后超时。确保正确输入 URL,或编辑下面的 URL

在此处输入图像描述

如果我执行“ curl http://skateparks.co/uptime" 然后我会得到应用程序正常的响应。

在此处输入图像描述

I have the NewRelic addon installed on my Heroku application and I'm attempting to use their "Availability" feature but it aways says that my app is down. Also, if I try to change the URL that I want to ping I will always get:

New Relic saved your changes, but http://skateparks.co/uptime timed out after 10 seconds. Ensure that the URL was entered properly, or edit the URL below

enter image description here

If I do a "curl http://skateparks.co/uptime" Then I'll get a response that the application is fine.

enter image description here

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

你的心境我的脸 2024-12-08 15:21:56

编辑 URL 时收到的错误消息仅供参考。当您修改 URL 时,我们会同步 ping URL 来进行完整性检查,以帮助您确保输入正确。有时,我们无法在输入 URL 时对站点执行 ping 操作,即使我们显示警告消息,我们仍会保留您的设置并开始对 URL 执行 ping 操作。我们至少有一位客户报告说,他们在编辑 URL 时总是遇到错误,尽管 pinger 本身在获取更新的设置后从未表明 URL 存在任何问题。

如果您的 URL 收到停机警报,但您认为该错误不正确,那么故障排除的一个很好的起点是使用以下命令来卷曲您的目标,该命令完全模仿了我们的 Pinger 的操作。

curl -H --head "Accept: text/html" -H "Cache-Control: no-cache, max-age=0" -H "User-Agent: NewRelicPinger/1.0" -H "X-Newrelic-Ignore: true" http://www.newrelic.com

请注意,我们从 head 请求开始,如果您的服务器不支持它,则返回到 get 请求。要模拟 get 请求,只需使用上面的curl 命令,但删除--head。

The error message you get when you edit the URL is informative only. We do a sanity check by pinging the URL synchronously when you modify it to help you ensure that you entered it correctly. Sometimes we are unable to ping a site at the time the URL is entered, and even though we display the warning message, we still keep your settings and start pinging the URL. We had at least one customer report that they always got the error when editing their URL even though the pinger itself once it got the updated settings never indicated there was any problem with the URL.

If you get a downtime alert with your URL but you believe the error is incorrect, a good starting point for troubleshooting is to curl your target using the following command, which mimics exactly what our Pinger does.

curl -H --head "Accept: text/html" -H "Cache-Control: no-cache, max-age=0" -H "User-Agent: NewRelicPinger/1.0" -H "X-Newrelic-Ignore: true" http://www.newrelic.com

Note that we start with a head request, and if your server doesn't support it fall back to a get request. To mimic the get request just use the curl command above but remove --head.

顾冷 2024-12-08 15:21:56

我在 New Relic 工作,我在我们的支持网站上为您创建了一张票证,我们可以在其中进一步解决此问题。您应该很快就会收到一封电子邮件,其中包含该票证的链接,但如果您有任何其他问题,请随时直接联系我。

干杯,

I work at New Relic and I've created a ticket for you on our support site where we can troubleshoot this further. You should get an email soon with a link to that ticket, but feel free to ping me directly if you have any other questions.

cheers,
b

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文