![]() ![]() ![]() In other terminology, these metrics measure traffic (in requests), availability (in error rate), and latency (in request duration). However, if you're not sure what metrics to focus on, a good place to start is with the metrics that measure the requests, errors, and duration (the criteria of the RED method). So the best metric for your analysis depends on your goals. Key metrics to visualizeīefore reading more, ask yourself what the goal of your test is.Įach metric provides a different perspective on the performance of the test. If you're new to visualization or performance testing, this section explains the key metrics to visualize, and provides some general advice about the visual indicators of system performance. Guidelines to visualize performance test results You have many ways to visualize k6 test results. K6 is also extensible, so if the built-in outputs don't suit your needs, you can develop an output extension that does. K6 provides much flexibility to present the data in the way that makes the most sense for your test goals and work environment.Īt the most accessible level, you can turn the end-of-test results into a graphical overview or visualize the CSV output with a spreadsheet.īeyond that, you can stream results in some structured format, such as Prometheus remote write, and visualize the stream in some frontend tool, such as Grafana. This output can become the input for different storage backends and visualization tools. When the volume of test metrics is high, visualization is one of the most valuable tools for performance-test analysis.įortunately, in addition to emitting many metrics, k6 also has many output formats. However, an abundance of data can be overwhelming. More metrics means more data to analyze, and more chances to find and correlate performance degradations. An overview of ways to use k6 output formats to visualize results in different services. ![]() Guidelines to choose the metrics to focus on and visualize. ![]()
0 Comments
Leave a Reply. |