Download full document:

auditmessageaction

Configuration for message action resource.

Properties

(click to see Operations)

Name	Data Type	Permissions	Description
name	<String>	Read-write	Name of the audit message 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 message 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 message action? or ?my message action?).<br>Minimum length = 1
loglevel	<String>	Read-write	Audit log level, which specifies the severity level of the log message being generated.. The following loglevels are valid: * 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.<br>Possible values = EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, NOTICE, INFORMATIONAL, DEBUG
stringbuilderexpr	<String>	Read-write	Default-syntax expression that defines the format and content of the log message.
logtonewnslog	<String>	Read-write	Send the message to the new nslog.<br>Possible values = YES, NO
bypasssafetycheck	<String>	Read-write	Bypass the safety check and allow unsafe expressions.<br>Default value: NO<br>Possible values = YES, NO
loglevel1	<String>	Read-only	.<br>Possible values = ALL, EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, NOTICE, INFORMATIONAL, DEBUG, NONE
hits	<Double>	Read-only	The number of times the action has been taken.
undefhits	<Double>	Read-only	The number of times the action resulted in UNDEF.
referencecount	<Double>	Read-only	The number of references to the action.
__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",
"auditmessageaction":{
      "name":<String_value>,
      "loglevel":<String_value>,
      "stringbuilderexpr":<String_value>,
      "logtonewnslog":<String_value>,
      "bypasssafetycheck":<String_value>,
}}

Response Payload:

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

delete

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

Query-parameters:

warning

http://<NS_IP>/nitro/v1/config/auditmessageaction/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",
"auditmessageaction":{
      "name":<String_value>,
      "loglevel":<String_value>,
      "stringbuilderexpr":<String_value>,
      "logtonewnslog":<String_value>,
      "bypasssafetycheck":<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",
"auditmessageaction":{
      "name":<String_value>,
      "logtonewnslog":true,
      "bypasssafetycheck":true,
}}

Response Payload:

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

get (all)

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

Query-parameters:

filter

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

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

view

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

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

pagesize=#no;pageno=#no

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

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

warning

http://<NS_IP>/nitro/v1/config/auditmessageaction?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>, "auditmessageaction": [ {
      "name":<String_value>,
      "loglevel":<String_value>,
      "loglevel1":<String_value>,
      "stringbuilderexpr":<String_value>,
      "logtonewnslog":<String_value>,
      "bypasssafetycheck":<String_value>,
      "hits":<Double_value>,
      "undefhits":<Double_value>,
      "referencecount":<Double_value>

}]}

get

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

HTTP Method: GET

Response Payload:

{ "errorcode": 0, "message": "Done", "auditmessageaction": [ {
      "name":<String_value>,
      "loglevel":<String_value>,
      "loglevel1":<String_value>,
      "stringbuilderexpr":<String_value>,
      "logtonewnslog":<String_value>,
      "bypasssafetycheck":<String_value>,
      "hits":<Double_value>,
      "undefhits":<Double_value>,
      "referencecount":<Double_value>

}]}

count

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

HTTP Method: GET

Response Payload:

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