Getting trend in the number of configuration changes

Ops Center Analyzer REST API Reference Guide

Version

11.0.x

Audience

anonymous

Part Number

MK-99ANA003-20

You can obtain the trend in the number of configuration changes.

Execution permission

Admin, Modify

Request line

POST baseURL/v1/services/ChangeHistorys/actions/getTrend/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 GetChangeCountParam objects necessary to execute an operation. For details, see the table below.

GetChangeCountParam

{
        "nodeIDs":["...", ...],
        "deviceTypes":["...", ...],
        "countFrom":"...",
        "countTo":"...",
        "interval":"..."
}

GetChangeCountParam (Type: GetChangeCountParam)

Attribute	Type	Description
nodeIDs	long[]	ID of the device for which the configuration change occurred
deviceTypes	enum[]	Type of device for which the configuration change occurred (For details about the valid values, see the table NodeDisplayType in List of enumerators.) Server Storage NetworkDevice Datastore
countFrom	dateTime	Aggregation start time of the configuration change history
countTo	dateTime	Aggregation end time of the configuration change history
interval	long	Aggregation interval of the configuration change history (ms).

Response body

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

ChangeCount

{
        "deviceType":"...",
        "periodFrom":"...",
        "count":"..."
}

ChangeCount (Type: ChangeCount)

Attribute	Type	Description
deviceType	enum	Type of device for which the configuration change occurred (For details about the valid values, see the table NodeDisplayType in List of enumerators.) Server Storage NetworkDevice Datastore
periodFrom	dateTime	Start time for the aggregation of the configuration change history
count	long	Number of configuration change histories

Attribute

Type

Description

deviceType

enum

Type of device for which the configuration change occurred

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

Server
Storage
NetworkDevice
Datastore

periodFrom

dateTime

Start time for the aggregation of the configuration change history

count

long

Number of configuration change histories

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.
412	Precondition Failed	The server is not available.
500	Internal Server Error	Server processing error.

Example code

[Request Header]
POST /Analytics/v1/services/ChangeHistorys/actions/getTrend/invoke HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json

[Request Body]
{
  "name" : "getTrend",
  "href" : "http://localhost:22015/Analytics/v1/services/ChangeHistorys/actions/getTrend/invoke",
  "method" : "POST",
  "type" : "application/json",

    "parameters":
    [
        {
            "countFrom": "2016-08-21T16:33:09.931+09:00",
            "countTo": "2016-08-22T16:33:09.931+09:00",
            "interval": 3600000
        }
    ]
}

[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 07:36:19 GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO d7cc224d2febee6f4345b8c1913f46150f9a8_YXZvNFILd2IcDAIaWXcFMFR3FVc=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block 
X-Content-Type-Options: nosniff
Content-Type: application/json

[Response Body]
{
  "instanceID" : "d7a87b6b-ddd8-49c9-b890-16a27ae95727",
  "created" : "2016-08-22T16:36:20.243+09:00",
  "updated" : "2016-08-22T16:36:20.243+09:00",
  "completed" : "2016-08-22T16:36:20.243+09:00",
  "state" : "success",
  "affectedResource" : [ ],
  "result" : [ {
    "periodFrom" : "2016-08-21T16:33:09.931+09:00",
    "count" : 110
  }, {
    "periodFrom" : "2016-08-21T17:33:09.931+09:00",
    "count" : 13
  }, {
    "periodFrom" : "2016-08-21T18:33:09.931+09:00",
    "count" : 5
  }, {
    "periodFrom" : "2016-08-21T19:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-21T20:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-21T21:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-21T22:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-21T23:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T00:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T01:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T02:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T03:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T04:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T05:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T06:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T07:33:09.931+09:00",
    "count" : 2
  }, {
    "periodFrom" : "2016-08-22T08:33:09.931+09:00",
    "count" : 3
  }, {
    "periodFrom" : "2016-08-22T09:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T10:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T11:33:09.931+09:00",
    "count" : 0
  }, {
    "periodFrom" : "2016-08-22T12:33:09.931+09:00",
    "count" : 15
  }, {
    "periodFrom" : "2016-08-22T13:33:09.931+09:00",
    "count" : 30
  }, {
    "periodFrom" : "2016-08-22T14:33:09.931+09:00",
    "count" : 80
  }, {
    "periodFrom" : "2016-08-22T15:33:09.931+09:00",
    "count" : 55
  } ]
}