get_correlated_logs
Correlate logs across AWS, Vercel, GCP, and Cloudflare services by merging them into a single chronological timeline to diagnose cross-platform errors.
Instructions
Fetch logs from multiple cloud platforms (AWS CloudWatch + Vercel) for a given time window and optional trace ID, then merge them into a single chronological timeline. Use this to correlate errors across frontend and backend services.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"start_time": "<start_time>"
},
"name": "get_correlated_logs"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| trace_id | No | Trace / request ID to filter logs across platforms. | |
| start_time | Yes | Start of time window (ISO-8601 string or Unix epoch in ms). Example: '2024-06-01T10:00:00Z' | |
| end_time | No | End of time window (ISO-8601 string or Unix epoch in ms). Defaults to now. | |
| aws_log_group_prefix | No | CloudWatch log group prefix to search. Default: /aws/lambda | /aws/lambda |
| aws_region | No | AWS region. Defaults to AWS_REGION env var. | |
| vercel_project | No | Vercel project name or ID to pull deployment logs from. | |
| gcp_service | No | GCP Cloud Run service name to filter logs. Omit to pull all project logs. | |
| cloudflare_worker | No | Cloudflare Worker script name to tail logs from. |