Cisco Cisco Prime Performance Manager 1.7 開発者ガイド
Cisco Prime Performance Manager 1.7 REST API Guide
<reportHeader>Interface Availability Percentage Down</reportHeader>
<reportHeader>Interface Availability Percentage Up</reportHeader>
<reportHeader>Interface Availability Percentage
Timeout</reportHeader>
</reportHeaders>
<reportData>
<reportDataItems>
<reportDataItem>ems3825d</reportDataItem>
<reportDataItem>GigabitEthernet0/0</reportDataItem>
<reportDataItem>2012-10-05T05:00-0400</reportDataItem>
<reportDataItem>1</reportDataItem>
<reportDataItem>0.0</reportDataItem>
<reportDataItem>100.0</reportDataItem>
<reportDataItem>0.0</reportDataItem>
</reportDataItems>
. . .
. . .
<reportDataItems>
<reportDataItem>SimLab-30.4.1.90</reportDataItem>
<reportDataItem>My_ifAlias_string-
GigabitEthernet0'1</reportDataItem>
<reportDataItem>2012-10-05T12:00-0400</reportDataItem>
<reportDataItem>3</reportDataItem>
<reportDataItem>0.0</reportDataItem>
<reportDataItem>100.0</reportDataItem>
<reportDataItem>0.0</reportDataItem>
</reportDataItems>
</reportData>
</report>
<reportHeader>Interface Availability Percentage Up</reportHeader>
<reportHeader>Interface Availability Percentage
Timeout</reportHeader>
</reportHeaders>
<reportData>
<reportDataItems>
<reportDataItem>ems3825d</reportDataItem>
<reportDataItem>GigabitEthernet0/0</reportDataItem>
<reportDataItem>2012-10-05T05:00-0400</reportDataItem>
<reportDataItem>1</reportDataItem>
<reportDataItem>0.0</reportDataItem>
<reportDataItem>100.0</reportDataItem>
<reportDataItem>0.0</reportDataItem>
</reportDataItems>
. . .
. . .
<reportDataItems>
<reportDataItem>SimLab-30.4.1.90</reportDataItem>
<reportDataItem>My_ifAlias_string-
GigabitEthernet0'1</reportDataItem>
<reportDataItem>2012-10-05T12:00-0400</reportDataItem>
<reportDataItem>3</reportDataItem>
<reportDataItem>0.0</reportDataItem>
<reportDataItem>100.0</reportDataItem>
<reportDataItem>0.0</reportDataItem>
</reportDataItems>
</reportData>
</report>
7 Pagination
The reports retrieved from the REST API has an upper limit set to 1000 records per page unless modified
by the “maxPageSize” parameter. If a report has more than 1000 records (or the “maxPageSize”),
the report is divided into pages. The first REST response contains the first 1000 records along with a
“Content-Range” header (refer to HTTP Response Headers section of this document).
by the “maxPageSize” parameter. If a report has more than 1000 records (or the “maxPageSize”),
the report is divided into pages. The first REST response contains the first 1000 records along with a
“Content-Range” header (refer to HTTP Response Headers section of this document).
When the report is broken into multiple pages, use the “pageIndex” parameter to navigate to the next
pages. The “Content-Range” HTTP header value provides the current page number and number of pages
the report contains.
pages. The “Content-Range” HTTP header value provides the current page number and number of pages
the report contains.
The following table shows a report sample that displays the “pageIndex” request parameter set to page
number “3”. The “Content-Range” header response displays page number 3 of 8 pages total.
number “3”. The “Content-Range” header response displays page number 3 of 8 pages total.
Table 58 - CSV Request / Response Sample Showing Pagination (Content-Range Header)
Request
GET
/ppm/rest/reports/Availability/Interfaces/Interface++Availability?
pageIndex=3
HTTP/1.1
Host: ppm-clean.cisco.com:4440
Response – Notice the “Content-Range” header indicating pagination.
HTTP/1.1 206 Partial Content
Transfer-Encoding: chunked
Date: Fri, 05 Oct 2012 21:08:04 GMT
Host: ppm-clean.cisco.com:4440
Response – Notice the “Content-Range” header indicating pagination.
HTTP/1.1 206 Partial Content
Transfer-Encoding: chunked
Date: Fri, 05 Oct 2012 21:08:04 GMT