Include Streaming HTTP Headers into the Health Check status

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to Solve

Multiple customers have reported poor latency for code creation, with results taking 5-10 seconds to appear. Analysis revealed that the required HTTP headers for streaming are not passing through some customers' proxies, leading to degraded performance. Currently, there's no easy way for administrators or end-users to identify and address this issue.

Proposed Solution

Implement a line check between the SM instance and the cloud connector to verify that all necessary headers for streaming are successfully transmitted and a streamed response is received. This check should be integrated into the health check system and potentially the IDE interface.

Objectives

1. Create a mechanism to detect if streaming HTTP headers are properly transmitted.
2. Integrate this check into the existing health check system.
3. Provide clear feedback to administrators through the health check interface.
4. Offer guidance (e.g., link to documentation) on how to resolve HTTP header setup issues.

Expected Outcome

• Administrators can quickly identify and address streaming header issues.
• End-users are informed when the system is not operating optimally.

Additional Notes

• Documentation should be updated to include information on proper HTTP header setup for optimal performance.
• Consider implementing this feature in a way that allows for easy expansion to check for other potential network/proxy issues in the future.