Cisco Cisco Prime Performance Manager 1.7 Developer's Guide
Cisco Prime Performance Manager 1.7 REST API Guide
Additional Notes
Only supported in the “GET /{reportType} /{category}../{reportName}”requests
Not supported by views.
5.7.15 filterAlgorithm
Table 21 – filterAlgorithm Parameter
Parameter
Notes
filterAlgorithm
The filterAlgorithm parameter is used to filter the reporting data using
complex algorithms. This parameter is similar to the reportObjectFilter
parameter, except that this parameter accepts complex algorithms. A complex
algorithm takes combinations of “or”, “and” and any macro implemented by
Prime Performance Manager reports. For more information about the Prime
Performance Manager macro refer to Prime Performance Manager Integration
Document.
You may use combinations of “or” and “and” along with any accepted macro
available in the Prime Performance Manager system to construct your
complex algorithm. You should notice that we only validate if the algorithm
can be parsed; that is, if Prime Performance Manager Algorithm Parser is able
to parse the given algorithm. We do NOT validate the names of the table
columns names and whether the algorithm is truly valid. Therefore, the user
may get an empty response if Prime Performance Manager is applying the
given algorithm on a set of columns that are not found for that report, or if the
algorithm does not make any sense.
Examples:
filterAlgorithm=CPUSlots==0 @and CPUNum==769 @and
CPUUtilAvg5min>0.8
complex algorithms. This parameter is similar to the reportObjectFilter
parameter, except that this parameter accepts complex algorithms. A complex
algorithm takes combinations of “or”, “and” and any macro implemented by
Prime Performance Manager reports. For more information about the Prime
Performance Manager macro refer to Prime Performance Manager Integration
Document.
You may use combinations of “or” and “and” along with any accepted macro
available in the Prime Performance Manager system to construct your
complex algorithm. You should notice that we only validate if the algorithm
can be parsed; that is, if Prime Performance Manager Algorithm Parser is able
to parse the given algorithm. We do NOT validate the names of the table
columns names and whether the algorithm is truly valid. Therefore, the user
may get an empty response if Prime Performance Manager is applying the
given algorithm on a set of columns that are not found for that report, or if the
algorithm does not make any sense.
Examples:
filterAlgorithm=CPUSlots==0 @and CPUNum==769 @and
CPUUtilAvg5min>0.8
Additional Notes
Only supported in the “GET /{reportType}/{category}../{reportName}”requests
Not supported by views.
5.7.16 deviceTimeZone
Table 22 – deviceTimeZone Parameter
Parameter
Notes
deviceTimeZone
The deviceTimeZone parameter allows node level reports to display
timestamps using the device (node) time zone. By default node level reports
use timestamps displayed on the server configured time zone
The deviceTimeZone parameter is a boolean text value that can be set for
node level reports request.
Possible values:
true
false
Examples:
deviceTimeZone=true
deviceTimeZone=false
timestamps using the device (node) time zone. By default node level reports
use timestamps displayed on the server configured time zone
The deviceTimeZone parameter is a boolean text value that can be set for
node level reports request.
Possible values:
true
false
Examples:
deviceTimeZone=true
deviceTimeZone=false