Metrics, logs & alerts · Verify

Observability Semantics & Cost Check

Generate representative metrics/logs across tenants, status classes, replicas, and error paths; measure series/stream growth and ingestion rejection.

Vibe Coding 1.3.0 · vibe-observability · English technical instructions

← Back to search

Use this workflow

Use this workflow in Codex or Claude Code with the free Vibe Coding plugin. Choose your assistant and prompt language, then add your task details after the prompt.

Prompt

Use $vibe-observability, workflow “Observability Semantics & Cost Check” (ID: observability-semantics-cost-check). Follow this workflow for the task below. Report the result in English.

Install the plugin

Operation

Verify the selected invariant through bounded scenarios in an authorized environment. Do not turn verification into unrelated implementation. Return passed, failed or blocked, with actual evidence and any missing required scenario.

Scenarios

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.

Workflow ID: observability-semantics-cost-check · View the versioned source · Shared workflow and authority rules