event_summary
Properties
| Name | Data Type | Permissions | Description |
|---|---|---|---|
| Warning | <Integer> | Read-only | Total Number of Warning Events. |
| Minor | <Integer> | Read-only | Total number of Minor Events. |
| Information | <Integer> | Read-only | Total number of Information Events. |
| Major | <Integer> | Read-only | Total number of Major Events. |
| Critical | <Integer> | Read-only | Total Number of Critical Events. |
| category | <String> | Read-only | Category of Event. |
| Clear | <Integer> | Read-only | Total Number of Warning Events. |
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, "event_summary":[{
"Warning":<Integer_value>,
"Minor":<Integer_value>,
"Information":<Integer_value>,
"Major":<Integer_value>,
"Critical":<Integer_value>,
"category":<String_value>,
"Clear":<Integer_value>}]}