Skip to main content

the plugin is using the Rubrik API, but if you query for a single backup job it could take minutes to complete in a bigger environment with a lot of backup jobs. if you are using curl and the API with a query object that is using a job name, the query finish within 1-2 seconds.

 

curl -H "content-type:application/json" -H "authorization: Bearer xxxxxxxxx" -H "accept:application/json" 'https://xxxxxx.xxxx.com/api/v1/job_monitoring?limit=500&object_name=my-backup-job-name' | jq

 

looks like the plugin is receiving the whole jobs list and than doing a selection, this could be optimized by building the query URL like in the curl command, so you receive very fast the result and have not to wait minutes (timeout of the check and the centengine default timeout is too low)

New→Discussion ongoing

Hello :)

Could you tell us if you used the cache feature to limit API calls and thus reduce the impact of the issue you are raising?

Kind regards.

yes i use the cache feature, but i take minutes for this request to get ALL informations from the rubrik API. if you only ask the API for “one” jobs , you get back this information in 1-2 sec.

and running with the cache feature you have always “old” data that you use from the cache

we run the cache only once per hour, to not create to much load on the rubrik API, if you request to many data from the API then it stops answering for a period of time, this could not be ajusted on rubrik API side !.  making small request to get only the information for on job would reduce the load on rubrik and will be much faster, and you have not to do the filtering of “all “ the data received on the poller (even reduce the poller load)

Terms & ConditionsCookie settingsAccessibility statement