anomaly_details
Properties
| Name | Data Type | Permissions | Description |
|---|---|---|---|
| hits_rate | <Double> | Read-write | Hits Rate. |
| __count | <Double> | Read-write | count.. |
| serv_tot_hits | <Double> | Read-write | Last Transaction Time for this URL in the sampled timeframe.. |
| state | <String> | Read-write | State up/down. Minimum length = 1 Maximum length = 64 |
| max_avg_ttfb | <Double> | Read-write | max_avg_ttfb time.. |
| max_hits | <Double> | Read-write | Count of this URL in given sampled timeframe.. |
| metric_name | <String> | Read-write | HTTP Request Method.. Maximum length = 30 |
| svcname | <String> | Read-write | AppName. Maximum length = 255 |
| ctnsappname | <String> | Read-write | AppName. Maximum length = 255 |
| ip_address | <String> | Read-write | IP Address. Maximum length = 512 |
| server_ip_address | <String> | Read-write | Server Source IP Address. Minimum length = 1 Maximum length = 64 |
| reason | <String> | Read-write | HTTP Request URL.. Maximum length = 100 |
| rpt_sample_time | <Double> | Read-write | Report Sample time.. |
| usecase | <String> | Read-write | Use Case.. Maximum length = 100 |
| avg_ttfb | <Double> | Read-write | Render time.. |
| hits_total | <Double> | Read-write | Total bytes accounted by this URL in sampled timeframe.. |
Operations
- GET (ALL)
-
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=yesIf 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)
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "anomaly_details":[{
"hits_rate":<Double_value>,
"__count":<Double_value>,
"serv_tot_hits":<Double_value>,
"metric_key":<String_value>,
"state":<String_value>,
"max_avg_ttfb":<Double_value>,
"max_hits":<Double_value>,
"metric_name":<String_value>,
"svcname":<String_value>,
"ctnsappname":<String_value>,
"ip_address":<String_value>,
"server_ip_address":<String_value>,
"reason":<String_value>,
"rpt_sample_time":<Double_value>,
"usecase":<String_value>,
"avg_ttfb":<Double_value>,
"hits_total":<Double_value>}]}