feat: incident tagging — DB schema + API to mark time windows with descriptions #1

Closed
opened 2026-05-09 15:31:21 -07:00 by pyr0ball · 1 comment
Owner

Core Xander ask. Add an incidents table to SQLite, REST endpoints to create/list/delete tagged incidents, and timestamp range association to log entries.

Schema sketch:

  • id, label (free text), started_at (ISO), ended_at (ISO), notes, created_at
  • Entries with timestamp_iso inside the window get associated on query

API:

  • POST /turnstone/api/incidents
  • GET /turnstone/api/incidents
  • DELETE /turnstone/api/incidents/{id}
Core Xander ask. Add an `incidents` table to SQLite, REST endpoints to create/list/delete tagged incidents, and timestamp range association to log entries. Schema sketch: - `id`, `label` (free text), `started_at` (ISO), `ended_at` (ISO), `notes`, `created_at` - Entries with `timestamp_iso` inside the window get associated on query API: - `POST /turnstone/api/incidents` - `GET /turnstone/api/incidents` - `DELETE /turnstone/api/incidents/{id}`
pyr0ball added this to the (deleted) milestone 2026-05-09 15:31:21 -07:00
Author
Owner

Already implemented: incidents table in app/ingest/pipeline.py, CRUD service in app/services/incidents.py, REST endpoints in app/rest.py, and full UI in web/src/views/IncidentsView.vue. Closing.

Already implemented: `incidents` table in `app/ingest/pipeline.py`, CRUD service in `app/services/incidents.py`, REST endpoints in `app/rest.py`, and full UI in `web/src/views/IncidentsView.vue`. Closing.
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: Circuit-Forge/turnstone#1
No description provided.