Table of Contents

Trace file lifecycle

The statuses a trace file moves through, from the profiler upload to the analyst's archive.

stateDiagram-v2
  state "Ready" as s_ready
  state "Assigned" as s_assigned
  state "Downloaded" as s_downloaded
  state "Started" as s_started
  state "Incomplete" as s_incomplete
  state "Analyzed" as s_analyzed
  state "Fixed" as s_fixed
  state "PRSubmitted" as s_pr_submitted
  state "Deployed" as s_deployed
  state "Resolved" as s_resolved
  state "ResolvedDuplicate" as s_resolved_duplicate
  state "Closed" as s_closed
  state "ClosedDuplicate" as s_closed_duplicate
  [*] --> s_ready: Created by the profiler upload
  s_ready --> s_assigned: Assigned in the Admin UI
  s_ready --> s_closed_duplicate: Duplicate detected
  s_assigned --> s_downloaded: collect-sync downloads the artifact
  s_downloaded --> s_started: Analyst starts analysis
  s_started --> s_incomplete: Analysis paused
  s_incomplete --> s_started: A new analyst resumes
  s_started --> s_analyzed: Root cause recorded
  s_analyzed --> s_incomplete: More data needed
  s_analyzed --> s_fixed: Fix prepared
  s_analyzed --> s_resolved_duplicate: Duplicate of another trace
  s_fixed --> s_pr_submitted: Fix submitted as a pull request
  s_pr_submitted --> s_deployed: Customer deploys the fix
  s_deployed --> s_resolved: Regression verification passes
  s_resolved --> s_closed: collect-sync archives the artifact
  s_resolved_duplicate --> s_closed_duplicate: collect-sync archives the artifact

The duplicate transitions are derived from the status table in the website README; the original diagram omits them.

Back to all flows

This diagram is generated from architecture/model.yaml. Edit the model, not this page.