Problem: Logs related to configuration and system behavior are currently fragmented across multiple locations, making troubleshooting slow and inefficient. There is no clear centralized view or consistent process to identify high-impact issues, and important configuration errors are often buried as generic warnings.

Key Gaps:
No single, centralized location for all relevant logs
Configuration-related errors are hard to discover and correlate
Log severity levels are not granular enough, causing critical issues to appear as low-priority warnings
Lack of guidance on whether customers should rely on platform logging or develop internal processes

Requested Improvements
Centralized Log Access
Provide a single, unified location or dashboard for:
Configuration errors
System and integration-related logs
Platform warnings and failures
Improved Log Severity Levels
Introduce clearer log levels (e.g., Critical, Error, Warning, Info)
Ensure high-impact configuration issues are flagged as errors or critical, not just warnings
Configuration Error Visibility
Surface configuration errors proactively (e.g., alerts or highlights) rather than requiring manual log inspection.
Best Practices / Guidance
Clarify whether the expectation is:
Platform-provided centralized logging, or
Customers building internal aggregation and alerting processes
Provide documentation or recommendations accordingly.