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
{{ message }}
This repository has been archived by the owner on Aug 4, 2023. It is now read-only.
💡 Join our Slack Community to ask general questions, suggest ideas and get direct help from all the folks at Checkly.
Is your feature request related to a problem? Please describe.
A domain was resolving to a cloud provider's service through 2 IPs, one of these IPs was not responding causing the checks to fail but the other IP did respond so overall we were seeing intermittent check failures but the service was healthy and up all the time.
Describe the solution you'd like
If the api check can log which IP it was calling when the domain was resolved, it would help us quickly identify that there is a bad IP
Describe alternatives you've considered
We did the DNS lookups to find the IPs and made requests ourselves to see this behaviour but that was only when we realised that this might be the cause
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
💡 Join our Slack Community to ask general questions, suggest ideas and get direct help from all the folks at Checkly.
Is your feature request related to a problem? Please describe.
A domain was resolving to a cloud provider's service through 2 IPs, one of these IPs was not responding causing the checks to fail but the other IP did respond so overall we were seeing intermittent check failures but the service was healthy and up all the time.
Describe the solution you'd like
If the api check can log which IP it was calling when the domain was resolved, it would help us quickly identify that there is a bad IP
Describe alternatives you've considered
We did the DNS lookups to find the IPs and made requests ourselves to see this behaviour but that was only when we realised that this might be the cause
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: