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

[gmilunich (Geoff Milunich)]

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:

JDBC Connector Troubleshooting Data Truncation

Hello! I am trying to troubleshoot a JDBC connector that is invoking a single SPROC for both CREATE and MODIFY operations (only two we’re focused on at the moment). I’ve pasted both the SPROC and the Java for reference. I keep receiving [“java.sql.DataTruncation: Data truncation”] for the sync attributes operation. I’ve turned on ccg debugging for the VAs, and noticed there was extra whitespace in the attribute values from the result for the provisioning plan, so I added a trim(); while that…

ToUpperCase error in JDBC connector

Hi Ousmane, This is the transform: { "id": "2819b94d-c807-4f23-9cd7-494265f77a1b", "name": "iSeries CUDPDS SubstringUpper Transform", "type": "upper", "attributes": { "input": { "attributes": { "values": [ { "type": "substring", "attributes": { "begin": 0, "end": 28, "input": { …

JDBC Connector log.info() not appearing on ccg.log

Hi! I am working with a JDBC connector provisioning rule, but I am not able to log to ccg.log. I added following lines according to document CCG Enable Debug Log by Connector - Compass [image] I think log changed to debug mode because I can see lines from JDBC connector, but not my log.info lines. I tried a very basic rule, only to make log print some variables to ccg.log: [image]

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:

What is the correct way of debugging connector rules

Hi, We are trying to write a before rule for web service connector. where we have written initial code and code does not through any error but it does not solve the purpose of writing rule as well. So in order to proceed further, We need to check the logs. Can someone help where does the logs from rules gets printed and do we need sailpoint support for checking these logs?

[jsosa (Julian Sosa)]

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.

[gmilunich (Geoff Milunich)]

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.