Error tracking and logging #132

Closed
opened 2026-03-31 18:21:50 +00:00 by anton · 3 comments
anton commented 2026-03-31 18:21:50 +00:00 (Migrated from codeberg.org)
No description provided.
anton commented 2026-04-06 16:57:21 +00:00 (Migrated from codeberg.org)

We log errors, but we should save them in an immutable storage.

We log errors, but we should save them in an immutable storage.
ryansquared commented 2026-06-26 23:58:04 +00:00 (Migrated from codeberg.org)

Logging is handled by systemdize.

We brought up Sentry yesterday in conversation. That seems like a good error tracking solution, but we'd have to restructure the application to make good use of it.

Logging is handled by systemdize. We brought up Sentry yesterday in conversation. That seems like a good error tracking solution, but we'd have to restructure the application to make good use of it.
caution-bot commented 2026-07-10 20:20:43 +00:00 (Migrated from codeberg.org)

Closed in favor of #377, which expands this into a GA-scoped Sentry integration issue with backend/frontend setup, dev/prod Sentry environment instructions, privacy requirements, and acceptance criteria.

Closed in favor of #377, which expands this into a GA-scoped Sentry integration issue with backend/frontend setup, dev/prod Sentry environment instructions, privacy requirements, and acceptance criteria.
Sign in to join this conversation.
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#132
No description provided.