Traffic
Observe the HTTP request stream for a Skytells app — request rate, response times, status code distribution, and per-request details.
The Traffic page shows the HTTP request stream hitting your app in real time and historically. Use it to understand load patterns, detect latency regressions, and correlate traffic spikes with deployments.
What Traffic shows
| Metric | Description |
|---|---|
| Request rate | Requests per second or per minute over a selected time window. |
| Response time (P50 / P95 / P99) | Latency percentiles — how long requests take at the median, 95th, and 99th percentile. |
| Status code distribution | Breakdown of 2xx, 3xx, 4xx, and 5xx responses. A rising 5xx rate indicates server errors in the app. |
| Request log | Per-request stream with method, path, status code, response time, and client information. |
Interpreting response time percentiles
- P50 (median) — half of all requests complete in this time or less. A good baseline for normal performance.
- P95 — 95% of requests complete within this time. Represents most users' experience.
- P99 — the slowest 1% of requests. High P99 with normal P50 usually means a specific endpoint or query is slow for some requests.
Common patterns
Traffic spike with CPU spike
A sudden rise in request rate that matches a CPU spike in Monitoring indicates genuine load increase rather than a bug. Evaluate whether your resource plan needs to scale.
Rising 5xx responses
A 5xx rate increase without a traffic increase usually means:
- A recent deployment introduced a bug → check Logs → Runtime
- A dependency (database, external API) is unavailable → check Project Monitoring
- A memory OOM condition is killing the container → check memory in Monitoring
High latency on specific paths
If P95 is high but P50 is normal, a specific route may be slow. Check the per-request log and filter by path to identify the offending endpoint.
Traffic and the reverse proxy
All traffic to a Skytells app passes through the Skytells reverse proxy before reaching the container. The proxy handles:
- TLS termination (HTTPS)
- Custom domain routing
- DDoS protection (shown in the Firewall widget on App Overview)
The Traffic page reflects requests as seen by the reverse proxy — after TLS termination, before they reach the container.
Related
- Monitoring — CPU and memory resource metrics.
- Logs — per-request log output from the app process.
- App Overview — Firewall widget showing protection status.
How is this guide?
Monitoring
View real-time and historical container metrics for a Skytells app — CPU usage, memory consumption, and container health over time.
Schedules
Create and manage cron-style scheduled jobs attached to a Skytells app — define recurring tasks that run on a fixed schedule inside your app's container.