If the category is "all", adds a custom logger for every category or the given user.
| Authorization token required | true |
| Admin Authorization token required | true |
<AddAccountLoggerRequest> ## AddAccountLoggerRequest
<id>{id} (String)</id>
<account by="{acct-selector-by} (adminName | appAdminName | id | foreignPrincipal | name | krb5Principal)">{key}</account> ## AccountSelector
<logger category="{category-name}" [level="(error | warn | info | debug | trace)"] /> ## LoggerInfo
</AddAccountLoggerRequest>
elements and attributes you can define within a
<AddAccountLoggerRequest> element:
| XPath | Required / Optional | Description |
| /id | Optional (0 or 1) | Type: {id} (String) Deprecated - use <account> instead |
| /account | Optional (0 or 1) | Type: {key} Use to select account Description for element text content:The key used to identify the account. Meaning determined by {acct-selector-by} |
| /account@by | Required (only 1) | Type: adminName | appAdminName | id | foreignPrincipal | name | krb5Principal Select the meaning of {acct-selector-key} |
| /logger | Required (only 1) | Logger category |
| /logger@category | Required (only 1) | Type: String name of the logger category |
| /logger@level | Optional (0 or 1) | Type: error | warn | info | debug | trace level of the logging. |
<AddAccountLoggerResponse> ## AddAccountLoggerResponse
(<logger category="{category-name}" [level="(error | warn | info | debug | trace)"] /> ## LoggerInfo)*
</AddAccountLoggerResponse>
elements and attributes you can define within a
<AddAccountLoggerResponse> element:
| XPath | Required / Optional | Description |
| /logger | Optional (0 or more) | Information on loggers |
| /logger@category | Required (only 1) | Type: String name of the logger category |
| /logger@level | Optional (0 or 1) | Type: error | warn | info | debug | trace level of the logging. |