anomaly_events

Configuration for AF Transaction Report table resource.

Read/write properties

ip_address<String>

IP Address.
Maximum length = 512

svcname<String>

svcname.
Maximum length = 255

__count<Double>

Number of records.

event_value<String>

Event Value.

ctnsappname<String>

AppName.
Maximum length = 255

rpt_sample_time<Double>

Report Sample time..

event_type<String>

Event Type..
Maximum length = 255

Operations

NOTE: In request payload, Mandatory parameters are marked red and bold.

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)

get (all)

URL:https://<MGMT-IP>/nitro/v2/config/anomaly_events

Query-parameters:

report_start_time

Use this query-parameter to specify the start time from which the summary for report is considered.

Possible Values:time in milli seconds

asc

Use this query-parameter to specify whether the results should be in ascending order or not.

Possible Values:yes, no

type

Use this query-parameter to specify the type.

Possible Values:total_requests, load_time, render_time

ns_vsvrs

Use this query-parameter to provide the infomation of netscaler and virutal server combination.

Possible Values:((ns_ip1, vsvrname1)|(ns_ip2, vsvrname2)|(ns_ip3, vsvrname3)

report_end_time

Use this query-parameter to specify the end time until where summary for report is considered.

Possible Values:time in milli seconds

order_by

Use this query-parameter to get the result that is ordered by the given property.

Possible Values:total_requests, load_time, render_time

HTTPS Method:GET

HTTPS 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:JSON

{ "errorcode": 0, "message": "Done", "severity": <String_value>, "anomaly_events":[{
      "ip_address":<String_value>,
      "svcname":<String_value>,
      "__count":<Double_value>,
      "event_value":<String_value>,
      "ctnsappname":<String_value>,
      "rpt_sample_time":<Double_value>,
      "event_type":<String_value>}]}