Observability Into Builders #233

New issue

Open

opened 2026-05-06 08:57:48 +00:00 by ryansquared · 3 comments

ryansquared commented

2026-05-06 08:57:48 +00:00

(Migrated from codeberg.org)

If a builder gets stuck, we have no way to know why it failed or how to fix it. We have no logs, no metrics, or anything.

ryansquared commented

2026-05-06 09:21:57 +00:00

(Migrated from codeberg.org)

Some thoughts on how this could work:

Client public keys get added to the builder
Builder sets up a stream encryption key (NOT AEAD, we can't verify the integrity of an unending stream)
Logs are shoved directly from the program into an encryption helper, which encrypts them to the ephemeral key
Encrypted logs and encrypted stream encryption key get uploaded... somewhere.

Some thoughts on how this could work: * Client public keys get added to the builder * Builder sets up a stream encryption key (NOT AEAD, we can't verify the integrity of an unending stream) * Logs are shoved directly from the program into an encryption helper, which encrypts them to the ephemeral key * Encrypted logs and encrypted stream encryption key get uploaded... somewhere.

anton commented

2026-05-18 18:03:59 +00:00

(Migrated from codeberg.org)

caution-bot commented

2026-07-10 20:31:33 +00:00

(Migrated from codeberg.org)

Backlog duplicate audit: #78 (store build logs in S3 and expose them via CLI/UI) is a narrower subset of this builder observability issue. Keeping this as the primary ticket for builder log/metric visibility; #78 is being closed in favor of this issue.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

public/platform#233

No description provided.

Rows
Columns