Files
copilotkit__copilotkit/showcase/harness/config/probes/aimock-wiring.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

18 lines
750 B
YAML

# Probe: aimock-wiring
#
# Verifies every LLM-calling showcase service has its OpenAI/Anthropic base
# URL pointed at showcase-aimock. Single-target probe — the driver fans out
# internally to every Railway service (minus the exclusion list), which is
# why `target` is a single synthetic entry rather than `targets: [...]`.
#
# Schedule mirrors the pre-existing cron cadence from orchestrator.ts
# (every 6 hours at the top of the hour). The accompanying alert rule
# `config/alerts/aimock-wiring-drift.yml` adds a `cron_only` trigger on
# the same schedule so a long green-run still produces a heartbeat tick
# the alert-engine can reason about.
kind: aimock_wiring
id: aimock-wiring
schedule: "0 */6 * * *"
target:
key: "aimock_wiring:global"