Files
task-stream/libs/web/tracker/infrastructure
Josep Piguillem 034704e46f feat: alerts open bugs, and repeats of the same problem go to that bug
Owners and admins turn on a secret URL per project (Settings →
Integrations), POST /api/webhooks/alerts/{project}/{token}, that Sentry,
Uptime Kuma, Prometheus Alertmanager, Grafana or any tool sending JSON
with a title can call. A new problem opens a bug as TaskStream (label
«alerta», chosen type and priority); while that bug is open, the same
fingerprint goes to it (a comment at most every 30 minutes) and
«resolved» is said on it; once it is closed, a new bug names the old
one. Alerts of a project are handled one at a time, so two at once open
one bug, and a bug not yet projected still counts as open. Unknown
project, alerts off or a bad token all answer 403.

TaskStream may now comment as the system actor, like it already opened
tickets for public proposals. Stored in Mongo (alert_integrations,
alert_traces), not in the event store.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-17 12:36:55 +02:00
..
2026-10-03 13:40:26 +02:00
2026-10-03 13:40:26 +02:00
2026-10-03 13:40:26 +02:00
2026-10-03 13:40:26 +02:00

web-tracker-infrastructure

Adaptadores GraphQL del tracker.

  • Import: @task-stream/web/tracker/infrastructure
  • Capa: infrastructure · Tags: scope:web-tracker, type:infrastructure

Contenido

  • graphql/*.graphql: operaciones; generated.ts lo genera npx nx run web:codegen.
  • adapters/: implementaciones de los gateways y mappers.ts (GraphQL → dominio, y la configuración de vuelta a input sin __typename).
  • provideTrackerInfrastructure().

Comandos

npx nx lint web-tracker-infrastructure

Reglas de dependencia entre capas: Arquitectura.