include db for gitea build
This commit is contained in:
1 parent
8de4a2e010
commit
645f923175
33 files changed
+1490
-150
No files matched your search
@@ -120,6 +120,29 @@ Categories: `scanner_probe`, `dependency_unreachable`, `client_credential_issue`
|
||||
`uaClass` on issue samples and endpoint stats. Issues UI: add-filter offers
|
||||
`client: X` and `hide client: X`. Not yet a triage/spike feature.
|
||||
|
||||
- Trace context (`internal/tracectx`): one request is several spans in several
|
||||
envelopes (nginx outer span on :442 with the real client, nginx inner span on
|
||||
:8181 from 127.0.0.1, then the app span), so the ingest-time same-envelope
|
||||
lookup in `normalizeTraces` almost never finds the parent (7 of 1154 nginx
|
||||
spans measured). `tracectx.Resolve` works on a loaded span set instead and is
|
||||
order independent. It yields `ClientIP` (first public peer up the chain),
|
||||
`IsDuplicate` (repeats an ancestor's failure: same status code), `IsRootCause`,
|
||||
child / upstream-child counts, `ParentMissing`.
|
||||
- `bad-actors` resolves loopback hops to the real client (839 hop spans /
|
||||
583 probes recovered in a 3h sample).
|
||||
- `spike-alerts` loads the spans of every trace with an error, drops duplicate
|
||||
hops from the counts and reports distinct clients per pattern; it falls back
|
||||
when the trace columns are absent. Historical rows have empty `span_id`, so it
|
||||
only helps for data written since the trace columns shipped (~08:09 UTC 2026-09-20).
|
||||
- `features.Row` gained `LogicalErrors`, `DuplicateErrors`, `RootCauseErrors`,
|
||||
`DistinctClients`, `TopClientShare`, `BotErrorShare` (additive).
|
||||
`window-features` reads optional `clientIp/uaClass/isDuplicate/isRootCause/hasUpstream`.
|
||||
- Trace view in the UI shows the resolved client (`lib/trace-client.ts`).
|
||||
- Not done: the collector still records the hop IP on issue samples at ingest;
|
||||
span name `GET /` for orchestrator spans is unchanged (changing it alters every
|
||||
orchestrator pattern signature); `HasUpstream` is loaded but not yet a triage
|
||||
rule; trace propagation is missing in cart/checkout/profile/scheduling (roots only).
|
||||
|
||||
## Commands
|
||||
|
||||
```bash
|
||||
|
||||
Reference in new issue
Block a user