Oracle Cloud Infrastructure Documentation

Managing Logging Levels

To help with troubleshooting, you can change the logging level of some services without restarting the service.

With the ability to raise the logging level during runtime, you don’t need to log every detail by default. As a result, you can decrease the overall default logging of services, reducing the amount of storage required. The support for logging levels varies by service.

Viewing Logging Levels

  • To view services that support dynamic logging, use the getServicesSupportingLogLevelOverrides command. 

    PCA-ADMIN> getServicesSupportingLogLevelOverrides
Command: getServicesSupportingLogLevelOverrides
Status: Success
Time: 2025-07-24 00:33:32,328 UTC
Data:
  admin
  iam
  api
  limit
PCA-ADMIN>

  • To view enabled logging levels for a service, use the getSupportedLogLevelOverrides serviceName=service command. If logging levels aren't supported for a service, you get an error message. 

    PCA-ADMIN> getSupportedLogLevelOverrides serviceName=admin
Command: getSupportedLogLevelOverrides serviceName=admin
Status: Success
Time: 2025-08-04 23:28:13,889 UTC
Data: 
  Logger Name    Supported Logging Levels                           
  -----------    ------------------------                           
  AdminService   SEVERE,WARNING,INFO,FINE,FINER,FINEST   
  AUDIT          SEVERE,WARNING,INFO,FINE,FINER,FINEST    
PCA-ADMIN> getSupportedLogLevelOverrides serviceName=iam
Command: getSupportedLogLevelOverrides serviceName=iam
Status: Success
Time: 2025-08-04 23:27:58,208 UTC
Data: 
  Logger Name   Supported Logging Levels   
  -----------   ------------------------   
  root          DEBUG,INFO,WARNING,ERROR   
  pcaiam        DEBUG,INFO,WARNING,ERROR  
PCA-ADMIN> getSupportedLogLevelOverrides serviceName=api
Command: getSupportedLogLevelOverrides serviceName=api
Status: Success
Time: 2025-08-04 23:28:03,967 UTC
Data: 
  Logger Name   Supported Logging Levels            
  -----------   ------------------------            
  root          DEBUG,INFO,WARNING,ERROR,CRITICAL   
  pcaapi        DEBUG,INFO,WARNING,ERROR,CRITICAL   
  audit         DEBUG,INFO,WARNING,ERROR,CRITICAL

  • To view the current log level of the services, use the getLogLevelOverrides command.

  • PCA-ADMIN> getlogleveloverrides                                                             
Command: getlogleveloverrides
Status: Success
Time: 2025-08-22 06:17:35,817 UTC
Data: 
  Service Name   Logger Name    Logger Level   
  ------------   -----------    ------------   
  admin          adminService   SEVERE         
  admin          audit          SEVERE         
  iam            root           DEBUG              
  iam            pcaiam         DEBUG       
  api            NOT SET        NOT SET        
  limit          NOT SET        NOT SET

Changing Logging Levels

  • To set a new log level for a service, use the setLogLevelOverride service=service loggerName=string level=log_level command.

    Note

    Run the getSupportedLogLevelOverrides serviceName=service to find the Logger Name and the available logging levels for a service.
    PCA-ADMIN> setlogleveloverride serviceName=iam loggername=pcaiam                    
Command: setlogleveloverride serviceName=iam loggername=pcaiam loggerlevel=ERROR
Status: Success
Time: 2025-08-22 06:37:24,095 UTC
Data: 
  status = PASS
  message = LLO - successfully set log level override

  • To remove a logging level for a service, use the unsetLogLevelOverride service=service loggerName=string level=log_level command.

    PCA-ADMIN> unsetLogLevelOverride serviceName=admin loggerName=AdminService
Command: unsetLogLevelOverride serviceName=admin loggerName=AdminService
Status: Success
Time: 2025-02-13 22:29:47,886 UTC
Data: 
  status = PASS
  message = LLO - successfully unset log level override