Download full document:

auditnslogaction

Configuration for ns log action resource.

Properties

(click to see Operations)

Name	Data Type	Permissions	Description
name	<String>	Read-write	Name of the nslog action. Must begin with a letter, number, or the underscore character (_), and must contain only letters, numbers, and the hyphen (-), period (.) pound (#), space ( ), at (@), equals (=), colon (:), and underscore characters. Cannot be changed after the nslog action is added. The following requirement applies only to the NetScaler CLI: If the name includes one or more spaces, enclose the name in double or single quotation marks (for example, ?my nslog action? or ?my nslog action).<br>Minimum length = 1
serverip	<String>	Read-write	IP address of the nslog server.<br>Minimum length = 1
serverport	<Integer>	Read-write	Port on which the nslog server accepts connections.<br>Minimum value = 1
loglevel	<String[]>	Read-write	Audit log level, which specifies the types of events to log. Available settings function as follows: * 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. * NONE - No events.<br>Possible values = ALL, EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, NOTICE, INFORMATIONAL, DEBUG, NONE
dateformat	<String>	Read-write	Format of dates in the logs. Supported formats are: * MMDDYYYY - U.S. style month/date/year format. * DDMMYYYY - European style date/month/year format. * YYYYMMDD - ISO style year/month/date format.<br>Possible values = MMDDYYYY, DDMMYYYY, YYYYMMDD
logfacility	<String>	Read-write	Facility value, as defined in RFC 3164, assigned to the log message. Log facility values are numbers 0 to 7 (LOCAL0 through LOCAL7). Each number indicates where a specific message originated from, such as the NetScaler appliance itself, the VPN, or external.<br>Possible values = LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7
tcp	<String>	Read-write	Log TCP messages.<br>Possible values = NONE, ALL
acl	<String>	Read-write	Log access control list (ACL) messages.<br>Possible values = ENABLED, DISABLED
timezone	<String>	Read-write	Time zone used for date and timestamps in the logs. Available settings function as follows: * GMT_TIME. Coordinated Universal Time. * LOCAL_TIME. The server?s timezone setting.<br>Possible values = GMT_TIME, LOCAL_TIME
userdefinedauditlog	<String>	Read-write	Log user-configurable log messages to nslog. Setting this parameter to NO causes auditing to ignore all user-configured message actions. Setting this parameter to YES causes auditing to log user-configured message actions that meet the other logging criteria.<br>Possible values = YES, NO
appflowexport	<String>	Read-write	Export log messages to AppFlow collectors. Appflow collectors are entities to which log messages can be sent so that some action can be performed on them.<br>Possible values = ENABLED, DISABLED
builtin	<String[]>	Read-only	Indicates that a variable is a built-in (SYSTEM INTERNAL) type.<br>Possible values = MODIFIABLE, DELETABLE, IMMUTABLE
__count	<Double>	Read-only	count parameter

Operations

(click to see Properties)

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>.

add

URL: http://<NSIP>/nitro/v1/config/

HTTP Method: POST

Request Payload:

object={
"params":{
      "warning":<String_value>,
      "onerror":<String_value>
},
"sessionid":"##sessionid",
"auditnslogaction":{
      "name":<String_value>,
      "serverip":<String_value>,
      "serverport":<Integer_value>,
      "loglevel":<String[]_value>,
      "dateformat":<String_value>,
      "logfacility":<String_value>,
      "tcp":<String_value>,
      "acl":<String_value>,
      "timezone":<String_value>,
      "userdefinedauditlog":<String_value>,
      "appflowexport":<String_value>,
}}

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": }

delete

URL: http://<NSIP>/nitro/v1/config/auditnslogaction/name_value<String>

Query-parameters:

warning

http://<NS_IP>/nitro/v1/config/auditnslogaction/name_value<String>?warning=yes

Use this query parameter to get warnings in nitro response. If this field is set to YES, warning message will be sent in 'message' field and 'WARNING' value is set in severity field of the response in case there is a

HTTP Method: DELETE

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": }

update

URL: http://<NSIP>/nitro/v1/config/

HTTP Method: PUT

Request Payload:

{
"params": {
      "warning":<String_value>,
      "onerror":<String_value>"
},
sessionid":"##sessionid",
"auditnslogaction":{
      "name":<String_value>,
      "serverip":<String_value>,
      "serverport":<Integer_value>,
      "loglevel":<String[]_value>,
      "dateformat":<String_value>,
      "logfacility":<String_value>,
      "tcp":<String_value>,
      "acl":<String_value>,
      "timezone":<String_value>,
      "userdefinedauditlog":<String_value>,
      "appflowexport":<String_value>,
}}

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": }

unset

URL: http://<NSIP>/nitro/v1/config/

HTTP Method: POST

Request Payload:

object={
"params":{
      "warning":<String_value>,
      "onerror":<String_value>,
      "action":"unset"
},
"sessionid":"##sessionid",
"auditnslogaction":{
      "name":<String_value>,
      "serverport":true,
      "loglevel":true,
      "dateformat":true,
      "logfacility":true,
      "tcp":true,
      "acl":true,
      "timezone":true,
      "userdefinedauditlog":true,
      "appflowexport":true,
}}

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": }

get (all)

URL: http://<NSIP>/nitro/v1/config/auditnslogaction

Query-parameters:

filter

http://<NSIP>/nitro/v1/config/auditnslogaction?filter=property-name1:property-val1,property-name2:property-val2

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

view

http://<NS_IP>/nitro/v1/config/auditnslogaction?view=summary

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

pagesize=#no;pageno=#no

http://<NS_IP>/nitro/v1/config/auditnslogaction?pagesize=#no;pageno=#no

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

warning

http://<NS_IP>/nitro/v1/config/auditnslogaction?warning=yes

Use this query parameter to get warnings in nitro response. If this field is set to YES, warning message will be sent in 'message' field and 'WARNING' value is set in severity field of the response in case there is a

HTTP Method: GET

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": <String_value>, "auditnslogaction": [ {
      "name":<String_value>,
      "serverip":<String_value>,
      "serverport":<Integer_value>,
      "loglevel":<String[]_value>,
      "dateformat":<String_value>,
      "logfacility":<String_value>,
      "tcp":<String_value>,
      "acl":<String_value>,
      "timezone":<String_value>,
      "userdefinedauditlog":<String_value>,
      "appflowexport":<String_value>,
      "builtin":<String[]_value>

}]}

get

URL: http://<NS_IP>/nitro/v1/config/auditnslogaction/name_value<String>

HTTP Method: GET

Response Payload:

{ "errorcode": 0, "message": "Done", "auditnslogaction": [ {
      "name":<String_value>,
      "serverip":<String_value>,
      "serverport":<Integer_value>,
      "loglevel":<String[]_value>,
      "dateformat":<String_value>,
      "logfacility":<String_value>,
      "tcp":<String_value>,
      "acl":<String_value>,
      "timezone":<String_value>,
      "userdefinedauditlog":<String_value>,
      "appflowexport":<String_value>,
      "builtin":<String[]_value>

}]}

count

URL: http://<NS_IP>/nitro/v1/config/auditnslogaction?count=yes

HTTP Method: GET

Response Payload:

{ "errorcode": 0, "message": "Done",auditnslogaction: [ { "__count": "#no"} ] }