1、jp@gc - Actiive Threads Over Time：不同時間活動用戶數量展示（圖表）
2、jp@gc - AutoStop Listener ：自動停止監聽器
average Response Time is greater than 10000ms for 10 seconds ：連續10s平均響應時間大於10000ms就停止測試。
average Latency is greater than 5000ms for 10 seconds ：連接10s平均等待時間大於5000ms就停止測試。
Error Rate is greater than 50% for 10 seconds ：10s內錯誤率一直高於50％就停止測試。
3、jp@gc - Bytes Throughput Over Time:不同時間吞吐量展示（圖表）（聚合報告里，Throughput是按請求個數來展示的，比如說1.9/sec，就是每s發送1.9個請求； 而這里的展示是按字節Bytes來展示的圖表）
4、jp@gc - Composite Graph： 混合圖表
在它的Graphs里面可以設置多少個圖表一起展示，它可以同時展示多個圖表
5、jp@gc - Console Status Logger：一些log的設置。
This is a simple listener that prints short summary log to console while JMeter is running in non-GUI mode. It also writes the same info into jmeter.log in GUI mode.
Note that response time and latency values printed are averages.
6、jp@gc - Flexible File Writer：這個插件允許你靈活記錄測試結果
Filename：結果記錄的地方
Overwirte existing file：是否覆蓋這個文
Ｗrite File Header：文件的頭(即文件的第一行)
Record each sample：如何記錄不同的sample（記錄哪些內容，用什么順序，如何隔開不同的值）
Write File Footer：文件的結尾（即文件的最后一行)
| startTime | epoch time when request was started |
| endTime | epoch time when reading response ended |
| responseTime | response time, time to full response loaded |
| latency | latency, time to first response byte received (if available) |
| responseCode | response code (200, 404 etc.) |
| responseMessage | response message (OK, Not Found etc.) |
| responseHeaders | response headers (if present in sample) |
| responseData | response data |
| requestData | request data from sample |
| sentBytes | number of request bytes sent, if available |
| receivedBytes | number of request bytes sent (if available) |
| threadName | name of thread in Thread Group that processed request |
| sampleLabel | name of the sampler that made request |
| isSuccsessful | is response was marked as successful |
| isFailed | is response was marked as failed (surrogate field) |
| startTimeMillis | same as startTime, but divided by 1000 (surrogate field, example: 1311121131.362) |
| endTimeMillis | same as endTime, but divided by 1000 (surrogate field) |
| responseTimeMicros | same as responseTime, but multiplied by 1000 (surrogate field) |
| latencyMicros | same as latency, but multiplied by 1000 (surrogate field) |
| variable#<N> | Sample variable with index N, see below for details |
7、jp@gc - Hits per Second：每秒點擊量
8、jp@gc - Loadosophia.org Uploader：This is special plugin in for uploading results to Loadosophia.org immediately after test end.
9、jp@gc - Page Data Extractor：以圖表的形式展示頁面上你想得到的一些結果，它以正則表達式的形式獲取key和vale。（下面的ｋｅｙ和ｖａｌｕｅ的正則表達式以括號標志）
10、jp@gc - PerfMon Metrics Collector：服務器性能監測控件，包括ｃｐｕ,ｍｅｍｏｒｙ,ｎｅｔｗｏｒｋ Ｉ/Ｏ等等。（JMeter cannot retrieve by default server metrics except Tomcat ones.：就是ｊｍｅｔｅｒ只能監控ｔｏｍｃａｔ的主機）（前提是要先在服務器上ｓｔａｒｔＡｇｅｎｔ,即把插件解壓到服務器上，運行ｓｔａｒｔＡｇｅｎｔ）
11、jp@gc - Reponse Codes per Second：This graph will display the response code per second returned during the test.
12、jp@gc - Reponse Latencies Over Time：This graph will display the response latencies during the load test. A latency is the duration between the end of the request and the beginning of the server response.（就是記錄客戶端發送請求完成后，服務器端返回請求之前這段時間）
13、jp@gc - Reponse Times Distribution：This graph will display the response time distribution of the test. The X axis shows the response times grouped by interval, and the Y axis the number of samples which are contained in each interval.
14：jp@gc - Respose Times Over Time：This graph will display for each sampler the average response time in milliseconds.
15、jp@gc - Response Times Percentiles：This graph will display the percentiles for the response time values. X Axis represents percentage, Y Axis Response time values. One point (P, Value) means for the whole scenario, P percent of the values are bellow Value ms.（沒太明白）
16：jp@gc - Response Times vs Threads：This graph shows how Response Time changes with amount of parallel threads. Naturally, server takes longer to respond when a lot of users requests it simultaneously. This graph visualizes such dependencies.
17：jp@gc - Transaction Throughput vs Threads：This listenter is very similar to Response Times vs Threads, exept it shows total server's transaction throughput for active test threads.
18、jp@gc - Transactions per Second：This graph shows the number of transactions per second for each sampler. It counts for each seconds the number of finished transactions.