Skip to content
Was this article helpful?


Configuration for API used to report the global service graph for per app. resource.


(click to see Operations )

Name Data Type Permissions Description
source <String> Read-write Source Node.
tot_svr_busy_err <Double> Read-write Total Server Errors.
tot_reqbytes <Double> Read-write Total Request Bytes.
destination <String> Read-write CS VServer Name.
appname <String> Read-write App name.
destination_type <String> Read-write Service Name.
response_time <Double> Read-write Response Time.
svcname <String> Read-write Service Name.
ctnsappname <String> Read-write Vserver Name.
source_type <String> Read-write LB VServer Name.
id <String> Read-write Id is system generated key.
ip_address <String> Read-write NS IP Address.
tot_respbytes <Double> Read-write Total Response Bytes.
tot_svr_ttfb <Double> Read-write Service Resp Rate.
vservername <String> Read-write Vserver Name.
tot_svr_ttfb_transactions <Double> Read-write Number of Transactions.
tot_bytes <Double> Read-write Total Bytes(Data Volume).
type <String> Read-write Vserver Type.
tot_requests <Double> Read-write Total Requests.


(click to see Properties )

  • GET (ALL)

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

The following parameters can be used in the nitro request : onerror <String_value>

Use this parameter to set the onerror status for nitro request. Applicable only for bulk requests.

Default value: EXIT

Possible values = EXIT, CONTINUE

get (all)

URL: https://<MGMT-IP>/nitro/v2/config/app_service_graph_node_edges Query-parameters:

filter https://<MGMT-IP>/nitro/v2/config/app_service_graph_node_edges ?filter=property-name1:property-value1,property-name2:property-value2 Use this query-parameter to get the filtered set of app_service_graph_node_edges resources configured on the system. You can set a filter on any property of the resource.

pagesize=#no;pageno=#no https://<MGMT-IP>/nitro/v2/config/app_service_graph_node_edges ?pagesize=#no;pageno=#no Use this query-parameter to get the app_service_graph_node_edges resources in chunks.

count https://<MGMT-IP>/nitro/v2/config/app_service_graph_node_edges ?count=yes Use this query-parameter to get the count of app_service_graph_node_edges resources.


Request Headers: Accept: application/json





Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error

Response Headers:


Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "app_service_graph_node_edges":[{
Was this article helpful?