Skip to content

Commit 1346518

Browse files
inancgumusheitortsergentjoanlopez
committed
k6browser: too many time series improve the text
Co-authored-by: Heitor Tashiro Sergent <[email protected]> Co-authored-by: Joan López de la Franca Beltran <[email protected]>
1 parent 47711c1 commit 1346518

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/sources/k6/next/using-k6-browser/recommended-practices/preventing-too-many-time-series-issue.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
---
2-
title: 'Preventing too many time series issue'
2+
title: 'Prevent too many time series error'
33
description: 'A guide on how to prevent the `too many time series` issue when using k6 browser.'
44
weight: 05
55
---
66

77
# Preventing too many time series issue
88

9-
Modern websites are complex and make a large number of requests to function as intended by their developers. These requests no longer serve only content for display to the end user but also retrieve insights, analytics, advertisements, and cache-busting purposes. Such requests are usually generated dynamically and may contain frequently changing IDs, posing challenges when correlating and analyzing your K6 test results.
9+
Modern websites are complex and make a large number of requests to function as intended by their developers. These requests no longer serve only content for display to the end user but also retrieve insights, analytics, advertisements, and cache-busting purposes. Such requests are usually generated dynamically and may contain frequently changing IDs, posing challenges when correlating and analyzing your k6 test results.
1010

11-
When load testing a website using the k6 browser module, these dynamic requests can result in a high number of similar-looking requests, making it difficult to correlate them and extract valuable insights. This can also lead to test errors, such as a _too-many-metrics_ error, due to high cardinality from metrics tagged with similar but dynamically changing URLs.
11+
When load testing a website using the k6 browser module, these dynamic requests can result in a high number of similar-looking requests, making it difficult to correlate them and extract valuable insights. This can also lead to test errors, such as a `too-many-metrics` error, due to high cardinality from metrics tagged with similar but dynamically changing URLs.
1212

1313
This issue also affects synthetic tests. While you may not encounter the _too-many-metrics_ error, you may end up with a large amount of uncorrelated metric data that cannot be tracked effectively over time.
1414

15-
To address this in the browser module has a [page.on('metric')](https://grafana.com/docs/k6/<K6_VERSION>/javascript-api/k6-browser/page/on) method, which allows you to define URL patterns using regex for matching. When a match is found, the URL and name tags for the metric are replaced with the new name.
15+
To address this, the browser module has a [page.on('metric')](https://grafana.com/docs/k6/<K6_VERSION>/javascript-api/k6-browser/page/on) method, which allows you to define URL patterns using regex for matching. When a match is found, the URL and name tags for the metric are replaced with the new name.
1616

1717
## Example usage
1818

0 commit comments

Comments
 (0)