When I am adding a new monitor e.g. for a website, there no option to test my checks whether it passes or fails before put into the production mode. To avoid false alerts, it will be good to have an option to validate the current status of a monitor before putting it in active condition. There is no point of adding a monitor if it fails immediately after adding. I rather correct the condition first and then add the monitor. Specifically this will be useful when I am checking rest endpoints or websites with certain conditions attached to it e.g. return some JSON, or a string etc etc. and I want to refine the return string I am checking over time.
Hello,
A down alert will not be generated when adding a new website monitor. Any failed checks should result in a "Configuration Error" state until the monitor is edited to a working state and is reported as up. However if you edit the monitor after it's first reported as up, any failures due to the new configuration will result in a down alert.
Regards,
Kurian
What I am asking is a test button to validate the configuration (whether during initial setup or subsequent changes) , it will be helpful.
What would be great too, is to add a more expanded reason for the configuration error. I have ran into cases in the past where all I got was a basic error and I had to almost re-invent the wheel with the investigations.
For example, when adding web monitors, all we get is Service Unavailable. It would be nice to get some additional context to what issues were encountered, maybe adding a traceroute image like you already do when a monitor goes down.
Thank you for the feedback. We'll evaluate the feasibility of adding such a feature.
Regards,
Kurian