Skip to content
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

Add agent script timings #14630

Closed
dannykopping opened this issue Sep 10, 2024 · 0 comments · Fixed by #14713 · May be fixed by grepdemos/coder#1
Closed

Add agent script timings #14630

dannykopping opened this issue Sep 10, 2024 · 0 comments · Fixed by #14713 · May be fixed by grepdemos/coder#1
Assignees
Labels
need-backend Issues that need backend work observability Issues related to observability (metrics, dashboards, alerts, opentelemetry)

Comments

@dannykopping
Copy link
Contributor

Similar to #14274, we require further insight into how long each script takes to execute in the agent.

Scripts can run:

  • on startup
    • can optionally have a flag (start_blocks_login) which prevents users logging in until script exits
  • on stop
  • on a cron schedule

We ultimately want to be able to indicate how long a workspace took to become "ready" from the time the build was initiated all the way to the agent scripts with blocking behaviour exiting. Scripts which do not block (i.e. run on startup without start_blocks_login, on stop, or on a cron schedule) should also be tracked and have some indication that they are non-blocking.

We need to track when each script started, exited, and with what status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need-backend Issues that need backend work observability Issues related to observability (metrics, dashboards, alerts, opentelemetry)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants