REST API for Oracle SD-WAN Edge Release 9.1.1

Get local & remote MOS data

get

http://<SDWAN_TENANT_IP>/v1/admin/statistics/qoe

Request

There are no request parameters for this operation.

There's no request body for this operation.

Response

Supported Media Types

application/json

200 Response

Result OK

Root Schema : schema

Type: object

401 Response

Not Logged into the SDWAN-Edge device

Root Schema : 401NotLoggedin

Type: object

Show Source

message: string

Example: Not logged in.
status: string

Example: fail

{
    "type":"object",
    "properties":{
        "status":{
            "type":"string",
            "example":"fail"
        },
        "message":{
            "type":"string",
            "example":"Not logged in."
        }
    }
}

403 Response

Insufficient Userlevel

Root Schema : 403InsufficientUserLevel

Type: object

Show Source

message: string

Example: User Level for user <user_name> is not sufficient for this <URL value> operation.
required_user_level: string

Example: ADMIN
status: string

Example: fail
user_level: string

Example: GUEST
user_name: string

Example: username

{
    "type":"object",
    "properties":{
        "status":{
            "type":"string",
            "example":"fail"
        },
        "user_name":{
            "type":"string",
            "example":"username"
        },
        "user_level":{
            "type":"string",
            "example":"GUEST"
        },
        "required_user_level":{
            "type":"string",
            "example":"ADMIN"
        },
        "message":{
            "type":"string",
            "example":"User Level for user <user_name> is not sufficient for this <URL value> operation."
        }
    }
}

405 Response

Invalid request method

Root Schema : 405ExpectedGet

Type: object

Show Source

message: string

Example: Operation must use a GET
status: string

Example: fail

{
    "type":"object",
    "properties":{
        "status":{
            "type":"string",
            "example":"fail"
        },
        "message":{
            "type":"string",
            "example":"Operation must use a GET"
        }
    }
}

Examples

Example of Accessing the API with cURL

The following example shows how to get local and remote MOS data by submitting a GET request on the REST resource using cURL. If the request requires a timestamp, use the timestamp from the response of the /login API. For more information about cURL, see Use cURL.

curl -X GET \
    -b cookies.txt \
    --header "Content-Type: application/json" \
    "https://$IPADDR/v1/admin/statistics/qoe"

Example of the Response Body

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

[
  {
    "qoelocal": [
      {
        "Application_Name": "DEFAULT_ICMP",
        "Minute": 276,
        "Name": "NCN0-CLIENT3",
        "Packets_Received_For_OWT": 119,
        "Packets_Received_For_Worst_Loss": 2,
        "Total_Owt": 2,
        "Update_Epoch_Time_mS": 1592450804989,
        "WAN_Egress_Packets_Lost": 0,
        "WAN_Egress_Packets_Lost_For_Worst_Loss": 0,
        "Worst_Owt": 8,
        "weMOS": 4.4,
        "weMOSWorst": 4.4
      }
    ],
    "qoeremote": [
      {
        "Application_Name": "DEFAULT_ICMP",
        "Minute": 276,
        "Name": "NCN0-CLIENT3",
        "Remote_Owt_Per_Min": 2,
        "Remote_Packets_Lost_Per_Min": 0,
        "Remote_Packets_Received_Per_Min": 119,
        "Remote_Worst_Owt": 9,
        "Remote_Worst_Packets_Lost": 0,
        "Remote_Worst_Packets_Received": 3,
        "Update_Epoch_Time_mS": 1592450804989,
        "wiMOS": 4.4,
        "wiMOSWorst": 4.4
      }
    ],
    "timestamp": "23:26:44 on 6/17/2020"
  }
]