[RFE] Show error if activity tracker extension fails to ping machine-exec in OpenShift Dev Spaces
Issue
- In OpenShift Dev Spaces, the activity tracker extension sends events to the 
/checode/bin/machine-execprocess to let it know that the current workspace is being used by the user. The process can be found in eachworkspacepod inside thenamespaceof the OpenShift Dev Spaces user.- Idle workspaces are terminated after 30 minutes by default, which is configured from 
spec.devEnvironments.secondsOfInactivityBeforeIdlingfrom theCheClusterCustom Resources (CR). - If the activity tracker extension fails to ping 
/checode/bin/machine-exec, a message is printed in the extension logs, however this is not easily noticeable from the user's perspective. 
 - Idle workspaces are terminated after 30 minutes by default, which is configured from 
 - OpenShift Dev Spaces does not indicate failed pings to machine-exec in the user interface (UI)
 
Environment
OpenShift Dev Spaces
- 3.15
 - 3.16
 - 3.17
 
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.