jcoffey-dev
a69093fff7
govulncheck started failing on main: golang.org/x/net 0.58.0 has an HTTP/2 HPACK encoder race that can crash a server (GO-2026-6617, fixed in 0.60.0), and the Go 1.26.8 toolchain in the pinned CI image has three net/http fixes pending (GO-2026-6612, GO-2026-6613, fixed in 1.26.9). - x/net 0.60.0 in every module that uses it, with the x/sys, x/text and x/term patch releases it pulls in; proto and the two fixtures move to go 1.26, which x/net 0.60.0 requires and CI already builds with. - The golang:1.26-bookworm image is re-pinned to today's digest (1.26.9) in both the Gitea and GitHub workflows. The Dockerfiles use the floating golang:1.26-alpine tag and pick up 1.26.9 on their next build. go build and govulncheck are clean in all nine modules.
windows-fixture
Sends synthetic Windows Event Log-shaped PushBatchRequests directly to
ingest's gRPC endpoint, bypassing the actual Windows agent entirely.
What this does and doesn't test
Tests: can the pipeline (ingest → ClickHouse → search → api → web)
correctly handle Windows-shaped data — the winevt.* attributes, the
record_id join between SQL and full-text search, Windows severity
levels mapping onto the right column values? This is exactly what's
automatable without a Windows host, and it's genuinely exercised: five
realistic, well-known Windows events (failed/successful logon, a service
state change, an application crash, an unexpected reboot) with real
EventIDs and providers.
Does not test: whether the real Windows agent's EvtSubscribe/ETW
integration actually works, whether Windows service registration
succeeds, whether ETW session creation/provider enabling works. Those are
fundamentally different questions — they need a real or virtualized
Windows host, and nothing here pretends otherwise. See
/docs/phase-1-runbook.md for exactly which is which.
Running
Requires the docker-compose stack up (ingest reachable, dev certs
generated):
cd hack/windows-fixture
go run . --count 5
sent 5 synthetic Windows-shaped records, ingest accepted 5
[SEVERITY_WARN] An account failed to log on. (event_id=4625 provider=Microsoft-Windows-Security-Auditing)
...
Then confirm both query paths see it:
curl -s -X POST http://localhost:8080/query -H 'Content-Type: application/json' \
-d '{"query": "SELECT host, severity, message, attributes['"'"'winevt.event_id'"'"'] AS event_id FROM logs WHERE host = '"'"'WIN-FIXTURE-01'"'"' ORDER BY timestamp DESC"}'
curl -s -X POST http://localhost:8080/query -H 'Content-Type: application/json' \
-d '{"query": "notepad"}'
Flags: --addr (default localhost:4317), --ca/--cert/--key
(default to ../dev-certs/out/{ca,client,client-key}.pem), --count
(default 5, cycles through the fixed event list if higher).