public-roadmap icon indicating copy to clipboard operation
public-roadmap copied to clipboard

Assert rules by location

Open anish-blackbox opened this issue 3 years ago • 2 comments

💡 For general support requests and bug reports, please go to checklyhq.com/support

Is your feature request related to a problem? Please describe. API endpoint checks are performed from two locations as a minimum which means some metrics e.g response time will vary. Our use case calls for checking the latency of our API's from various locations in case there are underlying issues that has crept up. The acceptable response times can vary between locations.

Describe the solution you'd like Ability to specify which asserts apply to what location will allow more flexibility and can perhaps be used in the future for more location specific metrics

Describe alternatives you've considered None. An option could be that we set up two checks, one of reach location however, since a check uses two locations, there will always be a variance in the response times

Additional context None

anish-blackbox avatar Jan 10 '22 19:01 anish-blackbox

@anish-blackbox thanks for contributing. I understand the concern, but it would complicate Checkly quite a bit at this point. I do see the need for location specific checks and assertions. How Checkly now works is by assuming you want a somewhat stable response time across the globe. We will likely pick this up if/when we introduce more location specific options for checks

tnolet avatar Jan 25 '22 19:01 tnolet

Thanks for the feedback. For now, iam thinking of sending alerts to a middleware service which will filter out the events by location. If the location iam interested in in part of the alert then it will forward that onto our ticketing system

anish-blackbox avatar Feb 13 '22 06:02 anish-blackbox