liveBook · Manning

Monitoring

As explained in Vibe Engineering

Monitoring is the continuous collection and examination of system behavior and operational measurements.

Monitoring continuously collects and examines system behavior and operational measurements so teams can detect token spikes, recurring agent failures, timeouts, and hidden bottlenecks before they become expensive surprises. section 5.6.2

Effective monitoring turns visibility into disciplined operational decisions:

  • Track agent-specific metrics, failure modes, and alerting thresholds rather than assuming infrastructure monitoring is sufficient. section 5.6.2
  • Use timing and queue data to expose uneven workloads, idle parallel agents, and optimization opportunities. section 5.6.2
  • Attach an explicit if-X-then-Y response to every metric; otherwise, a dashboard is merely decoration. section 9.4.4

Monthly AI development health check

A useful dashboard connects developer outcomes to action: investigate model or prompt changes when first-attempt success falls below 78%, audit waste when visible cost exceeds $1,000 per developer monthly, and schedule a retrospective when satisfaction falls below 3.8. section 9.4.4

Pipeline: payment-retry-feature
Status: Running (7m 23s)
[✓] Architect      (2m 14s, 12k tokens)  → design.md
[✓] Implementer-1  (3m 02s, 28k tokens)  → resilience.py
[◐] Implementer-2  (4m 11s, running)     → gateway changes
[ ] Tester-1       (waiting)
[ ] Tester-2       (waiting)  
[ ] Documenter     (waiting)
 
Total tokens: 47k ($0.42)
Estimated remaining: 35k tokens, 5 minutes

Inspect a live pipeline view showing agent status, elapsed time, token consumption, generated artifacts, waiting stages, total cost, and estimated completion. section 5.6.2

How Vibe Engineering covers it

How deep it goes
Extends from metrics and dashboards to alert thresholds and response playbooks, without detailing monitoring implementation.
Examples
Uses a live agent pipeline dashboard and a monthly health check with cost, quality, satisfaction, and cycle-time thresholds.
What it assumes
Assumes monitoring services and infrastructure, then distinguishes agent-specific metrics, failures, and alerting needs.
What you can do after
Operate/configure monitoring dashboards and convert threshold breaches into investigations, audits, retrospectives, or tooling changes.
How it connects
Links observability with alerting, dashboards, bottleneck analysis, cost optimization, and developer outcomes.

Also explained in

Compare how 51 books explain monitoring →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.