-
-
-
-
audit_log
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
audit_log
Configuration for Audit log messages resource.
Properties
(click to see Operations )
Name | Data Type | Permissions | Description |
---|---|---|---|
id |
|
Read-write | Id is system generated key for all the audit log entries. |
command |
|
Read-write | Command given for this action. |
status |
|
Read-only | Status of this action whether accepted/rejected by system. |
port |
|
Read-only | Client port from where operation specified for this entry was performed. |
message |
|
Read-only | Message for this action. |
username |
|
Read-only | User Name, who performed operation specified for this entry. |
client_type |
|
Read-only | Client Type. |
audittime |
|
Read-only | Action Time on which operation specified for this entry was started. |
ip_address |
|
Read-only | Client IP Address from where operation specified for this entry was performed. |
resource_name |
|
Read-only | Resource Name on which operation specified for this entry was performed. |
operation |
|
Read-only | Operation Type that is performed. |
resource_type |
|
Read-only | Resource Type on which operation specified for this entry was performed . |
Operations
(click to see Properties )
- GET (ALL)
- GET
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
The following parameters can be used in the nitro request : onerror <String_value>
Use this parameter to set the onerror status for nitro request. Applicable only for bulk requests.
Default value: EXIT
Possible values = EXIT, CONTINUE
get (all)
URL: https://<MGMT-IP>/nitro/v2/config/audit_log Query-parameters:
filter https://<MGMT-IP>/nitro/v2/config/audit_log ?filter=property-name1:property-value1,property-name2:property-value2 Use this query-parameter to get the filtered set of audit_log resources configured on the system. You can set a filter on any property of the resource.
pagesize=#no;pageno=#no https://<MGMT-IP>/nitro/v2/config/audit_log ?pagesize=#no;pageno=#no Use this query-parameter to get the audit_log resources in chunks.
count https://<MGMT-IP>/nitro/v2/config/audit_log ?count=yes Use this query-parameter to get the count of audit_log resources.
HTTPS Method: GET
Request Headers: Accept: application/json
X-NITRO-USER:username_value<String>
X-NITRO-PASS:password_value<String>
or
Cookie:NITRO_AUTH_TOKEN=token_value<String>
Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error
Response Headers:
Content-Type:application/json
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "audit_log":[{
"status":<String_value>,
"port":<Integer_value>,
"message":<String_value>,
"username":<String_value>,
"client_type":<String_value>,
"tenant_id":<String_value>,
"audittime":<Integer_value>,
"id":<String_value>,
"ip_address":<String_value>,
"resource_name":<String_value>,
"operation":<String_value>,
"command":<String_value>,
"resource_type":<String_value>}]}
<!--NeedCopy-->
get
URL: https://<MGMT-IP>/nitro/v2/config/audit_log/id_value<String> HTTPS Method: GET
Request Headers: Accept: application/json
X-NITRO-USER:username_value<String>
X-NITRO-PASS:password_value<String>
or
Cookie:NITRO_AUTH_TOKEN=token_value<String>
Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error
Response Headers:
Content-Type:application/json
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "audit_log":[{
"status":<String_value>,
"port":<Integer_value>,
"message":<String_value>,
"username":<String_value>,
"client_type":<String_value>,
"tenant_id":<String_value>,
"audittime":<Integer_value>,
"id":<String_value>,
"ip_address":<String_value>,
"resource_name":<String_value>,
"operation":<String_value>,
"command":<String_value>,
"resource_type":<String_value>}]}
<!--NeedCopy-->
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.