Get Summary Performance Information

get

/api/metric/PerformanceData/readSummary

Gets summary, or legend, performance information. You can specify either of the following combinations:
  • DeviceID and MetricID
    /api/metric/PerformanceData/readSummary?DeviceID=123&MetricID=456&TimeRange=now-24h..now
  • DeviceName, DeviceZoneName, MetricType, and InstanceName
    /api/metric/PerformanceData/readSummary?DeviceName=router.example.com&DeviceZoneName=MyZoneName&MetricType=Latency&InstanceName=Device&TimeRange=now-24h..now
If you specify both, the IDs takes precedence.

Request

Query Parameters
  • The ID of the device to get performance information for (or multiple, comma-separated device IDs).
    Match All
    • Device ID (or multiple, comma-separated Device IDs)
      Example: 40
  • The name of the device to get performance information for (or multiple, comma-separated device names).
    Match All
    • The serialized device name (or multiple, comma-separated serialized device names). The device name may be serialized (include the zone id) or just the name if the zone is included separately.
      Example: router.example.com OR router.example.com;z1
  • The name of the device zone to get performance information for. Deprecated. Use serialized device name instead.
  • The name of the metric instance to get performance information for.
  • The ID of the metric to get performance information for (or multiple, comma-separated metric IDs).
    Match All
    • Metric ID (or multiple, comma-separated Metric IDs)
      Example: 154
  • The name of the metric type to get performance information for.
  • The start time in epoch time seconds.
    Match All
    • StartTime in epoch time seconds
      Example: now
  • The stop time in epoch time seconds.
    Match All
    • StopTime in epoch time seconds
      Example: now
  • A shorthand string that encompasses the start and end times in RFC3339 format or relative time literal format. Takes precedence over StartTime if both are passed in.
    Match All
    • Shorthand string that encompasses the start and end times in RFC3339 format or relative time literal format. It will take precedence over StartTime if both are passed in.
      Example: now-24h..now

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : schema
Match All
Show Source
Nested Schema : SuccessfulGetOperation
Type: object
The response body for a successful get operation.
Show Source
Nested Schema : type
Type: object
Show Source
Nested Schema : data
Type: array
The performance data summary that matches the query parameters.
Show Source
Nested Schema : metricPerformanceDataReadSummary
Type: object
Show Source

Default Response

Failed operation
Body ()
Root Schema : schema
Type: object
Show Source
Nested Schema : errors
Type: array
The list of errors reported. Validation errors will be keyed by record field.
Show Source
Nested Schema : items
Type: object
An error.
Back to Top

Examples

The following examples show how to use query parameters in Get Summary Performance Information requests.

You can submit requests using cURL, an API client, or your browser.

To use the DeviceID and MetricID parameters:

http://hostFQDN/api/metric/PerformanceData/readSummary?DeviceID=123&MetricID=456&TimeRange=now-24h..now

To use the DeviceName, DeviceZoneName, MetricType, and InstanceName parameters:

http://hostFQDN/api/metric/PerformanceData/readSummary?DeviceName=router.example.com&DeviceZoneName=MyZoneName&MetricType=Latency&InstanceName=Device&TimeRange=now-24h..now

If you specify a combination of name and ID parameters (for example, both DeviceName and DeviceID), the value in the ID is used.

Example of the Response Body

The following example shows the contents of the response body in JSON format:

{
  "success": "true",
  "message": "Loaded 1 entries",
  "data": [
    {
      "MetricInstanceName": "Device",
      "Maximum": "0",
      "InstanceName": "Device",
      "MetricTypeName": "Latency",
      "Measurement": "metrictype_Latency",
      "Unit": "bits",
      "Abbr": "b",
      "UnitDivision": "1024",
      "Factor": "8",
      "PollTime": "300",
      "AverageValue": "1000",
      "MinimumValue": "0",
      "MaximumValue": "5000",
      "SumValue": "300000",
      "LastValue": "1500",
      "AverageAvailability": "1",
      "MinimumAvailability": "1",
      "MaximumAvailability": "1",
      "LastAvailability": "1",
      "AverageUtilization": "50",
      "MinimumUtilization": "0",
      "MaximumUtilization": "100",
      "LastUtilization": "60"
    }
  ]
}
Back to Top