AWS API Gateway Integration
Monitor request count, latency, 4xx/5xx error rates, and integration latency by stage. SLO burn rate analysis and AI anomaly detection keep your API layer within availability commitments.
How It Works
Deploy CloudFormation Stack
Launch the TigerOps CloudFormation template to configure Metric Streams for the AWS/ApiGateway and AWS/ApiGatewayV2 namespaces and grant the necessary IAM permissions.
Enable Detailed Metrics
Enable detailed CloudWatch metrics on your API Gateway stages. Detailed metrics provide per-resource and per-method breakdowns of latency and error rates beyond the stage-level aggregates.
Enable Access Logging
Configure API Gateway access logging to CloudWatch Logs using a JSON log format. TigerOps parses the access logs to provide per-path, per-IP, and per-user error rate and latency breakdowns.
Set SLO Alerts per Stage
Define error rate and latency SLOs per API stage. TigerOps computes SLO burn rate and fires early warning alerts when you are burning through your error budget faster than planned.
What You Get Out of the Box
Request Count & Throughput
Total API requests per stage, resource, and method. TigerOps surfaces traffic distribution across endpoints and detects unexpected traffic volume changes with AI anomaly detection.
4xx & 5xx Error Rate Tracking
Client error (4xx) and server error (5xx) rates broken down by HTTP status code, resource, and method. TigerOps distinguishes between API Gateway errors and integration errors for accurate fault attribution.
Latency & Integration Latency
End-to-end request latency and integration latency (time spent in your backend) tracked as p50/p95/p99 per stage. TigerOps alerts when integration latency spikes to identify backend slowdowns.
Stage-Level Deployment Tracking
API Gateway stage deployments are captured from CloudTrail and overlaid on metric charts. TigerOps immediately surfaces error rate and latency changes following a stage deployment.
Throttling & Quota Monitoring
ThrottleCount and usage plan quota utilisation tracked per API key and usage plan. TigerOps alerts when clients are being throttled and identifies which API keys are consuming the most quota.
AI SLO Burn Rate Analysis
TigerOps computes rolling error budget consumption rate and forecasts SLO breach time. Alerts fire hours before the breach so you can respond before your monthly availability commitment is at risk.
API Gateway Access Logging Setup
Enable detailed metrics and access logging on your API Gateway stage.
# Enable detailed metrics and access logging on a REST API stage
aws apigateway update-stage \
--rest-api-id abc123def \
--stage-name production \
--patch-operations \
op=replace,path=/defaultRouteSettings/detailedMetricsEnabled,value=true \
op=replace,path=/accessLogSettings/destinationArn,value=arn:aws:logs:us-east-1:123456789:log-group:/apigateway/production-access-logs
# Set access log format (JSON for TigerOps parsing)
aws apigateway update-stage \
--rest-api-id abc123def \
--stage-name production \
--patch-operations 'op=replace,path=/accessLogSettings/format,value={"requestId":"$context.requestId","ip":"$context.identity.sourceIp","caller":"$context.identity.caller","user":"$context.identity.user","requestTime":"$context.requestTime","httpMethod":"$context.httpMethod","resourcePath":"$context.resourcePath","status":"$context.status","protocol":"$context.protocol","responseLength":"$context.responseLength","integrationLatency":"$context.integrationLatency","responseLatency":"$context.responseLatency"}'
# Deploy TigerOps API Gateway monitoring stack
aws cloudformation deploy \
--template-url https://tigerops-cfn.s3.amazonaws.com/apigateway-integration.yaml \
--stack-name tigerops-apigw \
--capabilities CAPABILITY_IAM \
--parameter-overrides \
TigerOpsApiKey=${TIGEROPS_API_KEY} \
AccessLogGroup=/apigateway/production-access-logs \
ErrorRateSloPercent=99.9Common Questions
Does TigerOps support both REST API and HTTP API (API Gateway v2)?
Yes. TigerOps collects metrics from both AWS/ApiGateway (REST API) and AWS/ApiGatewayV2 (HTTP API and WebSocket API) namespaces via Metric Streams. Both are displayed in the same API Gateway dashboard.
How does TigerOps get per-resource latency for API Gateway?
Per-resource latency requires enabling detailed CloudWatch metrics on the API stage (charged per stage). When enabled, TigerOps collects Latency and IntegrationLatency broken down by resource path and HTTP method.
Can TigerOps alert when API Gateway is throttling clients?
Yes. TigerOps monitors the ThrottleCount metric per API stage. When throttling exceeds your configured threshold, TigerOps fires an alert and identifies the API key or usage plan responsible from access log data.
How does TigerOps correlate API Gateway errors with Lambda backend errors?
TigerOps links API Gateway integration errors with the corresponding Lambda invocation errors via the AWS request ID. When a 502 Bad Gateway is returned to a client, TigerOps finds the Lambda error log line with the same request ID.
Does TigerOps support API Gateway WebSocket APIs?
Yes. TigerOps monitors WebSocket API metrics including ConnectCount, MessageCount, ExecutionError, and IntegrationError via AWS/ApiGatewayV2 Metric Streams. Connection duration and message rate anomalies are detected automatically.
Protect Your API SLOs Before They Breach
Error rate monitoring, SLO burn rate alerts, and AI traffic anomaly detection. Connect your API Gateway in minutes.