Fix status filter OR logic and add P99/active stats endpoint
All checks were successful
CI / build (push) Successful in 1m1s
CI / docker (push) Successful in 47s
CI / deploy (push) Successful in 29s

Status filter now parses comma-separated values into SQL IN clause
instead of exact match, so filtering by multiple statuses works.

Added GET /api/v1/search/stats returning P99 latency (last hour) and
active execution count, wired into the UI stat cards with 10s polling.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
hsiegeln
2026-03-13 17:34:11 +01:00
parent c1f2ddb3f5
commit 3f98467ba5
8 changed files with 88 additions and 5 deletions

View File

@@ -95,6 +95,17 @@ export interface paths {
};
};
};
'/search/stats': {
get: {
responses: {
200: {
content: {
'application/json': ExecutionStats;
};
};
};
};
};
'/agents': {
get: {
parameters: {
@@ -181,6 +192,11 @@ export interface ProcessorNode {
/** Processor snapshot is a flat key-value map (Map<String, String> in Java) */
export type ProcessorSnapshot = Record<string, string>;
export interface ExecutionStats {
p99LatencyMs: number;
activeCount: number;
}
export interface AgentInstance {
agentId: string;
group: string;