Usage & Analytics
Track PDF volume, render performance, reliability, capacity, storage, bandwidth, and per-template health from the BladePDF dashboard.
Where to look
| Dashboard area | Use it for |
|---|---|
| Dashboard | A current snapshot of generation volume, average render time, success rate, plan usage, recent renders, and live utilization. |
| Analytics | Deeper trends for volume, latency percentiles, failures, capacity pressure, activity patterns, and template performance. |
| Renders & Logs | Individual requests, statuses, timings, logs, references, and failure investigation. |
| Billing & Plans | Current billing-period usage, plan limits, queue capacity, alerts, and upgrade options. |
Key metrics
| Metric | What it tells you |
|---|---|
| Total PDFs | Generation volume for the selected reporting period. |
| Render latency | Typical and tail performance through p50, p95, and p99 timings. |
| Success rate | The share of renders that completed successfully versus failed requests. |
| Bytes served | Total PDF output transferred across renders. |
| Storage used | Space consumed by stored PDFs, templates, and managed assets. |
Volume and reliability
Use the generation chart to compare current activity with the previous period and switch between volume, output bytes, and failures. The success-rate view separates successful and failed renders so a change in reliability is visible before it becomes a support issue.
When a failure spike appears, move to Renders & Logs and inspect the first failed requests in that time window. Start with the earliest warning or error instead of the final exception alone.
Capacity and queue pressure
The capacity section shows concurrency utilization, queue wait percentiles, queue pressure, and rejected requests. Reaching full concurrency does not necessarily mean a failure: work can wait in the queue until a render slot becomes available. Sustained queue growth or rejected requests are the stronger signals that the current plan is undersized.
See Limits & Concurrency for the request lifecycle and plan-limit behavior.
Template and activity insights
The template leaderboard compares render volume, average latency, p99 latency, success rate, and output bytes per template. Use it to find high-volume templates where a small optimization has the largest effect, or low-reliability templates that need focused investigation.
The activity heatmap shows when render traffic arrives by day and hour. This is useful for recognizing scheduled workloads, traffic bursts, and the periods when extra concurrency would matter most.
A practical review workflow
- Check total volume and success rate for an unexpected change.
- Review p95 and p99 latency rather than relying only on the average.
- Check queue wait and rejected requests to separate rendering time from capacity pressure.
- Use the template leaderboard to isolate the affected document type.
- Open individual renders and logs for the root cause.