jcoffey-dev
9bbd802a91
Phase 2 unified the two query languages behind one endpoint and renamed
the request field, and the runbooks were never updated. Following them
today does not work:
{"sql": ...} -> 400 query must not be empty
POST /api :8080/search -> 404, the route no longer exists
Both appear in the Phase 0 and Phase 1 runbooks and in the
windows-fixture README. That matters more than a normal doc typo,
because status.md cites the Phase 0 runbook as the record of how Phase
0 was verified -- so the documented verification procedure is one
nobody can re-run as written.
The Phase 1 step is rewritten rather than search-and-replaced: it
checked the SQL and full-text paths against two different endpoints,
and its exit criterion (the same record_id from both) now has to be
expressed against /query twice, once with SQL and once with a bare
word.
Phase 0's expected output for SELECT 1 also gained a warnings field
since it was written.
Every command here was run against a live stack before being written
down, including confirming both paths return the same record_id.
Signed-off-by: John Coffey <[email protected]>
53 lines
2.0 KiB
Markdown
53 lines
2.0 KiB
Markdown
# windows-fixture
|
|
|
|
Sends synthetic Windows Event Log-shaped `PushBatchRequest`s 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):
|
|
|
|
```sh
|
|
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:
|
|
|
|
```sh
|
|
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).
|