Yes I get a partial poll of about 15,000 devices then it fails. The partial poll is generally about 2am EST and then it will fail for a few hours and get partial success again and fail for a few hours. I have a ticket open with MaaS360 I can share the case owners name if you can help any. They suggested I do the below back on June 1st but I am not sure ClearPass can do 2-4. I did adjust the poll timer already. Also put in a feature request for 2-3 and for 1 because 1 is a global timer and applies to all content servers in clearpass. I asked for individual settings.
Here is what dev suggested and like I said I really haven't done anything with this info cause I don't know how to use the info.
"1. Reduction in frequency to 4 hours should be tried - will help to some extent but may not completely solve the problem.
2. Avoid computerNetworkInformation call per device - most of the information information is available in the search call itself. Can evaluate search v2 also.
3. Use separate search API pulls for Android, iOS and Blackberry devices (separate search api calls per platform - pass platformName parameters : platformName=Android or platformName=iOS or platformName = Blackberry for the pulls)
4. Respect the rate limits headers provided by X-Rate-Limit-Remaining, X-Rate-Limit-ResetWindow and X-Rate-Limit-Max response headers and throttle the API calls."
Danny were you the guy speaking at atmosphere about APIs this past conference?