Forum Discussion
forgot to say, in a loop that check for null token with sleep of 60s between requests.....1000 machines took about 24 mins....eurgh
Thanks for the pointer, didn't realize that "token" in the response was the indicator that there's more data if you do another GET request with the same token.
Yeah I hear ya, we have several thousand machines in the field, so the request rate limit is really tough to work around. What I'm trying to do is cache the data for a single report on all machines to avoid hitting the report generation endpoint too often, but ideally would just be able to create smaller reports more frequently based on host IDs. I guess maybe what we'll have to do is set up a queue instead and have it wait 60s between generating each report, hopefully people are alright with waiting a long time for their reports...