分析性能结果

仪表板提供了多个图表和状态指示器，可帮助您确定应用程序和基础架构是否满足预期性能水平。

• The Users chart displays the number of active virtual users over time and overlays additional key metrics such as automation errors, response times, and HTTP errors. This allows you to quickly identify correlations, for example, if higher load coincides with increased errors or slower response times.
• 基础架构图表显示执行负载（Serverless Load Generator 或本地计算机）的 Robot 的 CPU 和内存消耗。监控这些指标有助于确保任何性能问题都是由系统处于压力下引起的，而不是由机器人基础架构超载引起的。
• 组卡 - 每个组卡都简要概述了负载组的执行状态和关键指标。
  • Group name and test case name. The group name cannot be changed.
  • Status (no result, Passed or Failed). The status is determined automatically based on threshold compliance, but it can also be manually adjusted. This allows test owners to override results if they believe a group should be considered successful despite minor violations or marked as failed if business-critical expectations were not met.
  • Number of virtual users executed. This metric shows a full bar after it is fully completed.
  • Error rates (HTTP and automation errors)
  • 平均响应时间和最长响应时间

要查看HTTP错误和自动化错误，请执行以下操作：

1. Open an execution and select a view of interest from the Users charts or the Infrastructure charts.
2. Perform a selection in the view of interest (HTTP errors or Automation errors).
3. Consult the errors in the Web Traffic section and the Automation Errors section.

The dashboard view helps you quickly assess whether a group met its defined service level objectives (SLOs). For deeper analysis, you can open the Group Metrics view, which provides detailed charts on response times, error rates, step durations, and infrastructure usage.

通过使用详细信息视图，可以深入了解性能测试期间发生的特定事件。

• Selecting a timeframe and chart To open the detail view, first select a time range in the histogram and then choose a specific chart (e.g., HTTP response times, errors). The detail view will show relevant entries for the selected timeframe.
• HTTP request/response pairs The table lists all HTTP requests executed by the load group, including their name, type, response time, and status code.
  • 如果请求返回错误代码（例如 404、500），则会将其标记为错误。
  • 如果请求返回有效代码（例如 200），但超过响应时间阈值，则也会在此处报告。每个条目前面的数字表示问题发生的次数。
• Automation errors The same detail view can also be used to display automation-level errors such as selector failures or activity exceptions. These provide visibility into functional problems that may occur under load.

通过结合使用错误代码、阈值违规和自动化日志，详细信息视图有助于查明测试场景中性能或功能故障的根本原因。