fixed documentation #2169
fixed documentation #2169
Conversation
|
|
Codecov Report
@@ Coverage Diff @@
## master #2169 +/- ##
==========================================
+ Coverage 72.71% 72.73% +0.01%
==========================================
Files 184 184
Lines 14571 14577 +6
==========================================
+ Hits 10596 10602 +6
Misses 3333 3333
Partials 642 642
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
| @@ -374,7 +374,7 @@ You can save the above example as a local file and run it, or you can also run i | |||
|
|
|||
| To make full use of your test results and to be able to fully explore and understand them, k6 can output the raw metrics to an external repository of your choice. | |||
|
|
|||
| The simplest output option, meant primarily for debugging, is to send the JSON-encoded metrics to a file or to `stdout`. Other output options are sending the metrics to an InfluxDB instance, an Apache Kafka queue, or even to the k6 cloud. This allows you to run your load tests locally or behind a company firewall, early in the development process or as a part of a CI suite, while at the same time being able store their results in the k6 cloud, where you can compare and analyse them. You can find more information about the available outputs [here](https://k6.io/docs/getting-started/results-output) and about k6 Cloud Results [here](https://k6.io/docs/getting-started/results-output/cloud) and [here](https://k6.io/docs/cloud/analyzing-results/overview). | |||
| The simplest output option, meant primarily for debugging, is to send the JSON-encoded metrics to a file or to `stdout`. Other output options are sending the metrics to an InfluxDB instance, an Apache Kafka queue, or even to the k6 cloud. This allows you to run your load tests locally or behind a company firewall, early in the development process or as a part of a CI suite, while at the same time being able to store their results in the k6 cloud, where you can compare and analyse them. You can find more information about the available outputs [here](https://k6.io/docs/getting-started/results-output) and about k6 Cloud Results [here](https://k6.io/docs/getting-started/results-output/cloud) and [here](https://k6.io/docs/cloud/analyzing-results/overview). | |||
There was a problem hiding this comment.
Tiny suggestion:
is to send the JSON-encoded metrics to a file or to stdout.
So:
is to send the JSON-encoded metrics to a file or stdout.
|
Thank you for your contribution, @marooncoder09. We would love to send you a little swag pack as a token of our appreciation. Please get in touch with me via floor[@]grafana.com! |
Thank You @FloorD Loved to be the part of this organisation can you please elaborate a further how can I reach you ? |
Fixed Grammatical and punctuational errors in the README.md file