Issue Fixes
1. Incorrect Logging of Request Body
Resolved an issue where response logs were incorrectly being saved in place of the request body. Logging behaviour is now accurate and consistent.
2. Sync Engine Global Exception Handling
A global exception handling flow in Sync Engine previously triggered an unintended vFlow initial reload due to differing error codes. While the root cause lies in vFlow, a backward-compatible fix has been implemented in Sync Engine to ensure seamless operation with older vFlow codebases.
3. vMonitoring Performance Optimization
The vMonitoring status update, previously triggered on every API call, has been optimized to reduce frequent interactions with Redis. This enhancement has significantly lowered CPU utilization and improved system performance.