feat(admin-ui): surface error/warning logs in production for environment diagnostics (#2811)#2876
feat(admin-ui): surface error/warning logs in production for environment diagnostics (#2811)#2876faisalsiddique4400 wants to merge 3 commits into
Conversation
Signed-off-by: faisalsiddique4400 <faisalsiddique10886@gmail.com>
…ent diagnostics (#2811) Signed-off-by: faisalsiddique4400 <faisalsiddique10886@gmail.com>
Signed-off-by: faisalsiddique4400 <faisalsiddique10886@gmail.com>
|
Warning Review limit reached
More reviews will be available in 25 minutes and 4 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (102)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|



feat(admin-ui): surface error/warning logs in production for environment diagnostics (#2811)
Summary
This PR introduces a unified logging strategy that surfaces important warnings and errors in production environments while preserving development-only diagnostic logging behavior.
Previously, Admin UI logging relied on
devLogger, which is disabled in production builds. As a result, configuration issues, initialization failures, and environment-specific problems could become effectively invisible to administrators and support teams operating deployed Flex installations.This update introduces a structured logging approach that separates development diagnostics from operational warnings and errors, improving observability without exposing sensitive information.
Fix Summary
devprodbothVerification
passes successfully.
🔗 Ticket
Closes: #2811