## Problem Statement Ensure that errors are handled gracefully and that logs are available for troubleshooting and debugging purposes. This epic contains all issues related to showing users useful errors and backend logging useful for finding and debugging bugs. ## Exit Criteria - Errors are handled in a clear and understandable way, with detailed error messages and appropriate error codes. Logs are generated for all actions and events that occur within workspaces, and are accessible to users through a centralized logging system. ## Errors <details><summary>diagram that helped me to think about all the systems interactions</summary>  </details> ### User-initiated errors: | Error | current state | experiment solution (if different) | viable solution (if different) | |---|---|---|---| | User provides non-existing devfile | :white_check_mark: error message on workspace creation | | | | [Invalid devfile](https://gitlab.com/gitlab-org/gitlab/-/issues/409069) | GraphQL endpoint returns 500 | error message on workspace creation | | | [User provides unsupported but valid devfile](https://gitlab.com/gitlab-org/gitlab/-/issues/409073) | GraphQL returns 500 | error message on workspace creation | | | No agents available | :white_check_mark: error message on workspace creation | | | | [Workspace error (e.g. invalid container)](https://gitlab.com/gitlab-org/gitlab/-/issues/409074) | workspace overview shows "Starting" | workspace overview shows "error" | workspace overview shows details about why the pod failed to initialize | ### Admin-initiated errors: | Error | current state | experiment solution (if different) | viable solution (if different) | |---|---|---|---| | [Invalid agent configuration YAML file](https://gitlab.com/gitlab-org/gitlab/-/issues/409076) |`kas` and `agentk` log an error | ? | the agent details screen (`http://gdk.test:3000/gitlab-org/security/gitlab-test/-/cluster_agents/my-agent?tab=activity`) shows configuration issue | ### Agent-related errors: | Error | current state | experiment solution (if different) | viable solution (if different) | |---|---|---|---| | [Rails API is unresponsive (e.g. outage)](https://gitlab.com/gitlab-org/gitlab/-/issues/409080) | no errors logged | log error in the agent | | | :warning: [Kubernetes API server is unresponsive](https://gitlab.com/gitlab-org/gitlab/-/issues/409083) | agentk logs error | ? | Show the user that the agent is not healthy? | | Workspace failure | I assume it's the same as workspace error (in user-initiated section) | | | | Bug in Rails reconciliation loop | :question: | [Logged in production logs](https://gitlab.com/gitlab-org/gitlab/-/issues/409066) | | | Bug in Rails workspace create logic | :question: | [Logged in production logs](https://gitlab.com/gitlab-org/gitlab/-/issues/409066) | | ### Auth Proxy: Investigation still needed https://gitlab.com/gitlab-org/gitlab/-/issues/409084+ ## Tasks - [ ] Ensure that the [unfinished task around enhanced frontend error handling](https://gitlab.com/gitlab-org/gitlab/-/issues/407723#details) is captured in an issue. See [the question about this below](https://gitlab.com/groups/gitlab-org/-/epics/10461#note_1373441638). - [ ] There are several TODO comments in the Remote Development codebase referencing this epic (search `https://gitlab.com/groups/gitlab-org/-/epics/10461`). Ensure they are all resolved or else have follow-up issues before closing this epic.