Skip to content

Triage: crash reporting / observability baseline #52

Description

@ComfyChloe

Part of the ARC-OSC workboard triage track.

What's needed

Pick a crash-reporting / observability approach for the Electron client: local crash logs, a lightweight reporter, or a hosted sink.

Scope

  • Decide crash capture mechanism (main + renderer)
  • Decide where logs land (local file, optional upload)
  • Define the minimal set of health/heartbeat signals worth recording
  • Write the decision down before implementing

Acceptance criteria

  • A written triage decision exists for crash capture and log destination
  • Follow-up implementation issue(s) created from the decision

Out of scope: implementing the reporter itself (separate issue after triage).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority: LowCan wait before others with high priorityStatus: Needs TriageNeeds review to determine priority and ownership

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions