Tim Nolet
Tim Nolet
I see the problem. I guess if everyone is fully aware that this is happening, there is not a big problem. Making your paths and urls fully qualified isn't always...
I use Objection since version 1.4 on https://checklyhq.com, a monitoring SaaS. I use it for the reasons mentioned above. Feel free to use the logo or screenshot.  
hey @kgapos we don't support this now in the UI. However, you could add a teardown script with an `expect` function that actually does this. Have a look here https://www.checklyhq.com/docs/api-checks/teardown-script-examples#perform-additional-assertions...
Hey @dacevedo12 , sorry for the late reply and thanks for the feedback! I like the idea! we just moved our public roadmap to https://feedback.checklyhq.com/ and are archiving this repo....
@KBA-H thanks for contributing. I hear you. Sounds like a fair addition!
@alexnoyes do I understand that the "avalanche" of alerts you receive is the main pain point here? I'm asking this because this is something we are aware of, and actually...
@alexnoyes thanks for explaining this. Another question. Do you use the Checkly groups feature? If you group checks for similar/the same endpoints, an option would be to do exclusive alerting...
@alexnoyes thanks. Reminds me of my Nagios days! 😅 I guess our mission is to make this still easy to reason about.
@randak thanks for responding to this. I think we need to look at this, but a bit different than @alexnoyes explained it. I think we are discussing the abstract concept...
@jonoc330 this is on our radar as we speak. We are looking at how to avoid this, or give you more actionable options to mitigate this.