Open mattttt opened 8 years ago
@woodsaj confirmed that out first test customer, Zenedge, was experiencing some issues because they have several hundred monitors - so I imagine this will also be an issue.
With that, we'll likely need to handle both in the same manner.
During testing, the check interval was 1m and the NS1 api was return 429 rate limit reached errors.
We've increased the check interval to 5m, and things seem to be smooth for several hundred monitors.
I think we can leave this as polling all for the time being, unless NS1 says otherwise.
Yes agreed we should handle monitors the same way.
For the other topic, not sure I understand. Is the question whether it should always poll all monitors regardless of their selection of them? A 5m interval is probably the longest that would give reasonable results. If they will be selecting which monitors, is there a reason not to limit polling just to those?
Shannon, can you please confirm whether we meed to put the same selection criteria in place for Monitors - or if this is not an issue.
Thanks! Matt