Operational practices for maintaining production agent reliability.
Daily Operations
Morning Check (5 minutes)
- Check monitoring dashboard - any alerts fired overnight?
- Review current status - all agents UP?
- Check latency trends - any spikes?
- Verify scheduled jobs ran successfully
Weekly Review (30 minutes)
- Review availability metrics vs SLA
- Check latency percentile trends
- Review any incidents from the week
- Identify agents trending toward DEGRADED
- Update capacity projections
Monthly SLA Report
Availability percentage per agent, latency percentiles, eval pass rate, incident count and summary, comparison to previous months, action items.
Scenario Playbooks
Scenario: Agent Goes DOWN
Immediate actions (first 5 minutes):
- Acknowledge alert
- Verify not false positive (check from different network/device)
- Check if deploy happened recently
- Check agent provider status page
| Finding | Action |
|---|---|
| Recent deploy caused it | Roll back |
| Dependency is down | Wait/failover to backup |
| Agent crashed | Restart/redeploy |
| Provider outage | Wait, communicate to users |
| Unknown | Escalate |
Scenario: Agent Shows DEGRADED
Investigation: Which tests are failing? What's the latency distribution? Which evaluation prompts are failing? When did degradation start?
Common causes: Partial infrastructure issue, high load, model quality degradation, partial deployment in progress.
Scenario: Eval Pass Rate Dropping
This is serious - the agent is returning wrong answers.
Common causes: Model update changed behavior, context/prompt configuration changed, upstream data source issue, rate limiting causing truncated responses.
Scenario: Latency Spike
| Cause | Indicators | Fix |
|---|---|---|
| High load | All latencies up | Scale |
| Cold starts | Intermittent spikes | Keep warm |
| Large responses | Total latency up, TTFB ok | Optimize response |
| Network issues | Regional specific | Wait/investigate |
| Dependency slow | Consistent increase | Profile, optimize |
Scenario: Regional Failure
Common causes: CDN configuration issue, regional deployment failure, ISP routing problems, geo-blocking misconfiguration.
Scenario: Alert Storm
Don't panic. Look for common cause (usually infrastructure). Identify if monitoring system itself is healthy. If monitoring healthy: major incident, escalate. If monitoring unhealthy: fix monitoring first.
Troubleshooting Guides
"Can't Reach Agent Endpoint"
- DNS resolution - Can you resolve the hostname? Is DNS pointing to correct IP?
- Network connectivity - Can you ping the IP? Are there firewall issues?
- TLS/SSL - Is the certificate valid? Is it expired?
- Service running - Is the agent process running? Correct port?
- Load balancer - Is the LB healthy? Are backends registered?
"Agent Responds But Answers Wrong"
- Recent changes - Any deploy in last 24 hours?
- Model state - Is model loaded correctly? Provider issues?
- Context/RAG - Is context being retrieved? Right context?
- Prompt configuration - Has system prompt changed?
- Dependencies - Are all data sources available?
"Intermittent Failures"
Common patterns:
- Regular interval failures → cron job interfering
- Specific times → traffic spike, maintenance
- Random → race condition, resource exhaustion
Communication Templates
Status Page Update (Incident Start)
[INVESTIGATING] Agent Performance Degradation
We are currently investigating elevated error rates
affecting [agent name]. Some users may experience
slower responses or errors.
We will provide an update within 30 minutes.Status Page Update (Resolved)
[RESOLVED] Agent Performance Degradation
The issue affecting [agent name] has been resolved.
All systems are operating normally.
Duration: [start] - [end] ([X] minutes)
Impact: [description]Metrics to Watch
Real-Time (Dashboard)
| Metric | Warning | Critical |
|---|---|---|
| Availability | <99% | <95% |
| Eval Pass Rate | <95% | <90% |
| TTFB P50 | >target×1.5 | >target×2 |
| Error Rate | >1% | >5% |
Escalation Paths
| Severity | First Responder | Escalate After | To |
|---|---|---|---|
| Critical | On-call engineer | 30 min | Engineering lead |
| High | On-call engineer | 1 hour | Engineering lead |
| Medium | Assigned engineer | 4 hours | Team lead |
| Low | Assigned engineer | 24 hours | Team lead |
