Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add agent script timings #14630

Closed
grepdemos/coder
#1
Assignees
DanielleMaywood
Labels
need-backendIssues that need backend workobservabilityIssues related to observability (metrics, dashboards, alerts, opentelemetry)
@dannykopping

Description

@dannykopping

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 withoutstart_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.

Metadata

Metadata

Labels

need-backendIssues that need backend workobservabilityIssues related to observability (metrics, dashboards, alerts, opentelemetry)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2025 Movatter.jp