How aadilvarshani/reaperwatch works
ReaperWatch is a Windows endpoint telemetry collector and analyst console. A process-start event is captured through ETW, enriched and normalized by the agent, then written to local JSONL and optionally pushed to the console. The console ingests events from JSONL or authenticated HTTP, stores them, evaluates EQL detection rules, and serves APIs to the dashboard for overview, alerts, and hunting. README-documented dashboard capabilities are included; some frontend wiring and unsampled subsystem details are represented only where documentation supports them.
Main entry points: server.js Console API · etw_consumer.cpp ETW Consumer · matcher.js Detection Matcher · ingest.js Event Ingestion
Components 24
Windows Agent
- Agent Startup
agent/main.cpp - ETW Consumer
agent/collectors/etw_consumer.cpp - Process Enrichment
agent/collectors/process_monitor.cpp - Process Event Model
agent/collectors/process_event.h - JSON Serialization
agent/collectors/event_json.cpp - Network Config
agent/transport/config.cpp - JSONL Event Sink
agent/transport/event_sink.cpp - HTTP Sender
agent/transport/http_sender.cpp
Console Backend
- Console API
backend/api/server.js - JSONL Tailer
backend/ingestor/tail.js - Event Ingestion
backend/ingestor/ingest.js - SQLite Store
backend/storage/db.js - Detection Matcher
backend/detection/matcher.js - Declarative Rules
backend/detection/rules.js - MITRE Metadata
backend/detection/mitre.js - API Queries
backend/api/queries.js - Ingest Key
backend/storage/ingestKey.js
Analyst Dashboard
- Dashboard Views
dashboard/js/app.js - Dashboard Data
dashboard/js/data.js - EQL Interpreter
dashboard/js/eql.js
Other components
- Administrator
- Kernel ETW
- Events JSONL
- Analyst
Connections 29
- Administrator → Agent Startup: starts elevated
agent/main.cpp - Agent Startup → Network Config: loads config
agent/main.cpp - Agent Startup → ETW Consumer: starts collection
agent/main.cpp - ETW Consumer → Kernel ETW: consumes events
agent/collectors/etw_consumer.cpp - ETW Consumer → Process Enrichment: builds events
agent/collectors/etw_consumer.cpp - Process Enrichment → Process Event Model: populates
agent/collectors/process_monitor.cpp - ETW Consumer → JSON Serialization: serializes events
agent/collectors/etw_consumer.cpp - ETW Consumer → JSONL Event Sink: appends events
agent/collectors/etw_consumer.cpp - JSONL Event Sink → Events JSONL: writes JSONL
agent/transport/event_sink.cpp - ETW Consumer → HTTP Sender: sends events
agent/collectors/etw_consumer.cpp - Network Config → HTTP Sender: configures destination
README.md - HTTP Sender → Console API: POSTs events
README.md - Console API → Ingest Key: loads key
backend/api/server.js - Console API → SQLite Store: opens store
backend/api/server.js - Console API → JSONL Tailer: starts tailer
backend/api/server.js - JSONL Tailer → Events JSONL: reads appended data
backend/ingestor/tail.js - JSONL Tailer → Event Ingestion: passes events
backend/ingestor/tail.js - Console API → Event Ingestion: ingests HTTP events
backend/api/server.js - Event Ingestion → SQLite Store: stores events and alerts
backend/ingestor/ingest.js - Event Ingestion → Detection Matcher: matches event
backend/ingestor/ingest.js - Detection Matcher → Declarative Rules: evaluates rules
backend/detection/matcher.js - Detection Matcher → EQL Interpreter: runs queries
backend/detection/matcher.js - Detection Matcher → MITRE Metadata: adds technique metadata
backend/detection/matcher.js - Console API → API Queries: serves query results
backend/api/server.js - API Queries → SQLite Store: reads records
backend/api/queries.js - Analyst → Dashboard Views: uses console
README.md - Dashboard Views → Dashboard Data: renders data
- Dashboard Data → Console API: fetches console data
README.md - Dashboard Views → EQL Interpreter: runs Hunt queries
README.md