Data model
This is a conceptual model, not a database schema. The authoritative schema lives in the
API's SPE.Data* projects and its EF Core migrations.
erDiagram
CUSTOMER ||--o{ APPLICATION : owns
APPLICATION ||--o{ ENVIRONMENT : has
APPLICATION ||--o{ PROFILER : configures
PROFILER ||--o{ TRACE_FILE : produces
TRACE_FILE ||--o{ ARTIFACT : stores
TRACE_FILE ||--o| ANALYSIS : has
ANALYSIS ||--o{ RESOLUTION : yields
CUSTOMER ||--o{ USER : has
USER }o--|| ROLE : assigned
TEAMS_INSTALLATION }o--|| CUSTOMER : belongs_to
Entities
| Entity | Meaning | Owner |
|---|---|---|
| Customer | The paying organization. | API |
| Application | A customer code base Reignite analyzes; carries the source-control URL and main branch. | API |
| Environment | A deployment target for an application (Development, Staging, Production). | API |
| Profiler | A configured agent instance for one application and one environment; carries ProfilerID, KeyID, Secret, refresh and wait settings. |
API |
| API key | The credential material an agent or client presents. The secret is shown once and stored hashed/encrypted by the platform. | API |
| Trace file | The unit of analyst work: one uploaded trace or dump and its status. | API |
| Artifact | The binary object in Blob Storage that belongs to a trace file. | API + Blob Storage |
| Analysis | The root-cause record an analyst writes for a trace file. | API |
| Resolution | The fix, verification and regression outcome associated with an analysis. | API |
| User / Role | A person and the role that decides what they may do (Analyst, AnalystAdmin, SuperAdmin, Developer, and so on). | API |
| Teams installation | A per-tenant Teams bot installation record. | Teams bot (teams schema) |
| Subscription | The commercial plan and billing state. | API + Stripe |
Trace-file statuses
| Status | Meaning |
|---|---|
Ready |
Uploaded and waiting to be assigned. |
Assigned |
Assigned to an analyst. |
Downloaded |
The analyst's collect-sync has downloaded the artifact. |
Started |
Analysis has started. |
Incomplete |
Analysis is paused (more data or a different analyst). |
Analyzed |
Root cause recorded. |
Fixed |
A fix is prepared. |
PRSubmitted |
The fix is a pull request. |
Deployed |
The customer deployed the fix. |
Resolved |
Regression verification passed. |
ResolvedDuplicate |
The trace is a duplicate of another trace. |
Closed |
Archived by collect-sync. |
ClosedDuplicate |
Duplicate archived by collect-sync. |
The transitions are in the generated trace file lifecycle state diagram.
Notes
- The model is deliberately external. It names the concepts a developer or analyst needs to reason about; it does not name every table or column.
- The Teams bot's
teamsschema is intentionally separate from the API's business schema. The bot'sDbContextmaps only what it needs. - Artifacts are addressed by metadata in SQL and content in Blob Storage. A trace file without its artifact is an incomplete record; the API should treat that as an error, not a valid state.