auditmessages¶

Configuration for audit message resource.

Properties¶

(click to see Operations )

Name	Data Type	Permissions	Description
loglevel	<String[]>	Read-write	Audit log level filter, which specifies the types of events to display. The following loglevels are valid: * ALL - All events. * EMERGENCY - Events that indicate an immediate crisis on the server. * ALERT - Events that might require action. * CRITICAL - Events that indicate an imminent server crisis. * ERROR - Events that indicate some type of error. * WARNING - Events that require action in the near future. * NOTICE - Events that the administrator should know about. * INFORMATIONAL - All but low-level events. * DEBUG - All events, in extreme detail. Possible values = ALL, EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, NOTICE, INFORMATIONAL, DEBUG
numofmesgs	<Double>	Read-write	Number of log messages to be displayed. Default value: 20 Minimum value = 1 Maximum value = 256
value	<String>	Read-only	The Audit message.
__count	<Double>	Read-only	count parameter

Operations¶

(click to see Properties )

GET (ALL)
COUNT

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

get (all)¶

URL: http:// <netscaler-ip-address> /nitro/v1/config/auditmessages

Query-parameters:

args

http:// <netscaler-ip-address> /nitro/v1/config/auditmessages? args=loglevel: <String[]_value> ,numofmesgs: <Double_value>

Use this query-parameter to get auditmessages resources based on additional properties.

attrs

http:// <netscaler-ip-address> /nitro/v1/config/auditmessages? attrs=property-name1,property-name2

Use this query parameter to specify the resource details that you want to retrieve.

filter

http:// <netscaler-ip-address> /nitro/v1/config/auditmessages? filter=property-name1:property-val1,property-name2:property-val2

Use this query-parameter to get the filtered set of auditmessages resources configured on NetScaler.Filtering can be done on any of the properties of the resource.

view

http:// <netscaler-ip-address> /nitro/v1/config/auditmessages? view=summary

Use this query-parameter to get the summary output of auditmessages resources configured on NetScaler.

Note: By default, the retrieved results are displayed in detail view (?view=detail).

pagination

http:// <netscaler-ip-address> /nitro/v1/config/auditmessages? pagesize=#no;pageno=#no

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

HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Accept:application/json

Response:

HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Response Header:

Content-Type:application/json

Response Payload:

{ "auditmessages": [ {
loglevel:<String[]_value>,numofmesgs:<Double_value>      "value":<String_value>
}]}

count¶

URL: http:// <netscaler-ip-address> /nitro/v1/config/auditmessages? count=yes