Request: Add Cursor Pagination Support for NetBrain APIs
Current Implementation
The NetBrain integration currently uses offset pagination via the beginIndex parameter across multiple API endpoints.
Issue Description
While researching cursor-based pagination (using afterId), we discovered:
- No official documentation exists for
afterId or cursor pagination support in NetBrain's API docs
- However, API error responses explicitly suggest using
AfterID for pagination, indicating the feature may be available
- The current data response/extract does not include entity IDs, which are required to implement cursor-based pagination
APIs Affected
Querying this issue for the following NetBrain API endpoints::
/CMDB/Topology/OneIPTable
/CMDB/Devices
/CMDB/Interfaces/Attributes
/CMDB/Topology/Devices/Neighbors
Request
Is there any support around:
- Whether cursor pagination using
afterId/AfterID is officially supported?
- How to retrieve entity IDs in API responses to enable cursor-based pagination?
- Best practices for implementing cursor pagination across these endpoints?
Request: Add Cursor Pagination Support for NetBrain APIs
Current Implementation
The NetBrain integration currently uses offset pagination via the
beginIndexparameter across multiple API endpoints.Issue Description
While researching cursor-based pagination (using
afterId), we discovered:afterIdor cursor pagination support in NetBrain's API docsAfterIDfor pagination, indicating the feature may be availableAPIs Affected
Querying this issue for the following NetBrain API endpoints::
/CMDB/Topology/OneIPTable/CMDB/Devices/CMDB/Interfaces/Attributes/CMDB/Topology/Devices/NeighborsRequest
Is there any support around:
afterId/AfterIDis officially supported?