I was recently asked a question about the Epic EMP connector that I could not answer. Even after reviewing the connector documentation I still can not answer the question. The question was what exactly does Enable Logging in the EMP config actually do?
No where on the connector or the documentation really explains what this is for or what it’s intended use case is. When should it be enabled why would you enable it.
The reason this question came up was because our Epic team discovered that in our Epic Test that SailPoint was consuming a lot of storage. We were advised to disable logging. In order to better advise the Epic team I would like to gain an understanding what exactly this does. Epic team is pushing really hard to disable this in Prod which of course makes me nervous because I do not know what exactly it does.
I went back through SailPoint’s documentation around connector logging and VA/CCG logs, and based on what they describe, here’s how I understand the EMP “Enable Logging” setting.
What does “Enable Logging” actually do?
It causes the Epic connector to generate verbose connector-operation logs on the VA, which you can review in ccg.log. SailPoint’s connector logging mechanism uses logging levels/classes (Epic’s class is openconnector.connector.EPICConnector) and writes the output to ccg.log.
What’s the intended use?
It’s intended for debugging/troubleshooting because SailPoint defines DEBUG as “very verbose… used for development and debugging” (and TRACE as “most verbose”).
When should it be enabled?
Enable it only when you’re actively troubleshooting an Epic connector issue, and time-box it (SailPoint’s log configuration uses durationMinutes = “number of minutes logging should remain enabled”).
Why SailPoint consuming a lot of storage?
DEBUG/TRACE logging produces a large volume of output on the VA disk. SailPoint explicitly notes that enabling standard debug logging “is not sustainable due to the amount of information it delivers,” and those connector logs are stored in ccg.log on the VA.
