Hello support,

Observed situation

The current hpe_synergy_http template does not address the problem of pagination for the data returned by Oneview API as described in "count" parameter here:

https://support.hpe.com/docs/display/public/dp00003271en_us/index.html#stdparams

If the data is "more" than expected, the returned data to Zabbix will be truncated to the default limit of the API.

Result:

It translate for instance as such in the data returned by "Get data" (and dependent items):

```

        "start": 0,
        "count": 32,
        "total": 51,
        "prevPageUri": null,
        "nextPageUri": "/rest/<method>?start=32&count=32"

```

You can see here that the data length is 51 but the template will only return 32 due to the default pagination count.

Expected:

Template should either go to "quick win", document a "count" macro explaining that this is a hard limit that users can try to override, or go toward a better implementation with a fetch and merge data loop.

Using the current logic of the template script, it's a bit hard => it implies to merge each page data received and return the final data, need to add a check of return code at each page + ensure it's below timeout.

I would suggest to loop as long you have a "nextPageUri" != null in data and merge the "members" results as it's there that the API data are stored.