Enhancement: Enable Debug Logging Process Changed!

Description

We are delighted to inform you about the new process for enabling connector logs for ISC. This update is part of our initiative to standardize the method of configuring logging levels per connector, making the process more streamlined!

With the recent enhancement to the logging process, customers can now enable logging exclusively via ISC Rest APIs.

What is the problem ?

Enabling debug logging offers insight into all the Virtual Appliances (VAs) within the cluster, The purpose of the log is to serve as a red flag when something is broken. It enables the quick and effective detection of bugs and vulnerabilities.

While this capability is valuable during troubleshooting of issues related to source connectors., excessive logging can deplete resources, occupy excessive space, and potentially impede the performance of connector.

What is the Solution

Earlier methods for enabling logging in Identity Security Cloud by CCG Enable debug logs by connector, which involves updating the Log4j or Lo4j2 property file with logging classes of the connector to enable detailed logs about the operations the connector is performing, will cease to exist.

Moving forward, the logging functionality will be exclusively configurable through ISC Rest API!

Who is affected?

All ISC customers.

Important Dates

Enable Debug Logging for connector via Rest API is Live Now!

Customer Communications

To learn more and ask questions please visit the Developer Community.

Note: To enable logs via CCG, Customers can collaborate with their Customer Success Manager (CSM) to enable them for a specific duration.