You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to make the URL tests more helpful for ensuring a service is online, it could optionally check for the presence of a string that if the URL works, but the string is not found, it will still consider the test as failed. It could perhaps be a different status to differentiate between the URL not loading, and the string not having been found.
Another tool we use has something similar, and I have attached a screenshot. This is a tool called Pingdom which regularly checks websites, and one of the optional features is to check for a string when it looks at the response from the page.
The text was updated successfully, but these errors were encountered:
It's done on my fork. Pending a pull request but not sure how to handle this with my previous pull request. Should I branch from my branch or start from master?
Awesome! Ideally, start from master, but if you want to branch from your roles branch that works as well but I won't be able to merge it until the other branch is, then I imagine there will be merge conflicts
In order to make the URL tests more helpful for ensuring a service is online, it could optionally check for the presence of a string that if the URL works, but the string is not found, it will still consider the test as failed. It could perhaps be a different status to differentiate between the URL not loading, and the string not having been found.
Another tool we use has something similar, and I have attached a screenshot. This is a tool called Pingdom which regularly checks websites, and one of the optional features is to check for a string when it looks at the response from the page.
The text was updated successfully, but these errors were encountered: