Nodes can be managed using REST API

Node creation

New node is created automatically when WCS server which is not in the database connects to backend server.

Node changing

The node parameters can be changed with REST API query /api/node/update

https://hostname:8090/api/node/update
{
  "id": "15",
  "profiles": ["14", "17"]
}

Where:

• id – node identifier
• profiles – profile identifies list by which metrics are aquired fron this node

Node deletion

The node can be deleted with REST API query /api/node/delete

https://hostname:8090/api/node/delete
{
  "id": "3"
}

Where:

• id – node identifier

This node monitoring stops when node is deleted.

Obtaining node information

The node information can be obtained with REST API query /api/node/list

https://hostname:8090/api/node/list
{
  "id": "3"
}

Where:

• id – node identifier

If node Id is set, the response will contain this node information only. If Id is not set, the response will contain all the nodes list on backend server.

The response contains the following fields

[
    {
        "id": 3,
        "host": "95.191.131.64",
        "profiles": [
            2
        ]
    }
]

Where:

• id – node identifier
• host - WCS server address
• profiles - profiles list

Obtaining node current state

The node current state can be obtained with REST API query  /api/node_status/list

https://hostname:8090/api/node_status/list
{
  "id": "13"
}

Where:

• id – node identifier

If node Id is set, the response will contain this node state only. If Id is not set, the response will contain all the nodes current state on backend server.

The response contains the following fields

[
    {
        "id": 15,
        "connectTimestamp": 1545645928951,
        "connectCounter": 1,
        "connected": true,
        "rate": 0
    }
]

Здесь

• id – node identifier
• connectTimeStamp – current connection timestamp
• connectCounter – current connection tries count
• connected – is the connection established
• rate – metrics aquisition rate