Skip to content

Please show workspace instances and attributions in the admin panel #16556

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.

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

Closed
jankeromnes opened this issue Feb 24, 2023 · 1 comment
Closed
Labels
meta: stale This issue/PR is stale and will be closed soon support team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code

Comments

@jankeromnes
Copy link
Contributor

jankeromnes commented Feb 24, 2023

Is your feature request related to a problem? Please describe

A frequent use case that comes up when helping customers is knowing: what instances ran for a given workspace, and how long did they last.

For example, in the context of #15304 it's helpful to know that, for a given workspace, there were 5 instances, but 2 instances ran for 24h straight (i.e. the customer was affected by the timeout bug twice, which tells us how many credits they should get back).

Describe the behaviour you'd like

In the Workspace page of the Admin panel, please show a list of:

  • Instance ID
  • When started/stopped
  • Duration or credits spent
  • Usage attribution (e.g. link to org or user)

Describe alternatives you've considered

For now, we tend to go spelunking into the DB in order to piece together this information manually. But, this requires in-depth knowledge of the DB and significant time & manual effort.

Additional context

@jankeromnes jankeromnes added type: improvement Improves an existing feature or existing code team: webapp Issue belongs to the WebApp team labels Feb 24, 2023
@jankeromnes jankeromnes changed the title Please show a workspace's instances in the admin panel Please show workspace instances and attributions in the admin panel Mar 6, 2023
@stale
Copy link

stale bot commented Jun 10, 2023

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 Jun 10, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
@github-project-automation github-project-automation bot moved this to In Validation in 🍎 WebApp Team May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon support team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code
Projects
Status: In Validation
Development

No branches or pull requests

1 participant