You can obtain information about a specific history of configuration changes.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/ChangeHistorys/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:ChangeHistory
{ "instanceID":"...", "message":"...", "dateTime":"...", "nodeId":"...", "deviceName":"...", "deviceType":"...", "componentId":"...", "componentName":"...", "componentType":"...", "attributeType":"...", "previousValue":"...", "newValue":"...", "componentChangeType":"...", "nodeChangeType":"..." }
ChangeHistory (Type: ChangeHistory)
Attribute |
Type |
Description |
---|---|---|
instanceID |
string |
ID of the configuration change history |
message |
string |
Message of the configuration change history |
dateTime |
dateTime |
Configuration change detection time |
nodeId |
string |
ID of the device for which the configuration change occurred |
deviceName |
string |
Name of the device for which the configuration change occurred |
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.)
|
componentId |
string |
ID of the component for which the configuration change occurred |
componentName |
string |
Name of the component for which the configuration change occurred |
componentType |
enum |
Type of component for which the configuration change occurred (For details about the valid values, see the table ComponentType in List of enumerators.) |
attributeType |
enum |
Attribute type of component for which the configuration change occurred (For details about the valid values, see the table ComponentAttributeType in List of enumerators.) |
previousValue |
string |
Value before the configuration is changed |
newValue |
string |
Value after the configuration is changed |
componentChangeType |
enum |
Modification type of component for which the configuration change occurred (For details about the valid values, see the table ChangeEventType in List of enumerators.)
|
nodeChangeType |
enum |
Modification type of device for which the configuration change occurred (For details about the valid values, see the table ChangeEventType in List of enumerators.)
|
Status codes
Status code |
Reason phrase |
Description |
---|---|---|
200 |
OK |
Success. |
401 |
Unauthorized |
No login privilege. |
404 |
Not Found |
The resource was not found. |
412 |
Precondition Failed |
The server is not available. |
500 |
Internal Server Error |
Server processing error. |
Example code
[Request Header] GET /Analytics/v1/objects/ChangeHistorys/16$1201$vm%23ITPDLab_172.17.17.115_vm-149$vm%23ITPDLab_172.17.17.115_vm-149$null$1471252355000$MODIFY HTTP/1.1 Authorization: Basic c3lzdGVtOm1hbmFnZXI= Host: localhost:22015 Accept: application/json Content-Type: application/json [Response Header] HTTP/1.1 200 OK Date: Mon, 22 Aug 2016 07:24:22 GMT Server: Cosminexus HTTP Server Cache-Control: no-cache WWW-Authenticate: HSSO 2e48b94f47d976ece069226313cacf394cf613f3_YXZvNFILd2IcDAIaWXcFMFR3FVc=_V0810 X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff Content-Type: application/json [Response Body] { "instanceID" : "16$1201$vm#ITPDLab_172.17.17.115_vm-149$vm#ITPDLab_172.17.17.115_vm-149$null$1471252355000$MODIFY", "message" : "The number of CPU cores was changed from 2 to 1.\nDevice name: 172.17.17.119\nName of VM: CT003hoshi", "dateTime" : "2016-08-15T18:12:35.000+09:00", "nodeId" : "h#ITPDLab_172.17.17.115_host-143", "deviceName" : "172.17.17.119", "deviceType" : "Server", "componentId" : "vm#ITPDLab_172.17.17.115_vm-149", "componentName" : "CT003hoshi", "componentType" : "VIRTUAL_MACHINE", "attributeType" : "NUM_OF_CPU_CORES", "previousValue" : "2", "newValue" : "1", "componentChangeType" : "MODIFY", "nodeChangeType" : "MODIFY" }