As said earlier, if you have a lot of websites (200+) we can discuss some longer intervals for your account but otherwise this is unlikely to happen as it doesn't work with updown.io credit pricing and doesn't fit well the current UI. The 1h check interval is already cheap enough for most use-cases (and provides better monitoring).
The reason is that we use updown.io to test our website forms. And with 24 test submissions per day it clutters our database. And the admin screens show the test submissions mostly.
I see, thanks for providing the reason. Unfortunately that's more of a side-track usage so not a priority to optimise for. And filling production database with automated test is indeed not great anyway (be it every 1 or 12 hours) so you'd better find a way to remove those automatically or hide them on your end.
The maintenance window feature if implemented could help you with this (as you could say only one or two hour per day should be active monitoring for example). So you may want to vote for this one too.
6 Comments
Intervals above 1h may be available on demand depending on how many sites you are monitoring. Please ask support if you want.
I would like to have the choice of a 2h ,4h, 8h ,12h or 1 day interval. I would be glad, if you could add more options.
We would like a 12 hour interval too.
As said earlier, if you have a lot of websites (200+) we can discuss some longer intervals for your account but otherwise this is unlikely to happen as it doesn't work with updown.io credit pricing and doesn't fit well the current UI. The 1h check interval is already cheap enough for most use-cases (and provides better monitoring).
Thank you for the explanation.
We are not looking to save the credits.
The reason is that we use updown.io to test our website forms. And with 24 test submissions per day it clutters our database. And the admin screens show the test submissions mostly.
I see, thanks for providing the reason. Unfortunately that's more of a side-track usage so not a priority to optimise for. And filling production database with automated test is indeed not great anyway (be it every 1 or 12 hours) so you'd better find a way to remove those automatically or hide them on your end.
The maintenance window feature if implemented could help you with this (as you could say only one or two hour per day should be active monitoring for example). So you may want to vote for this one too.
Sign in to comment