JDBC Provisioning Rule - Logs not working, Not showing in ccg.log

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

I am working to assist another developer with a JDBC Provisioning Rule and they were stating that the log statements that they added were not showing up in the ccg.log file.

I provided them with the latest log config file for the API-based setup and asked them to try it again. They did, and still no dice.

Do We need to try it the other way, using the setup on the VA as referenced here: CCG Enable Debug Log by Connector - Compass

I can see the rule being called and completed, but no configured debug logs from the rule are visible. I would rather not up the logs to warning or error just to get them to print.

Here is the body used to set the log level:

{
    "durationMinutes": 120,
    "rootLevel": "WARN",
    "logLevels": {
        "sailpoint.connector.JDBCConnector": "DEBUG"
    }
}

For these rules, so we need to update the log4j file on the VA directly? Or is there something that we are missing?

Similar issues have been mentioned in other posts with no solutions:

This old ticket seems to reference the previous way, using log4j.properties, but the links have all been updated to point to the API Method:

2

Hi @gmilunich I modified log4j file on VA, but although I put in debug mode, only logs with log.warn() worked. I could not log log.debug() calls. But as this was sufficient for me, I followeed on with debug in log4j config and log.warn() in rule code.

3

I saw your solution and have provided it to the developer to try so we can figure out what the issue is, however I think this may be a larger issue that should be looked at, as using WARN for DEBUG/INFO is not a good practice overall in the long run.

2 Likes
4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.