Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Select certain monitors? #14

Open
mattttt opened this issue Jun 8, 2016 · 3 comments
Open

Select certain monitors? #14

mattttt opened this issue Jun 8, 2016 · 3 comments

Comments

@mattttt
Copy link
Contributor

mattttt commented Jun 8, 2016

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

@mattttt
Copy link
Contributor Author

mattttt commented Jun 8, 2016

@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.

@mattttt
Copy link
Contributor Author

mattttt commented Jun 8, 2016

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.

@weyrick
Copy link

weyrick commented Jun 8, 2016

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants