openclaw - 💡(How to fix) Fix Connection-level fields on health (rttMs, lastHeartbeatAt, connected) [1 participants]

TL;DR

Adding connection-level fields to the existing health RPC or creating a separate gateway.ping endpoint can provide the necessary information for a live gateway reachability indicator.

Guidance

• Consider adding connected, rttMs, and lastHeartbeatAt fields to the existing health RPC response to provide connection-level information.
• Alternatively, create a separate gateway.ping endpoint to return these fields, keeping the health endpoint focused on service-level summaries.
• Evaluate the trade-offs between modifying the existing endpoint versus introducing a new one, considering factors like backwards compatibility and UI polling cadence.
• Test any proposed changes against a branch to ensure the new fields meet the requirements for the live gateway reachability indicator.

Notes

The best approach depends on the specific requirements and constraints of the system, including the potential impact on existing users of the health endpoint and the desired polling frequency for the UI indicator.

Recommendation

Apply workaround by adding the necessary fields to the existing health RPC, as this seems to be the most straightforward approach to provide the required information without introducing additional complexity.