Skip to content
Was this article helpful?


Statistics for audit.


(click to see Operations)

Name Data Type PermissionsDescription
clearstats<String>Read-writeClear the statsistics / counters.<br>Possible values = basic, full
auditsyslogmsgsent<Double>Read-onlySyslog messages sent to the syslog server(s) over UDP.
auditsyslogmsgsentrate<Double>Read-onlyRate (/s) counter for auditsyslogmsgsent
auditsyslogmsggen<Double>Read-onlySyslog messages about to be sent to the syslog server.
auditsyslogmsggenrate<Double>Read-onlyRate (/s) counter for auditsyslogmsggen
auditsyslogmsgsenttcp<Double>Read-onlySyslog messages sent to the syslog server(s) over TCP.
auditsyslogmsgsenttcprate<Double>Read-onlyRate (/s) counter for auditsyslogmsgsenttcp
auditnsballocfail<Double>Read-onlyNAT allocation failed.
auditnsballocfailrate<Double>Read-onlyRate (/s) counter for auditnsballocfail
auditlog32errsyslogallocnsbfail<Double>Read-onlyNsb allocation failed.
auditlog32errsyslogallocnsbfailrate<Double>Read-onlyRate (/s) counter for auditlog32errsyslogallocnsbfail
auditmemallocfail<Double>Read-onlyFailures in allocation of Access Gateway context structure. When an Access Gateway session is established, the NetScaler creates an internal context structure , which identifies the user and the IP address from which the user has logged in.
auditmemallocfailrate<Double>Read-onlyRate (/s) counter for auditmemallocfail
auditportallocfail<Double>Read-onlyNumber of times the NetScaler failed to allocate a port when sending a syslog message to the syslog server(s).
auditportallocfailrate<Double>Read-onlyRate (/s) counter for auditportallocfail
auditcontextnotfound<Double>Read-onlyFailures in finding the context structure for an Access Gateway session during attempts to send session-specific audit messages. During an Access Gateway session, audit messages related to the session are queued up in the auditlog buffer for transmission to the audit log server(s). If the session is killed before the messages are sent, the context structure allocated at session creation is removed. This structure is needed for sending the queued auditlog messages. If it is not found, this counter is incremented.
auditcontextnotfoundrate<Double>Read-onlyRate (/s) counter for auditcontextnotfound
nsbchainallocfail<Double>Read-onlyNsb Chain allocation failed.
nsbchainallocfailrate<Double>Read-onlyRate (/s) counter for nsbchainallocfail
clientconnfail<Double>Read-onlyFailures in establishment of a connection between the NetScaler and the auditserver tool (the Netscalers custom logging tool).
clientconnfailrate<Double>Read-onlyRate (/s) counter for clientconnfail
flushcmdcnt<Double>Read-onlyAuditlog buffer flushes. In a multiprocessor NetScaler, both the main processor and the co-processor can generate auditlog messages and fill up the auditlog buffers. But only the primary processor can free up the buffers by sending auditlog messages to the auditlog server(s). The number of auditlog buffers is fixed. If the co-processor detects that all the auditlog buffers are full, it issues a flush command to the main processor.
flushcmdcntrate<Double>Read-onlyRate (/s) counter for flushcmdcnt
systcpconnfail<Double>Read-onlyFailures in establishment of a connection between the NetScaler and the syslog server.
systcpconnfailrate<Double>Read-onlyRate (/s) counter for systcpconnfail
logunsentlbsys<Double>Read-onlyTotal auditlog messages which are not delivered to load balanced syslog servers
logunsentlbsysrate<Double>Read-onlyRate (/s) counter for logunsentlbsys
logsdropped<Double>Read-onlyTotal number of log messages dropped by NetScaler after max hold limit is reached
logsdroppedrate<Double>Read-onlyRate (/s) counter for logsdropped
logsdroppedtxminnsbs<Double>Read-onlyTotal number of log messages dropped by NetScaler when NSBQ length is less than TX min NSBs
logsdroppedtxminnsbsrate<Double>Read-onlyRate (/s) counter for logsdroppedtxminnsbs


(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:


    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:



    Note: In such cases, make sure that the request header DOES not include the following:



Mandatory parameters are marked in red and placeholder content is marked in <green>.

get (all)

URL: http://<netscaler-ip-address>/nitro/v1/stat/audit




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

HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue> Accept:application/json


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 errorResponse Headers:


Response Payload:

{ "audit": [ {
Was this article helpful?