Metrics, logs & alerts · Verify
Observability Semantics & Cost Check
Verify that the selected telemetry path represents the intended signal within its identity, freshness and cardinality limits.
MCP library 1.6.1 · Instruction library 1.6.1 · English technical instructions
← Back to searchUse this workflow
Connect Vibe Coding Library to a coding agent that supports MCP over Streamable HTTP. Choose Other / MCP agent for a neutral prompt, or a ready-made Codex or Claude Code invocation. Add your task details below.
Goal
Verify that the selected telemetry path represents the intended signal within its identity, freshness and cardinality limits.
Context
Identify selected metric/log/alert/dashboard, actual engines/versions, units and labels, expected signal meaning, cardinality budget and observation window.
Scenarios
Select the cases that test the requested guarantee. Define expected state/effects before execution; use the authorized environment and a valid control.
- Generate representative metrics/logs across tenants, status classes, replicas, and error paths; measure series/stream growth and ingestion rejection.
- Run recording/alert rules through normal, reset, missing, stale, burst, and recovery windows.
- Provision dashboards/alerts in a disposable environment and validate datasource, variables, units, permissions, links, and query errors.
- Exercise VictoriaLogs ingestion backpressure, malformed timestamps, tenant mismatch, retention boundary, and bounded query concurrency.
- Compare end-to-end signal latency and correlation from emitted event to operator-visible dashboard/alert.
Verification
Compare emitted and queried values, reset/no-data behavior, alert transitions, tenant visibility and measured series/stream or query growth.
Execute and decide
Use a controlled emitter/time series or log corpus with expected counts, units, timestamps, tenant and label dimensions. Establish the normal query/operator result, then replay the selected reset, stale/missing, burst, ingestion-failure or recovery window.
Observe ingestion acceptance, queried values, rule/alert transitions and the displayed units/identity. Measure actual series/stream/query growth for the supplied dimensions; distinguish a theoretical cardinality bound from observed combinations. Route test alerts to a controlled sink rather than real recipients unless authorized.
Return passed, failed or blocked with input/window, expected/observed signal, resource evidence and untested engine/production layers. Feed a failure into the authorized signal-owner repair, repeat its corpus/control and finish Patch Checking for source changes.
Workflow ID: observability-semantics-cost-check · View the versioned source · Shared workflow and authority rules