Table of Contents

Profiling session lifecycle

How a threshold breach in a customer application becomes a trace file, an analysis, and a verified fix.

sequenceDiagram
  autonumber
  participant p_customer_app as Customer Application
  participant p_profiler as Reignite Profiler
  participant p_api as Reignite Control Plane
  participant p_artifact_store as Artifact Storage
  participant p_analyst as Reignite Analyst
  participant p_website as Reignite Portal
  p_customer_app->>p_profiler: Metric breaches a configured threshold
  p_profiler->>p_api: Authenticates with the profiler credentials
  p_api->>p_profiler: Returns the configuration and collection policy
  p_profiler->>p_profiler: Captures a trace or memory dump
  p_profiler->>p_artifact_store: Uploads the artifact
  p_profiler->>p_api: Registers the trace file
  p_api->>p_website: Surfaces the trace in the portal
  p_analyst->>p_website: Claims the trace for analysis
  p_analyst->>p_artifact_store: Downloads the artifact
  p_analyst->>p_customer_app: Delivers the fix
  p_customer_app->>p_profiler: Deploys the fix and keeps measuring
  p_profiler->>p_api: Reports post-fix metrics

Back to all flows