Parham Monfared
1262690276
The single-file stdlib server became the limit: no way to track what had been done about an alert, no accounts, and a UI that had to be hand-rolled in template strings. This restructures it into something deployable. Backend (FastAPI) - app/ holds config, database, auth, delivery and the routers; triagelib keeps the triage engine unchanged, so the validated screening and runbook logic is untouched. - Cases persist per alert fingerprint with a status workflow (investigating, customer contacted, escalated to Infra, waiting, remediated, resolved, won't fix, false positive), an assignee, notes and an append-only history. An alert that stops and re-fires lands back on the same case and counts as a reopen. - Suppression rules move from a JSON file into the database. Auth - Signed session cookies over PBKDF2 local accounts, plus an OIDC flow ready for Authentik: users are created on first login and admin follows a group claim. Local login can be switched off entirely once SSO is live. Zendesk and Jira - Delivery is now implemented, behind three gates: the integration must be configured, its feature flag on, and CX_FEATURE_SEND_ENABLED on. A demo instance leaves the last off and cannot mail anyone. Both search before creating, so re-diagnosing an alert updates one ticket rather than opening several, and a rolling daily cap stops a loop mailing everybody. Deployment - Multi-stage Dockerfile builds the bundle and serves it from the API origin. - docker-compose for local and single-host use; Gitea Actions runs the tests, builds the image and renders deploy/k8s with envsubst. Two fixes found while testing: assigning a case returned a null assignee, and add_event could leave an already-loaded history collection stale. Known gap: the engine reaches OpenStack via `docker exec <region>-osc`, which does not work in a pod without the CX-Tools containers alongside it. docs/DEPLOYMENT.md sets out the three ways to close that. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
48 lines
1.3 KiB
YAML
48 lines
1.3 KiB
YAML
# Local development and single-host deployment.
|
|
#
|
|
# cp .env.example .env # then edit
|
|
# docker compose up --build
|
|
#
|
|
# Reaching Prometheus and OpenStack still depends on the CX-Tools containers
|
|
# being up on the same host - see docs/DEPLOYMENT.md.
|
|
services:
|
|
app:
|
|
build:
|
|
context: .
|
|
dockerfile: backend/Dockerfile
|
|
image: cx-triage:local
|
|
ports:
|
|
- "${CX_PORT:-8080}:8080"
|
|
env_file: [.env]
|
|
environment:
|
|
CX_DATABASE_URL: ${CX_DATABASE_URL:-postgresql+psycopg://cx:cx@db:5432/cxtriage}
|
|
CX_STATIC_DIR: /app/static
|
|
volumes:
|
|
# The engine shells out to `docker exec <region>-osc ...`, so it needs the
|
|
# host's Docker socket. Mount read-only and drop it if you point the app
|
|
# at Prometheus/OpenStack directly instead.
|
|
- /var/run/docker.sock:/var/run/docker.sock:ro
|
|
- cx-data:/data
|
|
depends_on:
|
|
db: { condition: service_healthy }
|
|
restart: unless-stopped
|
|
|
|
db:
|
|
image: postgres:16-alpine
|
|
environment:
|
|
POSTGRES_USER: cx
|
|
POSTGRES_PASSWORD: cx
|
|
POSTGRES_DB: cxtriage
|
|
volumes:
|
|
- cx-db:/var/lib/postgresql/data
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U cx -d cxtriage"]
|
|
interval: 5s
|
|
timeout: 3s
|
|
retries: 20
|
|
restart: unless-stopped
|
|
|
|
volumes:
|
|
cx-data:
|
|
cx-db:
|