Skip to content

feat: observability metrics into what is preventing auto-stop (ssh connection, browser ide, etc.) #7273

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
ericpaulsen opened this issue Apr 24, 2023 · 6 comments

Comments

@ericpaulsen
Copy link
Member

customer feedback:

when maintaining Coder and it's infrastructure costs, admins need to know why & why not a workspace is shutting down. need log evidence related to how long a workspace has been on, how long the active session has been up, etc.

@github-actions github-actions bot added the stale This issue is like stale bread. label Oct 22, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2023
@bpmct bpmct reopened this Nov 5, 2023
@github-actions github-actions bot removed the stale This issue is like stale bread. label Nov 6, 2023
@stirby

This comment was marked as off-topic.

@stirby
Copy link
Collaborator

stirby commented Mar 6, 2024

Update: fixed by: #12175. Will be available on next release.

@aslilac
Copy link
Member

aslilac commented Mar 6, 2024

well this is asking about from an admin perspective right? I think my work was kind of tangential to this

@aslilac
Copy link
Member

aslilac commented Mar 6, 2024

we could totally add an audit log when we do the activity bump though, which might be more helpful?

@stirby
Copy link
Collaborator

stirby commented Mar 6, 2024

You're totally right, comment was made hastily.

The activity bump log would be extraordinarily beneficial for admins yes.

@aslilac
Copy link
Member

aslilac commented Mar 6, 2024

The only issue is how to do it without being too noisy, as bumps happen very frequently... maybe we just need to be able to batch audit log items

@sreya sreya closed this as not planned Won't fix, can't repro, duplicate, stale Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants