You are here:
View and Compare Org Performance Metrics
Monitor and analyze your org's performance in Scale Center.
View a snapshot of your org's performance metrics over a defined time range, or compare two time ranges. Ranges longer than 12 hours can take several minutes to load.
- From Setup, enter Scale Center in the Quick Find box, then click Org Performance.
- Select a time range.
- To compare two time ranges from the last 30 days, select Compare. The first range is the baseline. The second is the comparison.
- Click Submit to load time series charts for each metric.
- Click to toggle a metric, or double-click to isolate it.
-
Click and drag any chart to select a time range and open an analysis.
When Concurrent Apex Errors are elevated, drag a spike in its chart to open the Concurrent Apex report. The report surfaces potential causes (throttling, schema, or deployment invalidation) and shows time distribution for long-running transactions. If significant time is at the database layer, focus on SOQL and DML optimization. The report lists the top five contributing operations by type (Insert, Update, and Delete). Apply indexed fields and appropriate filters first. Entry points display as Critical, Major, or Minor. Columns in red mark the dominant layer. For deeper investigation, turn on Debug Logs with Finest Mode and reproduce the triggering use case. Then, open the Apex Log Analyzer and check the Analysis tab. To resolve row lock contention, review your data model, audit
FOR UPDATEusage, and batch large transactions.
| Metric | Definition |
|---|---|
| Successful Logins | Total successful logins. |
| Failed Logins | Total unsuccessful logins. An unusually high count can indicate network problems. |
| Concurrent Apex Errors | Synchronous Apex requests that exceeded 5 seconds and the concurrent request governor limit. The limit is based on license type and count (minimum 10, cap of 50) and exists to prevent service disruptions and prolonged page load times. Exceeding it causes unrecoverable runtime exceptions. Common causes include inefficient SOQL, excessive concurrent DML, high-CPU Apex code, and schema or metadata changes that invalidate caches. |
| Concurrent UI Errors | UI requests that exceeded 10 seconds and governor limits. Common causes include multiple dashboard refreshes and long-running reports. To learn more, see Proactive Alert Monitoring: Concurrent UI Errors. |
| Row Lock Errors | Exceptions from simultaneous attempts to update the same record. Common causes: parent-child data skew, failed API or Apex triggers, and Email-to-Case timeouts. To learn more, see Proactive Alert Monitoring: Rowlock Timeout Errors. |
| Total Callout Errors | Errors from callouts to external or managed packages. |

