Log configuration and location in Identity Suite v15 deployed using IGA Xpress 1.0

Products

• CA Identity Suite

Issue/Introduction

Where are the logging configurations and the log files in Version 15?

Resolution

ADJUSTING LOGGING LEVELS:

The logging configuration for Identity Suite v15 are configured in the IGA Xpress gui under the Services tab, Application Service, Logging tab.   
Unchecked, the logging is at the default INFO level.    To change the logging check the "Logging" box and adjust as required. 

For example, Identity Manager with DEBUG logging set to Rotate based on size and retain 20 backup logs:

 

Logging levels can also be viewed and adjusted directly in the yaml files. 

/opt/brcm/iga/conf/idm/idm.yaml

logging:
  log_level: DEBUG
  log_rotation: Size
  max_log_rotations: 20
  max_log_size: 100

 

 

LOG FILE LOCATIONS:

All logs are found under the following folder in a sub folder for each service.

/opt/brcm/iga/logs/

 

/xpress      =    Deployment, IGA Xpress install logs
/install/       =    installation logs
/idm/          =    Identity Manager  
/idg/           =    Identity Governance
/idp/           =    Identity Portal
/imps/        =    Provisioning Server
/imcs/        =    Connector Server
/impr/         =    Provisioning Router
/impd/        =    Provisioning Directory
/ustore/      =    User Store
/urouter/    =    User Store Router
/uproxy/     =    User Store Proxy
/balancer/  =    Balancer 
/suite/        =    Suite

DATASOURCE DEBUG / TEST CONNECTION DEBUG: 

When pressing "Test Connection" if need more information about the message error you can add more DEBUG information in the file /opt/brcm/iga/inst/xpress/log.yaml. (Please, backup this file before do any change!)

1. Backup your existing log.yaml file from xpress
2. Edit using vi or other editor and change the classes

Example of all clases in DEBUG:

version: 1
disable_existing_loggers: false
formatters:
  simple:
    format: '%(asctime)s | %(name)s | %(levelname)s | %(message)s'
  other:
    format: '%(asctime)s | %(levelname)s | %(message)s'
handlers:
  console:
    class: logging.StreamHandler
    level: DEBUG
    formatter: simple
    stream: ext://sys.stdout
  file:
    class: logging.handlers.RotatingFileHandler
    level: DEBUG
    formatter: simple
    filename: /opt/brcm/iga/logs/xpress/xpress.log
    maxBytes: 1000000
    backupCount: 2
loggers:
  root:
    level: DEBUG
    handlers: [console, file]
  uvicorn.error:
    level: DEBUG
    handlers: [console, file]
  uvicorn.access:
    level: DEBUG
    handlers: [console, file]

3. igactrl restat xpress
4. monitor the log file /opt/brcm/iga/logs/xpress/xpress.log. You can use command:

tail -f /opt/brcm/iga/logs/xpress/xpress.log to monitor the log and to stop issue Ctrl+C any time 

5. Go to IGA xpress Web Console under Services Component / Datasources and press the "Test Connection" button that you will see detailed information about the failure in the xpress.log

6. After you end debugging, rollback the changes you did in the file log.yaml, restart xpress with igactl restart xpress to prevent you log grows a lot.

Another way to test the connection is using the testdb command line:

1. Go to/opt/brcm/iga/inst/suite/bin$
2. Issue the command: (This is a sample, please adapt the dbhost, portnumber, databasename, dbuser and dbpassword to your environment values)

./testdb "jdbc:sqlserver://;serverName=dbhost;portNumber=1433;selectMethod=cursor;databaseName=idmdb;encrypt=false" dbuser dbpassword
{ "status":true,"message":"The Connection is Successful"}