Metrics
The Metrics page gives you a real-time view of your application’s performance and resource usage. You can use it to monitor request patterns, identify bottlenecks, and track resource consumption. To view metrics, navigate to your app and click Metrics in the navigation.
Time Range
Section titled “Time Range”Use the time range picker to control the window of data displayed across all charts. Available time ranges are 1 hour, 6 hours, and 1 day.
Activity
Section titled “Activity”Requests
Section titled “Requests”The requests chart shows HTTP traffic to your application as a stacked bar chart, broken down by status code category:
- 2XX (green): Successful responses
- 4XX (orange): Client errors (bad requests, not found, etc.)
- 5XX (red): Server errors
Use this to spot traffic spikes, elevated error rates, or unexpected patterns.
Application Health
Section titled “Application Health”CPU and Memory Usage
Section titled “CPU and Memory Usage”The CPU and memory charts show your application’s resource consumption over time as a percentage of your limits. Each chart includes a dashed reference line showing the limit.
| Resource | Default Limit |
|---|---|
| CPU | 0.5 vCPU |
| Memory | 500 MB |
- If your application consistently approaches the CPU limit, it may experience throttling. Consider optimizing CPU-intensive operations or reducing the work done per request.
- If your application exceeds the memory limit, it will be terminated (OOM killed) and restarted. If you see memory usage climbing toward the limit, check for memory leaks.
Replicas
Section titled “Replicas”The Metrics page shows how many replicas of your application are currently running (for example, “3/3 replicas running”). FastAPI Cloud automatically scales the number of replicas based on traffic.
If you see fewer replicas running than expected (for example, “1/2 replicas running”), it usually means a new deployment is rolling out, a replica is scaling up, or a pod crashed and is being replaced. This is typically temporary and resolves on its own. If the issue persists, check your application logs for crash errors or out-of-memory issues.