Filtering requests from WebGazer

Use cases

Rate limiting

If you have some rate limiting on your servers, you might accidentally block requests from WebGazer and cause it to generate false positives.

Let's say you have 10 gazers and the same server serves all of the endpoints. Requests from WebGazer for all these gazers might hit the server in the very same second and get throttled, resulting in an untrue incident notification.

Access filtering

The URL you want to monitor might be semi-public behind a firewall and accessible only to specific IP ranges. In cases like this, you can enable WebGazer access and check the service by whitelisting the WebGazer's IP addresses.

IP addresses

We publish the list of IP addresses that a WebGazer request can originate from. You can configure your throttling software or firewall to disable throttling or give access to these IP addresses.

You can access the list of these IP addresses here: https://api.webgazer.io/ip_addresses.txt

This list is generated automatically and gets updated occasionally when we update our infrastructure.

Table of Contents

Use casesIP addresses