Download full document:

ns_l7_latency_config

Configuration for L7 Latency configuration on NetScaler resource.

(click to see Operations)

Properties

(click to see Operations)

NameData TypePermissionsDescription
vserverType<String>Read-writeVirtual server type(lb/sslvpn/CR).
Minimum length = 2
Maximum length = 64
l7LatencyThresholdNotifyIntetval<Integer>Read-writeL7 Latency Threshold Notify Intetval.
l7LatencyNotifyCount<Integer>Read-writeL7 Latency Notify Count.
l7LatencyThresholdWaitInterval<Integer>Read-writeL7 Latency Threshold Wait Interval.
ns_ip_address<String>Read-writeNetScaler IP Address.
Minimum length = 1
Maximum length = 64
l7LatencyThresholdFactor<Integer>Read-writeL7 Latency Threshold Factor Value.
vserverName<String>Read-writeVirtual server name.
Maximum length = 255
l7LatencyMonitoring<String>Read-writeENABLE/DISABLE.
Maximum length = 512
latencyName<String>Read-onlyName of latency profile.

Operations

(click to see Properties)

GET (ALL)| MODIFY

Some options that you can use for each operations:

  • Getting warnings in response:NITRO allows you to get warnings in an operation by specifying the "warning" query parameter as "yes". For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

    http://<netscaler-ip-address>/nitro/v1/config/login?warning=yes

    If any, the warnings are displayed in the response payload with the HTTP code "209 X-NITRO-WARNING".

  • Authenticated access for individual NITRO operations:NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:

    X-NITRO-USER:<username>

    X-NITRO-PASS:<password>

    Note: In such cases, make sure that the request header DOES not include the following:

    Cookie:NITRO_AUTH_TOKEN=<tokenvalue>

Note:

Mandatory parameters are marked in red and placeholder content is marked in <green>.

get (all)

URL: https://<MGMT-IP>/nitro/v1/config/ns_l7_latency_config

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "ns_l7_latency_config":[{
"vserverType":<String_value>,
"l7LatencyThresholdNotifyIntetval":<Integer_value>,
"l7LatencyNotifyCount":<Integer_value>,
"l7LatencyThresholdWaitInterval":<Integer_value>,
"ns_ip_address":<String_value>,
"l7LatencyThresholdFactor":<Integer_value>,
"latencyName":<String_value>,
"vserverName":<String_value>,
"l7LatencyMonitoring":<String_value>}]}

modify

URL: https://<MGMT-IP>/nitro/v1/config/ns_l7_latency_config/

HTTP Method: null

Request Payload:

{ns_l7_latency_config:{
"l7LatencyThresholdNotifyIntetval":<Integer_value>,
"vserverType":<String_value>,
"l7LatencyThresholdWaitInterval":<Integer_value>,
"l7LatencyNotifyCount":<Integer_value>,
"ns_ip_address":<String_value>,
"vserverName":<String_value>,
"l7LatencyThresholdFactor":<Integer_value>,
"l7LatencyMonitoring":<String_value>}}

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "ns_l7_latency_config":[{
"vserverType":<String_value>,
"l7LatencyThresholdNotifyIntetval":<Integer_value>,
"l7LatencyNotifyCount":<Integer_value>,
"l7LatencyThresholdWaitInterval":<Integer_value>,
"ns_ip_address":<String_value>,
"l7LatencyThresholdFactor":<Integer_value>,
"latencyName":<String_value>,
"vserverName":<String_value>,
"l7LatencyMonitoring":<String_value>}]}