summarize_access_log
Summarize proxy access logs to identify client timeouts, upstream latency, scanner activity, and sensitive data exposure using aggregated status classes and latency percentiles.
Instructions
[probe] Proxy access log aggregated: status classes, top paths with p50/p95, per-upstream latency and 504s, 499s (clients giving up), proxy-vs-upstream gap, scanner-like paths, sensitive data in the log. Never raw lines.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"service": "<service>"
},
"name": "summarize_access_log"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | Time window like 15m, 2h, 1d (default 15m) | |
| service | Yes | Workload name as you would say it: a Deployment, StatefulSet, DaemonSet, Service, or Pod name | |
| namespace | No | Kubernetes namespace (required: no default configured; see list_namespaces) |