> For the complete documentation index, see [llms.txt](https://docs.perfagents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perfagents.com/user-guide/load-test-orchestration/load-test-dashboard.md). # Load Test Dashboard The Load Test Dashboard provides a centralized view of all load testing activities within a selected project. It gives instant visibility into test executions, system performance trends, and infrastructure utilization. This dashboard is accessible via the Dashboard section. It updates dynamically based on the selected organization, project, and time range (e.g., Last 7 Days). {% embed url="" %} ### Layout Structure The Load Testing Dashboard consists of: 1. Summary Metric Cards (Top Section) 2. Top Load Tests List 3. Recent Runs 4. Test Activity Graph 5. Test Run Count Graph 6. Time Range Filter ### Summary Metrics (Top Section) The top row displays high-level KPIs for quick performance insights:
MetricDescriptionPurpose
Active Test Number of currently running tests vs. completed tests. Helps identify whether load tests are actively executing.
Total Runs (Last 7 Days) Total number of test executions during the selected time period. Tracks testing frequency and adoption trends.
Failed Load Tests Number of failed executions. Provides immediate visibility into stability and execution health.
Total LG-Hours Virtual User (VU) consumption and percentage of allocated capacity used. Tracks plan usage and resource efficiency.
Average Completion Rate Average success rate across executed tests. Helps measure overall reliability of test executions.
### Top Load Tests List & Recent Runs These panels highlight the most frequently executed tests and the most recent executions, providing a quick snapshot of current performance activity. #### Test Activity & Run Count Graphs These visual trend charts display: 1. **Test Activity Graph:** Daily test runs and Success Rate over time, helping to assess if reliability is improving or declining. 2. **Test Run Count Graph:** Historical view of test frequency and operational discipline. ### Time Range Filter Located in the top-right, this filter allows users to adjust the time range (default: Last 7 Days) to analyze weekly or monthly trends. ### How to Use This Dashboard Effectively The Load Testing Dashboard is designed for: 1. **Engineering Teams:** To track execution frequency and identify test failures. 2. **Performance Teams:** To evaluate load test stability and monitor VU utilization. 3. **Leadership / Stakeholders:** To get a high-level snapshot of testing activity and assess reliability trends. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.perfagents.com/user-guide/load-test-orchestration/load-test-dashboard.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.