avaya:aads:keycloak:debug
This is an old revision of the document!
Change Loglevel for AADS Keycloak
To change the loglevel of AADS Keycloak Service do the following.
As root User change the following File by adding Parameter: –log-level=<root-level>
/opt/Avaya/DeviceServices/<AADS-Versions>/CAS/10.2.0.1.16/service.d/keycloak.start.sh
Restart Keycloak Service
In Case of Cluster Config all AADS Nodes need to be changed
The following Levels are available:
| Level | Description |
| FATAL | Critical failures with complete inability to serve any kind of request. |
| ERROR | A significant error or problem leading to the inability to process requests. |
| WARN | A non-critical error or problem that might not require immediate correction. |
| INFO | Keycloak lifecycle events or important information. Low frequency. |
| DEBUG | More detailed information for debugging purposes, such as database logs. Higher frequency. |
| TRACE | Most detailed debugging information. Very high frequency. |
| ALL | Special level for all log messages. |
| OFF | Special level to turn logging off entirely (not recommended). |
Example:
vi /opt/Avaya/DeviceServices/10.2.0.1.16/CAS/10.2.0.1.16/service.d/keycloak.start.sh
$INSTALL_PARENT/keycloak-22.0.4/bin/kc.sh \
start \
--proxy edge \
--hostname-path=/auth \
**----log-level=DEBUG**
..
svc keycloak restart
avaya/aads/keycloak/debug.1721969746.txt.gz · Last modified: (external edit)
