Application Metrics
Track how your deployed applications are performing inside Devpilot, including response times, request volume, active users, and error rates.
The Application Metrics view in Devpilot gives you a workspace-wide read on how your deployed applications are behaving at runtime. It is the companion to the Infrastructure view: where infrastructure tells you how your servers are holding up, application metrics tell you how your apps on top of them are performing.
You open it from the sidebar under Monitoring > Application, at the route /dashboard/monitoring/application.
What you see today
The current application metrics dashboard focuses on four headline KPIs, each shown as a tile with its current value and a short-term trend badge.
| Metric | What it tells you |
|---|---|
| Response Time | The average time your apps take to return a response to a request. Lower is better. |
| Requests/min | How much traffic your apps are receiving right now. Useful for spotting traffic spikes, launches, or sudden drop-offs. |
| Active Users | How many distinct users are interacting with your apps over the recent window. |
| Error Rate | The percentage of requests that returned an error. A rising error rate is usually the first signal that a recent deployment introduced a regression. |
Each tile also shows a delta compared to the previous period (for example "-12ms" on response time, or "+145" on requests/min) so you can tell at a glance whether things are improving or getting worse.
The Application Metrics page is a high-level dashboard. For per-error drill-down, use Monitoring > Error Tracking. For per-request diagnostic output from your deployment pipeline, use Monitoring > Logs.
How it ties into your deployments
Devpilot correlates these metrics with your deployment history so you can answer the most common operational question: did my last release make things better or worse?
Deploy a change. When you push a new deployment from Git, script, or package flow, Devpilot records a deployment row with its commit, branch, start/end time, duration, and final status.
Watch the metrics shift. After the deployment goes live, the Application Metrics tiles update. A spike in error rate or response time immediately after a deploy is a strong signal that the release introduced a regression.
Follow the deployment insights. Devpilot also generates deployment insights (severity, category, health score, recommended action) that surface on your app's deployment page. Use these to decide whether to roll back, hotfix, or keep shipping.
Deployment success rate
The success/failure status of every deployment is tracked against each app. Over time this gives you a rolling success rate: the fraction of deployments that completed without errors versus those that were cancelled, failed, or rolled back.
You can see the per-deployment breakdown on each app's Deployments page, including:
- Commit id, branch, and committer for each deploy.
- Start time, end time, and total duration.
- Final status (success, failed, cancelled, rolled back).
- Whether the deployment is currently Live.
- The deployment that a rollback was triggered from, if applicable.
Combined with the error rate on the Application Metrics dashboard, this is the view you use to decide whether a particular app is in a healthy release cadence or needs attention.
Error trends
The Error Rate tile on the Application Metrics dashboard is your early-warning indicator. It shows the percentage of requests that returned an error in the current window, along with the change compared to the previous window.
To investigate the errors themselves, open Monitoring > Error Tracking. There you can see individual error events, grouped errors (same stack trace across many requests), trend charts, and filters by severity or resolution state. You can also resolve or ignore an error group from that page.
Application Metrics currently shows aggregate KPIs for the workspace. Per-app breakdowns, historical charts, and user-session analytics are on the roadmap. Until they ship, use the per-app Deployments and Error Tracking pages for deeper drill-down.
Suggested workflow
A typical way to use the Application Metrics page day-to-day:
Glance at the four tiles when you first open the dashboard in the morning. If response time, error rate, or request volume look unusual, dig deeper.
Cross-check with recent deployments. Open Monitoring > Activity Logs or the app's deployment history to see whether a recent release lines up with the change.
Triage errors in Error Tracking. Mark the ones you have fixed as resolved and silence the ones you are deliberately ignoring so the signal stays clean.
Confirm the fix worked. After your next deployment, come back to Application Metrics and verify error rate is back to baseline.
Next steps
Infrastructure Metrics
See how your servers are holding up under the traffic your apps are serving.
Error Tracking
Drill into individual errors, group them, and mark them resolved.
Alerts
Get notified when a metric crosses a threshold you care about.
Activity Logs
See who did what in the workspace, including deployment triggers.
Monitoring Overview
Understand the monitoring features available in Devpilot, including server metrics, quota alerts, activity logs, deployment failure patterns, and webhook delivery logs.
Infrastructure Metrics
Monitor the health of the servers in your Devpilot workspace, including CPU, memory, disk, network, and uptime for your full server fleet.