Scenarios of using trace logging

The following scenario is of using trace logging for targeted diagnostics.

Example: Two tenants, Tenant X and Tenant Y, report delays in capture activities that are being processed.

For Tenant X, activities are never completed, whereas for Tenant Y, activities are very slow.

In this case, to troubleshoot, an administrator can enable logging of the Transformation Server components for those two tenants only and set the logging for Tenant X to 'All' and Tenant Y to 'Error'.

In scenarios such as the following, you may not require trace logging:

Tenants are used solely for development, testing, or staging purposes. Logging in these environments may generate unnecessary data that does not provide long-term value.
Tenants are short-lived. They are created for temporary purposes, such as onboarding, demos, or customer trials.
Tenants have non-critical workloads. For example, a tenant used by Educational Services to showcase features. Disabling logging for such tenants can improve system performance and conserve storage resources.
Tenants with very low or infrequent activity do not need detailed logging. The overhead of storing and managing logs for such tenants may outweigh the diagnostic value.