MVP shape
The module covers access event recording, log parsing, and a basic authenticated surface
Projects
A lightweight service for access logs, event tracking, and security boundary checks
A server-side monitoring module for recording access events, parsing logs, and validating basic authentication boundaries on public endpoints.
Verifiable entry points
No public demo
The monitor depends on real access logs and can expose IPs, request paths, and runtime timelines, so there is no public demo.
Source evidence
Review log parsing, incremental ingest, SQLite schema, aggregation API, authentication, and the static dashboard.
The module covers access event recording, log parsing, and a basic authenticated surface
Node 22 and the native module ABI are explicit local verification constraints
It can become a runtime summary source for Dashboard Console
Asset status
Only repository-backed product mocks, public documentation, or an explicit no-public-image explanation appear here.
Asset type: Architecture diagram
Asset type: Documentation
The public runbook records log input, configuration, authentication requirements, build tests, and Windows deployment.
Personal projects often go live without minimal access visibility, making abnormal traffic, configuration mistakes, and exposed endpoints hard to diagnose.
Collect, parse, and present key access events through a Node service, with optional Basic Auth for the monitoring surface.
Knock reads Nginx access logs incrementally and writes parsed records to local SQLite. An Express API aggregates time windows, status codes, and suspicious requests, with Basic Auth protecting the monitoring surface.
Step 01
The service reads from a saved file offset and detects truncation or rotation on a best-effort basis.
Step 02
Request fields and suspicious signals are parsed and written inside one transaction.
Step 03
A local database stores indexed requests and data covered by the configured retention window.
Step 04
The API returns overview, time series, top IP, top path, and suspicious-request data for 1h, 24h, or 7d windows.
Step 05
A static dashboard calls the same-origin API; public exposure requires Basic Auth or equivalent access control.
Decision 01
Decision 02
Decision 03