executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
retellai-observabilitySet up comprehensive observability for Retell AI integrations with metrics, traces, and alerts. Use when implementing monitoring for Retell AI operations, setting up dashboards, or configuring alerting for Retell AI integration health. Trigger with phrases like "retellai monitoring", "retellai metrics", "retellai observability", "monitor retellai", "retella…
Independent GitHub snapshot · Automated classification · Original documentation governs
Set up comprehensive observability for Retell AI integrations.
| Metric | Type | Description |
|---|---|---|
retellai_requests_total | Counter | Total API requests |
retellai_request_duration_seconds | Histogram | Request latency |
retellai_errors_total | Counter | Error count by type |
retellai_rate_limit_remaining | Gauge | Rate limit headroom |
import { Registry, Counter, Histogram, Gauge } from 'prom-client';
const registry = new Registry();
const requestCounter = new Counter({
name: 'retellai_requests_total',
help: 'Total Retell AI API requests',
labelNames: ['method', 'status'],
registers: [registry],
});
const requestDuration = new Histogram({
name: 'retellai_request_duration_seconds',
help: 'Retell AI request duration',
labelNames: ['method'],
buckets: [0.05, 0.1, 0.25, 0.5, 1, 2.5, 5],
registers: [registry],
});
const errorCounter = new Counter({
name: 'retellai_errors_total',
help: 'Retell AI errors by type',
labelNames: ['error_type'],
registers: [registry],
});
async function instrumentedRequest<T>(
method: string,
operation: () => Promise<T>
): Promise<T> {
const timer = requestDuration.startTimer({ method });
try {
const result = await operation();
requestCounter.inc({ method, status: 'success' });
return result;
} catch (error: any) {
requestCounter.inc({ method, status: 'error' });
errorCounter.inc({ error_type: error.code || 'unknown' });
throw error;
} finally {
timer();
}
}
import { trace, SpanStatusCode } from '@opentelemetry/api';
const tracer = trace.getTracer('retellai-client');
async function tracedRetell AICall<T>(
operationName: string,
operation: () => Promise<T>
): Promise<T> {
return tracer.startActiveSpan(`retellai.${operationName}`, async (span) => {
try {
const result = await operation();
span.setStatus({ code: SpanStatusCode.OK });
return result;
} catch (error: any) {
span.setStatus({ code: SpanStatusCode.ERROR, message: error.message });
span.recordException(error);
throw error;
} finally {
span.end();
}
});
}
import pino from 'pino';
const logger = pino({
name: 'retellai',
level: process.env.LOG_LEVEL || 'info',
});
function logRetell AIOperation(
operation: string,
data: Record<string, any>,
duration: number
) {
logger.info({
service: 'retellai',
operation,
duration_ms: duration,
...data,
});
}
# retellai_alerts.yaml
groups:
- name: retellai_alerts
rules:
- alert: Retell AIHighErrorRate
expr: |
rate(retellai_errors_total[5m]) /
rate(retellai_requests_total[5m]) > 0.05
for: 5m
labels:
severity: warning
annotations:
summary: "Retell AI error rate > 5%"
- alert: Retell AIHighLatency
expr: |
histogram_quantile(0.95,
rate(retellai_request_duration_seconds_bucket[5m])
) > 2
for: 5m
labels:
severity: warning
annotations:
summary: "Retell AI P95 latency > 2s"
- alert: Retell AIDown
expr: up{job="retellai"} == 0
for: 1m
labels:
severity: critical
annotations:
summary: "Retell AI integration is down"
{
"panels": [
{
"title": "Retell AI Request Rate",
"targets": [{
"expr": "rate(retellai_requests_total[5m])"
}]
},
{
"title": "Retell AI Latency P50/P95/P99",
"targets": [{
"expr": "histogram_quantile(0.5, rate(retellai_request_duration_seconds_bucket[5m]))"
}]
}
]
}
Implement Prometheus counters, histograms, and gauges for key operations.
Integrate OpenTelemetry for end-to-end request tracing.
Set up JSON logging with consistent field names.
Define Prometheus alerting rules for error rates and latency.
| Issue | Cause | Solution |
|---|---|---|
| Missing metrics | No instrumentation | Wrap client calls |
| Trace gaps | Missing propagation | Check context headers |
| Alert storms | Wrong thresholds | Tune alert rules |
| High cardinality | Too many labels | Reduce label values |
app.get('/metrics', async (req, res) => {
res.set('Content-Type', registry.contentType);
res.send(await registry.metrics());
});
For incident response, see retellai-incident-runbook.