Skip to content

Epic: Establish Workspace Success Rate (IDE) #11910

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
4 of 43 tasks
akosyakov opened this issue Aug 5, 2022 · 2 comments
Closed
4 of 43 tasks

Epic: Establish Workspace Success Rate (IDE) #11910

akosyakov opened this issue Aug 5, 2022 · 2 comments
Labels
aspect: reliability meta: stale This issue/PR is stale and will be closed soon operations: observability This issue relates to the observability of Gitpod (metrics, logs, traces) team: IDE type: epic

Comments

@akosyakov
Copy link
Member

akosyakov commented Aug 5, 2022 •
edited
Loading

Context

IDE team should establish a workspace success rate according to internal RFC

Value

Improve visibility in reliability issues for users trying access the workspace using different IDE interfaces.

Acceptance Criteria

  • All SLIs are defined and documented
  • All SLOs are defined and overview available in one place
  • All alerts on SLOs are created
  • Grafana dashboards are available for IDE clients and proxies

Plan

Engineering

SLIs/SLOs

Connections errors mean any error to IDE services from any protocol (http, web-socket, Gitpod API, IDE backends, etc) as a ratio per a client session or a throughput in proxies.
@akosyakov akosyakov added operations: observability This issue relates to the observability of Gitpod (metrics, logs, traces) team: IDE type: epic aspect: reliability labels Aug 5, 2022
@akosyakov akosyakov changed the title Epic: Workspace Success Rate (IDE) Epic: Establish Workspace Success Rate (IDE) Aug 5, 2022
@akosyakov akosyakov moved this to In Progress in 🚀 IDE Team Aug 5, 2022
This was referenced Aug 5, 2022
Merged
Closed
@stale
Copy link

stale bot commented Nov 9, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Nov 9, 2022
@andreafalzetti
Copy link
Contributor

Closing as we now prefer improving observability ad-hoc where we need it's important

Repository owner moved this from In Progress to Done in 🚀 IDE Team Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
aspect: reliability meta: stale This issue/PR is stale and will be closed soon operations: observability This issue relates to the observability of Gitpod (metrics, logs, traces) team: IDE type: epic
Projects
🚀 IDE Team
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@andreafalzetti @akosyakov