Metrics
Metrics come from OpenTelemetry auto-instrumentation, CloudWatch Lambda/API Gateway metrics, and service-specific custom metrics.
Sources
| Source | Examples | Where configured |
|---|---|---|
| OTel host/process/http instrumentation | process CPU, memory, HTTP duration/counts | OTEL_NODE_ENABLED_INSTRUMENTATIONS in serverless.common.yml |
| AWS SDK instrumentation | DynamoDB, SQS, Lambda client calls | OTel Node instrumentation layer |
| Lambda/API Gateway CloudWatch metrics | invocations, errors, duration, throttles, method metrics | provider.tracing, provider.apiGateway.metrics, Terraform stage settings |
| Custom metrics | leads queue/downstream failure metrics | service handlers such as services/leads/functions/* |
Standard Lambda RED
| Metric | Meaning |
|---|---|
aws_lambda_invocations | Request rate |
aws_lambda_errors | Error count/rate |
aws_lambda_duration_average | Latency |
aws_lambda_throttles | Throttle count |
Alarms
Per-service CloudWatch alarms are defined in serverless.common.yml and attached by each service's custom.alerts block.
| Tier | Use case | Error threshold |
|---|---|---|
alertsCritical | Tier-1 services such as leads | 5 errors / 5 min |
alertsImportant | Higher-traffic or partner-facing services | 8 errors / 10 min |
alertsStandard | Default service tier | 20 errors / 10 min |
Prod alarms notify PagerDuty and dev+alerts@drive.com.au; non-prod alarm behavior depends on the service's selected alert tier and stage list.