Jump to

• Request
• Response
• Examples

Get the Node Usage Related Metrics

get

/console/admin/api/v1.1/dashboard/statistics/nodeRes

Get the node usage related metrics (CPU, memory, disk usage).

Request

Supported Media Types

• application/json

Query Parameters

• endTime(optional): string
  The end time of a time range in the format 'yyyyMMddhhmmss'
• nodeID(optional): string
  Node ID of a specific peer, orderer, proxy, or the console itself
• startTime(optional): string
  The start time of a time range in the format 'yyyyMMddhhmmss'

Back to Top

Response

Supported Media Types

• application/json

200 Response

Response with a series of usage records by restriction

Body ()

Root Schema : schema

Type: object

Show Source

• data(optional): array data

{
    "type":"object",
    "properties":{
        "data":{
            "type":"array",
            "items":{
                "$ref":"#/definitions/StatsNodeRes"
            }
        }
    }
}

Nested Schema : data

Type: array

Show Source

• Array of: object StatsNodeRes

{
    "type":"array",
    "items":{
        "$ref":"#/definitions/StatsNodeRes"
    }
}

Nested Schema : StatsNodeRes

Type: object

Show Source

• nodeId(optional): string
• nodeType(optional): string
• resUsage(optional): object resUsage

{
    "type":"object",
    "properties":{
        "nodeId":{
            "type":"string"
        },
        "nodeType":{
            "type":"string"
        },
        "resUsage":{
            "type":"object",
            "properties":{
                "startTime":{
                    "type":"string"
                },
                "endTime":{
                    "type":"string"
                },
                "cpu":{
                    "type":"number"
                },
                "memory":{
                    "type":"number"
                },
                "disk":{
                    "type":"number"
                }
            }
        }
    }
}

Nested Schema : resUsage

Type: object

Show Source

• cpu(optional): number
• disk(optional): number
• endTime(optional): string
• memory(optional): number
• startTime(optional): string

{
    "type":"object",
    "properties":{
        "startTime":{
            "type":"string"
        },
        "endTime":{
            "type":"string"
        },
        "cpu":{
            "type":"number"
        },
        "memory":{
            "type":"number"
        },
        "disk":{
            "type":"number"
        }
    }
}

400 Response

invalid arguments

Body ()

Root Schema : 400errorModels

Type: object

Show Source

• key(optional): string
• value(optional): string

{
    "type":"object",
    "properties":{
        "key":{
            "type":"string"
        },
        "value":{
            "type":"string"
        }
    },
    "example":{
        "respMesg":"invalid argument"
    }
}

Example:

{
    "respMesg":"invalid argument"
}

Default Response

unexpected error

Body ()

Root Schema : errorModel

Type: object

Show Source

• code: integer(int32)
• message: string

{
    "type":"object",
    "required":[
        "code",
        "message"
    ],
    "properties":{
        "code":{
            "type":"integer",
            "format":"int32"
        },
        "message":{
            "type":"string"
        }
    }
}

Back to Top

Examples

This endpoint is used to get the node usage related metrics such as CPU, memory, and disk usage percentages, reflecting the health metrics you can see on the console. The result is a JSON body which contains a series of usage records for the specified nodes in the specified time range. If nodeID is not specified, it returns this information for all nodes in the instance. If the time range is specified, the returned usage information is the average value of all the usage over the specified time range. If time range is not specified, the latest usage information is returned, plus a one minute time range.

The following example shows how to generate the node metrics by submitting a GET request on the REST resource using cURL.

curl -X GET -u username:password -k 
"http://<rest_server_url>:port/console/admin/api/v1.1/dashboard/statistics/nodeRes?nodeID=<nodeID>&startTime=<yyyymmddhhmmss>&endTime=yyyymmddhhmmss"

For example,

curl -X GET -u [e-mail]:mypswd -k 
"http://server.oracle.com:10000/console/admin/api/v1.1/dashboard/statistics/nodeRes?nodeID=peer0-1&startTime=20190224000000&endTime=20190224050000"

Example of the Response Body

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

{
  "data": [
    {
      "nodeId": "peer0-1",
      "nodeType": "peer",
      "resUsage": {
        "startTime": "Sun, 24 Feb 2019 00:00:00 GMT",
        "endTime": "Sun, 24 Feb 2019 05:00:00 GMT",
        "cpu": 2.8215833333333333,
        "memory": 0.34320972222222224,
        "disk": 0.065
      }
    }
  ]
}

Back to Top