Title
Suppress Unnecessary Logs from Drift Utility API Jobs
Description
As a Drift Utility team,
we want to suppress unnecessary and low-value logs generated by Utility API jobs that operate through the Drift Utility UI,
so that application logs are cleaner, easier to analyze, and focused on actionable information, improving observability, troubleshooting efficiency, and reducing log noise and storage overhead.
Acceptance Criteria
Log Reduction
Non-essential logs (e.g., repetitive info logs, debug statements, verbose request/response logs) are suppressed for Utility API jobs.
Only meaningful logs (errors, warnings, and important business events) are retained.
Log Level Control
Utility jobs respect configured log levels (e.g., INFO, WARN, ERROR).
DEBUG-level logs are disabled in non-development environments.
No Functional Impact
Suppressing logs does not impact the execution, performance, or output of Utility API jobs.
All existing job flows continue to function as expected.
Error & Audit Visibility
Critical error logs and audit-relevant logs remain available and unchanged.
Any job failure must still generate clear and actionable error logs.
Consistency Across Jobs
Log suppression is applied consistently across all Drift Utility jobs invoked via the Utility UI.
Validation
Logs are verified in lower environments (e.g., DEV/QA) to confirm reduction of unnecessary entries.
No important operational or troubleshooting logs are missing after the change.