Skip to content

web_detail_data_collection_config

Configuration for web detail data collection config resource.

Properties

(click to see Operations )

Name Data Type Permissions Description
network_latency_client_side <Double> Read-write Network Latency Client side Time should be greate than value or equal to .(millisec).
server_response_time <Double> Read-write Server Response Time should be greate than or equal to value.(millisec).
network_latency_server_side <Double> Read-write Network Latency Client server Time should be greate than or equal to value.(millisec).
application_response_time <Double> Read-write Application Response Time should be greater than or equal to value. (millisec).
http_rsp_status_2xx_enabled <Integer> Read-write HTTP Response Status Method collect enabled for 2xx response..
name <String> Read-only name of the configuration.
max_first_level_number_of_record <Double> Read-only Maximum number of record to be maintained at first level report..
max_second_level_number_of_record <Double> Read-only Maximum number of record to be maintained except at first level report..

Operations

(click to see Properties )

  • GET (ALL)
  • GET
  • UPDATE

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/web_detail_data_collection_config

Query-parameters:

filter https://<MGMT-IP>/nitro/v2/config/web_detail_data_collection_config ?filter=property-name1:property-value1,property-name2:property-value2

Use this query-parameter to get the filtered set of web_detail_data_collection_config 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/web_detail_data_collection_config ?pagesize=#no;pageno=#no

Use this query-parameter to get the web_detail_data_collection_config resources in chunks.

count https://<MGMT-IP>/nitro/v2/config/web_detail_data_collection_config ?count=yes

Use this query-parameter to get the count of web_detail_data_collection_config resources.

HTTPS Method: GET

Request Headers:

Accept: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

or

Cookie:NITRO_AUTH_TOKEN=token_value<String>

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:

Content-Type:application/json

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "web_detail_data_collection_config":[{
      "name":<String_value>,
      "network_latency_client_side":<Double_value>,
      "server_response_time":<Double_value>,
      "max_first_level_number_of_record":<Double_value>,
      "network_latency_server_side":<Double_value>,
      "application_response_time":<Double_value>,
      "http_rsp_status_2xx_enabled":<Integer_value>,
      "max_second_level_number_of_record":<Double_value>}]}

get

URL: https://<MGMT-IP>/nitro/v2/config/web_detail_data_collection_config/name_value<String>

HTTPS Method: GET

Request Headers:

Accept: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

or

Cookie:NITRO_AUTH_TOKEN=token_value<String>

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:

Content-Type:application/json

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "web_detail_data_collection_config":[{
      "name":<String_value>,
      "network_latency_client_side":<Double_value>,
      "server_response_time":<Double_value>,
      "max_first_level_number_of_record":<Double_value>,
      "network_latency_server_side":<Double_value>,
      "application_response_time":<Double_value>,
      "http_rsp_status_2xx_enabled":<Integer_value>,
      "max_second_level_number_of_record":<Double_value>}]}

update

URL: https://<MGMT-IP>/nitro/v2/config/web_detail_data_collection_config/name_value<String>

HTTPS Method: PUT

Request Headers:

Content-Type: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

or

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Request Payload:

{"web_detail_data_collection_config":{
<b>      "application_response_time":<Double_value></b>,
      "network_latency_client_side":<Double_value>,
      "http_rsp_status_2xx_enabled":<Integer_value>,
      "server_response_time":<Double_value>,
      "network_latency_server_side":<Double_value>}}

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 Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "web_detail_data_collection_config":[{
      "name":<String_value>,
      "network_latency_client_side":<Double_value>,
      "server_response_time":<Double_value>,
      "max_first_level_number_of_record":<Double_value>,
      "network_latency_server_side":<Double_value>,
      "application_response_time":<Double_value>,
      "http_rsp_status_2xx_enabled":<Integer_value>,
      "max_second_level_number_of_record":<Double_value>}]}
Was this article helpful?