Files
copilotkit__copilotkit/showcase/harness/config/alerts/agent-red-fleet.yml
Jordan Ritter 0522b7fa41 refactor(showcase): rename showcase/ops → showcase/harness
The monitoring/alerting service is a test harness (probes, assertions,
alerting), not an operations service. Rename the directory, package
name (@copilotkit/showcase-ops → @copilotkit/showcase-harness), all
internal references (Dockerfile, Prometheus metric prefix
showcase_ops_ → showcase_harness_, orchestrator log messages, probe
YAML nameExcludes, test fixtures), and regenerate pnpm-lock.yaml.

Wire protocol names (X-Ops-* headers) and shell-dashboard internal
API naming (OPS_BASE_URL, ops-api.ts) are intentionally unchanged —
they are stable contracts between sender and receiver.
2026-04-28 13:48:12 -07:00

25 lines
629 B
YAML

id: agent-red-fleet
name: "Fleet-wide agent-red escalation"
owner: "@oss"
# Cross-service aggregation for the L2 agent-reachability dimension. Mirrors
# smoke-red-fleet.yml — see that file's comments for rationale and timing.
signal:
dimension: agent
triggers:
- green_to_red
- sustained_red
# A7: groupBy omitted; signal.dimension already partitions traffic. See
# smoke-red-fleet.yml for rationale and buildBucketKey for the mechanics.
aggregation:
windowMs: 120000
minMatches: 3
template: |
<!channel> agent red across fleet — {{count}} services: {{services}}
conditions:
rate_limit:
window: 10m