K6 quality of life updates (#10985)

* add k6 docs; improve conf file

* Update collectors/statsd.plugin/k6.md

Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>

* Update collectors/statsd.plugin/k6.md

Co-authored-by: Joel Hans <joel.g.hans@gmail.com>

* Update collectors/statsd.plugin/k6.md

Co-authored-by: Joel Hans <joel.g.hans@gmail.com>

* Update collectors/statsd.plugin/k6.md

Co-authored-by: Joel Hans <joel.g.hans@gmail.com>

* Update collectors/statsd.plugin/k6.md

Co-authored-by: Joel Hans <joel.g.hans@gmail.com>

* Update collectors/statsd.plugin/k6.md

Co-authored-by: Joel Hans <joel.g.hans@gmail.com>

* change list to headings

* add k6 to statsd readme

* fix avg type

* Update collectors/statsd.plugin/README.md

Co-authored-by: Joel Hans <joel.g.hans@gmail.com>

* Update collectors/statsd.plugin/README.md

Co-authored-by: Joel Hans <joel.g.hans@gmail.com>

* Update collectors/statsd.plugin/README.md

Co-authored-by: Joel Hans <joel.g.hans@gmail.com>

* Update collectors/statsd.plugin/README.md

Co-authored-by: Joel Hans <joel.g.hans@gmail.com>

* Update collectors/statsd.plugin/k6.md

Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>

Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Co-authored-by: Joel Hans <joel.g.hans@gmail.com>

collectors/statsd.plugin/README.md

@@ -19,6 +19,17 @@ Since statsd is embedded in Netdata, it means you now have a statsd server embed
 
 Netdata statsd is fast. It can collect more than **1.200.000 metrics per second** on modern hardware, more than **200Mbps of sustained statsd traffic**, using 1 CPU core. The implementation uses two threads: one thread collects metrics, another one updates the charts from the collected data.
 
+# Available StatsD collectors
+
+Netdata ships with collectors implemented using the StatsD collector. They are configuration files (as you will read bellow), but they function as a collector, in the sense that configuration file organize the metrics of a data source into pre-defined charts. 
+
+On these charts, we can have alarms as with any metric and chart.
+
+- [K6 load testing tool](https://k6.io)
+  - **Description:** k6 is a developer-centric, free and open-source load testing tool built for making performance testing a productive and enjoyable experience.
+  - [Documentation](/collectors/statsd.plugin/k6.md)
+  - [Configuration](https://github.com/netdata/netdata/blob/master/collectors/statsd.plugin/k6.conf)
+
 ## Metrics supported by Netdata
 
 Netdata fully supports the StatsD protocol. All StatsD client libraries can be used with Netdata too.

collectors/statsd.plugin/k6.conf

@@ -6,6 +6,7 @@
 
 [dictionary]
     http_reqs = HTTP Requests
+    http_reqs_failed = Failed HTTP Requests
     vus = Virtual active users
     vus_max = max Virtual active users
     iteration_duration = iteration duration
@@ -19,7 +20,7 @@
     http_req_receiving = Receiving HTTP requests
     http_req_waiting = Waiting HTTP requests
     http_req_duration_median = Median HTTP req duration
-    http_req_duration_average = AVG HTTP req duration
+    http_req_duration_average = Avg HTTP req duration
     http_req_duration = HTTP req duration
     http_req_duration_max = max HTTP req duration
     http_req_duration_min = min HTTP req duration
@@ -30,13 +31,22 @@
 
 [http_reqs]
     name = http_reqs
-    title = HTTP Requests
+    title = HTTP Requests rate
     family = http requests
     context = k6.http_requests
     dimension = k6.http_reqs http_reqs last 1 1 sum
     type = line
     units = requests/s
 
+[http_reqs]
+    name = http_reqs_failed
+    title = Failed HTTP Requests rate
+    family = http requests
+    context = k6.http_requests
+    dimension = k6.http_reqs_failed http_reqs_failed last 1 1 sum
+    type = line
+    units = requests/s
+
 [vus]
     name = vus
     title = Virtual Active Users
@@ -53,7 +63,7 @@
     dimension = k6.iteration_duration iteration_duration last 1 1 
     dimension = k6.iteration_duration iteration_duration_max max 1 1 
     dimension = k6.iteration_duration iteration_duration_min min 1 1 
-    dimension = k6.iteration_duration iteration_duration_avg avg 1 1 
+    dimension = k6.iteration_duration iteration_duration_avg average 1 1 
     type = line
     units = s
 
@@ -74,31 +84,27 @@
     units = kb/s
     type = area 
 
-[http_req_status]
-    name = http_req_status
-    title = Time spent on HTTP 
-    family = http requests
-    dimension = k6.http_req_blocked http_req_blocked last 1 1 
-    dimension = k6.http_req_connecting http_req_connecting last 1 1
-    units = ms
-    type = line
-    
 [http_req_duration_types]
     name = http_req_duration_types
-    title = Time spent on HTTP connection states
+    title = HTTP Requests total duration
     family = http requests
     dimension = k6.http_req_sending http_req_sending last 1 1
     dimension = k6.http_req_waiting http_req_waiting last 1 1
     dimension = k6.http_req_receiving http_req_receiving last 1 1
+    dimension = k6.http_req_blocked http_req_blocked last 1 1 
+    dimension = k6.http_req_connecting http_req_connecting last 1 1
     units = ms
     type = stacked
 
 [http_req_duration]
     name = http_req_duration
-    title = Total time for HTTP request
+    title = HTTP duration metrics
     family = http requests
     dimension = k6.http_req_duration http_req_duration_median median 1 1 
     dimension = k6.http_req_duration http_req_duration_max max 1 1
-    dimension = k6.http_req_duration http_req_duration_average avg 1 1
+    dimension = k6.http_req_duration http_req_duration_average average 1 1
     dimension = k6.http_req_duration http_req_duration_min min 1 1
-    dimension = k6.http_req_duration httP_req_duration_p95 percentile 1 1
+    dimension = k6.http_req_duration http_req_duration_p95 percentile 1 1
+    dimension = k6.http_req_duration http_req_duration last 1 1
+    units = ms
+    type = line

collectors/statsd.plugin/k6.md

@@ -0,0 +1,72 @@
+<!--
+title: "K6 load test monitoring with Netdata"
+custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/stats.d.plugin/k6.md
+sidebar_label: "K6 Load Testing"
+-->
+
+# K6 Load Testing monitoring with Netdata
+
+Monitors the impact of load testing experiments performed with [K6](https://k6.io/).
+
+You can read more about the metrics that K6 sends in the [K6 documentation](https://k6.io/docs/using-k6/metrics/). 
+
+## Requirements
+
+-   When running the k6 experiment, specify a [StatsD output](https://k6.io/docs/results-visualization/statsd/).
+    -   Tip: K6 currently supports tags only with [datadog output](https://k6.io/docs/results-visualization/datadog/), which is in essence StatsD. Netdata can be used with both.
+
+## Metrics
+
+### HTTP Requests
+ 
+Number of HTTP requests that K6 generates, per second.
+
+### Failed HTTP Requests
+
+Number of failed HTTP requests that K6 generates, per second.
+
+### Virtual Active Users
+Current number of active virtual users.
+
+### Iteration Duration
+
+The time it took K6 to complete one full iteration of the main function.
+
+### Dropped Iterations
+
+The number of iterations that could not be started either due to lack of Virtual Users or lack of time.
+
+### Data
+
+The amount of data received and sent.
+
+### TTP Requests total duration
+   
+The total duration it took for a round-trip of an HTTP request. It includes:
+- Blocked HTTP requests: time spent blocked before initiating the request
+- Connecting HTTP requests: time spent establishing TCP connection to the remote host
+- Sending HTTP requests: time spent sending data to the remote host
+- Receiving HTTP requests: time spent receiving data from the remote host
+- Waiting HTTP requests: time spent waiting for response from the remote host
+
+### HTTP duration metrics
+
+Different metrics on the HTTP request as defined by K6. The HTTP request duration is defined by K6 as: `HTTP sending request` + `HTTP receiving request` + `HTTP waiting request`. 
+
+Metrics:
+- Median
+- Average
+- Max
+- Min
+- 95th percentile
+- absolute (the value as it is, without any computation)
+
+## Configuration
+
+The collector is preconfigured and defined in `statsd.plugin/k6.conf`.
+
+Due to being a StatsD collector, you only need to define the configuration file and then send data to Netdata using the StatsD protocol.
+
+If Netdata is running on the same machine as K6, no further configuration is required. Otherwise, you will have to [point K6](https://k6.io/docs/results-visualization/statsd/) to your node and make sure that the K6 process can reach Netdata.
+
+The default namespace that is used in the configuration is `k6`. If you change it in K6, you will have to change it as well in the configuration file `k6.conf`.