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

Capture reason for build failure in coderd logs #14062

Assignees
BrunoQuaresmaDanielleMaywood
Labels
customer-requestedFeatures requested by enterprise customers. Only humans may set this.enterpriseEnterprise-license / premium functionalityobservabilityIssues related to observability (metrics, dashboards, alerts, opentelemetry)
@stirby

Description

@stirby

Administrators often have to manually identify the source of build failures by looking in each workspace's logs, monitoring dashboards for their provider, or having their users report issues internally. This makes triaging pervasive workspace problems difficult, especially across clouds.

When a build fails, we should include areason for the failure in the control plane logs, simply the returned Terraform error. Right now,I believe we only report theinitialize terraform: exit status 1.

This way admins can filter the coderd logs and set up alerts when a type of error is hit frequently enough.

cc@kylecarbs

Metadata

Metadata

Labels

customer-requestedFeatures requested by enterprise customers. Only humans may set this.enterpriseEnterprise-license / premium functionalityobservabilityIssues related to observability (metrics, dashboards, alerts, opentelemetry)

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2025 Movatter.jp