From a1831934b7240a4a76a43539aa83abb4683c53c8 Mon Sep 17 00:00:00 2001 From: Pepe Cano <825430+ppcano@users.noreply.github.com> Date: Wed, 7 Feb 2024 11:14:22 +0100 Subject: [PATCH] Update docs/sources/next/examples/error-handler.md Co-authored-by: Heitor Tashiro Sergent --- docs/sources/next/examples/error-handler.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/next/examples/error-handler.md b/docs/sources/next/examples/error-handler.md index 07ed5db136..9b1a6cfece 100644 --- a/docs/sources/next/examples/error-handler.md +++ b/docs/sources/next/examples/error-handler.md @@ -13,7 +13,7 @@ In k6, there are two common approaches to store additional error information: - Console logs and output [k6 logs to Loki](https://k6.io/blog/using-loki-to-store-and-query-k6-logs/), a file, or use [Grafana Cloud k6](https://grafana.com/docs/grafana-cloud/k6/analyze-results/inspect-test-results/inspect-logs/). - Using [Tags](https://grafana.com/docs/k6//using-k6/tags-and-groups/) in a [custom counter metric](https://grafana.com/docs/k6//using-k6/metrics/create-custom-metrics) to track error data. -When deciding what error data to store, consider whether it is an general or specific error, and be aware that high-load tests may generate a substantial volume of error data. +When deciding what error data to store, consider whether it's a general or specific error, and be aware that high-load tests may generate a substantial volume of error data. Below is an example using an `ErrorHandler` class to log error information. It accepts a callback that instructs how to log errors. The example provides instructions for both previously mentioned options: console logs and custom metrics.