Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Site down for X amount of time before alert is fired for site checks

feature-request
feature-idea
rfb

#1

Our devs are constantly deploying to our apps and we have noticed that every time a deploy happens when a check is executed we get a failed check. Obviously its just coincidence that the check is executed right when a deploy is happening and the site may only be down for 20 seconds but that’s enough time to fire an alert.

A nice feature would be to have the ability to set a time before an alert is fired. For example don’t fire an alert unless site is down for 30 seconds or 1 minute, etc…


New Relic Edit

  • I want this too
  • I have more info to share (reply below)
  • I have a solution for this

0 voters

We take feature ideas seriously and our product managers review every one when plotting their roadmaps. However, there is no guarantee this feature will be implemented. This post ensures the idea is put on the table and discussed though. So please vote and share your extra details with our team.


#2

Not sure if this helps you but you can setup browsers to ping your site to see if it is down, then change the interval in which you ping the site.

https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/using-monitors/add-edit-monitors


#3

Hey @xoibsurferx - Thanks for posting here on the community. Right now Synthetics alerts default to alerting on a failure. There is no way (using default Synthetics Alerts) to configure alerts on multiple failures, or failures running for a certain timeframe.

That said, you can use NRQL alerts to reach those goals. Check out this post to see how to do that:

I’ll still get a feature request submitted for you, and I’ll add a poll to your post for others to vote on this.


#4

If the application is deployed via a script or tool, then add a call to the Synthetics API to disable the synthetic at the start of the deployment. Another step to re-enable the synthetic once the deployment has been verified.