Getting a list of threshold informations with profiles and resources specified

Ops Center Analyzer REST API Reference Guide

Version

11.0.x

Audience

anonymous

Part Number

MK-99ANA003-18

You can obtain dynamic or static threshold information by specifying a threshold profile and resources.

Execution permission

Admin, Modify

Request line

POST baseURL/v1/objects/ThresholdProfiles/{id}/actions/getResourceThresholdValues/invoke

Request body

The structure of the request body and the object attributes are as follows:

Action

{
        "name":"...",
        "href":"...",
        "method":"...",
        "type":"...",
        "parameters":["...", ...]
}

Action (Type: Action)

Attribute	Type	Description
name	string	Name of the action.
href	string	URL for the action.
method	string	Name of the method.
type	string	Data format for the object.
parameters	anyType[]	A list of ResourceThresholdParam objects necessary to execute an operation. For details, see the table below.

ResourceThresholdParam

{
        "metricType":"...",
        "resourceType":"...",
        "resourceIds":["...", ...]
}

ResourceThresholdParam (Type: ResourceThresholdParam)

Attribute	Type	Description
metricType	enum	ID of the metric to be obtained (For details about the valid values, see the table MetricType in List of enumerators.)
resourceType	enum	Type of the metric to be obtained (For details about the valid values, see the table PerformanceResourceType in List of enumerators.)
resourceIds	string[]	ID of the resource to be obtained. To obtain multiple resources at the same time, specify the IDs of those resources.

Attribute

Type

Description

metricType

enum

ID of the metric to be obtained

(For details about the valid values, see the table MetricType in List of enumerators.)

resourceType

enum

Type of the metric to be obtained

(For details about the valid values, see the table PerformanceResourceType in List of enumerators.)

resourceIds

string[]

ID of the resource to be obtained. To obtain multiple resources at the same time, specify the IDs of those resources.

Response body

The structure of the response body and the object attributes is as follows:

Job

{
        "instanceID":"...",
        "created":"...",
        "updated":"...",
        "completed":"...",
        "state":"...",
        "affectedResource":["...", ...],
        "result":["...", ...]
}

Job (Type: Job)

Attribute	Type	Description
instanceID	string	ID of the Instance.
created	string	Date the object is generated in "yyyy-mm-ddThh:mm:ss.mmmTZD" format (e.g., 2017-08-25T20:07:39.472+09:00).
updated	string	Time the object is updated in "yyyy-mm-ddThh:mm:ss.mmmTZD" format (e.g., 2017-08-25T20:07:39.472+09:00).
completed	string	Time the processing completed in "yyyy-mm-ddThh:mm:ss.mmmTZD" format (e.g., 2017-08-25T20:07:39.472+09:00).
state	string	One of the following values is set: "failed": The operation failed. "success": The operation completed successfully.
affectedResource	string[]	A blank space is set.
result	anyType[]	A list of objects. No value is set.

Status codes

Status code	Reason phrase	Description
200	OK	Success.
400	Bad Request	The format of the request body is invalid.
401	Unauthorized	No login privilege.
403	Forbidden	No update privilege.
404	Not Found	The resource was not found.
412	Precondition Failed	The server is not available.
500	Internal Server Error	Server processing error.
503	Service Unavailable	Analyzer detail view server communication error.

Example code

[Request Header]
POST /Analytics/v1/objects/ThresholdProfiles/thProfile%23fe428a12-35a8-4210-8e9d-d0d28fe38d5d/actions/getResourceThresholdValues/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json

[Request Body]
{
  "name": "getResourceThresholdValues",
    "href" : "http://localhost:22015/Analytics/v1/objects/ThresholdProfiles/thProfile%23fe428a12%2d35a8%2d4210%2d8e9d%2dd0d28fe38d5d/actions/getResourceThresholdValues/invoke",
  "method": "POST",
  "type": "application/json",
  "parameters":[{
    "resourceType":"ESX_VM",
    "metricType":"ESX_VM_VM_CPUREADY",
    "resourceIds":["vm#ABC_172.17.17.115_vm-142"]
  }]
}

[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 02:54:28 GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json


[Response Body]
{
  "instanceID" : "21735e31-eb30-4c9d-b049-9c8f161619b4",
  "created" : "2016-07-20T11:54:29.279+09:00",
  "updated" : "2016-07-20T11:54:31.282+09:00",
  "completed" : "2016-07-20T11:54:31.282+09:00",
  "state" : "success",
  "affectedResource" : [ ],
  "result" : [ {
    "instanceID" : "vm#ABC_172.17.17.115_vm-142",
    "metricType" : "ESX_VM_VM_CPUREADY",
    "metricTypeName" : "CPU Ready (VMware Virtual Machine)",
    "resourceType" : "ESX_VM",
    "resourceId" : "vm#ABC_172.17.17.115_vm-142",
    "resourceName" : "exampleVM",
    "profileId" : "thProfile#ESX_VM",
    "profileName" : "Default Profile for VM (VMware)",
    "values" : [ {
      "instanceID" : "thPlan#ESX_VM",
      "planType" : "Base",
      "planName" : "Base",
      "schedule" : [ 1, 2, 3, 4, 5, 6, 7 ],
      "from" : "00:00",
      "to" : "24:00",
      "priority" : 1,
      "description" : "Base Plan",
      "monitoringMode" : "Dynamic",
      "unit" : "msec",
      "proportion" : false,
      "stepSize" : 1.0,
      "max" : 3.4028235E38,
      "min" : 0.0,
      "fixed" : false
    } ]
  } ]
}