mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

[INFRA-007] Job events and audit logging #169

New Issue
Closed
opened 2026-02-01 07:24:42 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-02-01 07:24:42 +00:00
Owner
Copy Link

Summary

Implement job-events module for immutable audit logging using event sourcing pattern.

Event Types

Job lifecycle:

  • job.created, job.queued, job.started, job.completed, job.failed

Step lifecycle:

  • step.started, step.progress, step.output, step.completed

AI events:

  • ai.tool_called, ai.tokens_used, ai.artifact_created

Gate events:

  • gate.started, gate.passed, gate.failed

Storage Strategy

  • PostgreSQL: Immutable audit log (permanent)
  • Valkey Streams: Recent events (last 1000 per job)
  • Valkey Pub/Sub: Real-time streaming

API Endpoints

  • GET /runner-jobs/:jobId/events - List events for a job
  • GET /runner-jobs/:jobId/events/stream - SSE stream of events

Tasks

  • Create apps/api/src/job-events/job-events.module.ts
  • Create apps/api/src/job-events/job-events.service.ts
  • Create apps/api/src/job-events/job-events.controller.ts
  • Implement event emission (internal service)
  • Implement PostgreSQL persistence
  • Implement Valkey Streams for recent events
  • Implement Pub/Sub for real-time

Files to Create

  • apps/api/src/job-events/job-events.module.ts
  • apps/api/src/job-events/job-events.service.ts
  • apps/api/src/job-events/job-events.controller.ts
  • apps/api/src/job-events/dto/

Acceptance Criteria

  • Events are emitted for all job/step state changes
  • Events are persisted to PostgreSQL
  • Recent events available via Valkey Streams
  • Real-time streaming works via Pub/Sub

Related

## Summary Implement job-events module for immutable audit logging using event sourcing pattern. ## Event Types Job lifecycle: - job.created, job.queued, job.started, job.completed, job.failed Step lifecycle: - step.started, step.progress, step.output, step.completed AI events: - ai.tool_called, ai.tokens_used, ai.artifact_created Gate events: - gate.started, gate.passed, gate.failed ## Storage Strategy - PostgreSQL: Immutable audit log (permanent) - Valkey Streams: Recent events (last 1000 per job) - Valkey Pub/Sub: Real-time streaming ## API Endpoints - GET /runner-jobs/:jobId/events - List events for a job - GET /runner-jobs/:jobId/events/stream - SSE stream of events ## Tasks - [ ] Create apps/api/src/job-events/job-events.module.ts - [ ] Create apps/api/src/job-events/job-events.service.ts - [ ] Create apps/api/src/job-events/job-events.controller.ts - [ ] Implement event emission (internal service) - [ ] Implement PostgreSQL persistence - [ ] Implement Valkey Streams for recent events - [ ] Implement Pub/Sub for real-time ## Files to Create - apps/api/src/job-events/job-events.module.ts - apps/api/src/job-events/job-events.service.ts - apps/api/src/job-events/job-events.controller.ts - apps/api/src/job-events/dto/ ## Acceptance Criteria - Events are emitted for all job/step state changes - Events are persisted to PostgreSQL - Recent events available via Valkey Streams - Real-time streaming works via Pub/Sub ## Related - Epic: #162 - Depends on: #164 (schema), #165 (BullMQ/Valkey)
jason.woltje added this to the M4.2-Infrastructure (0.0.4) milestone 2026-02-01 07:24:42 +00:00
jason.woltje added the phase-2apip0api labels 2026-02-01 07:24:42 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label api api p0 phase-2
Milestone
No items
No Milestone M4.2-Infrastructure (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#169
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?