From b6e3886aab99ec21702bb2e41a8702c806bfc8f2 Mon Sep 17 00:00:00 2001
From: Ivan <2103732+codebien@users.noreply.github.com>
Date: Tue, 16 Jan 2024 16:08:32 +0100
Subject: [PATCH] Changelog for the report updates (#3546)

Changelog for the data collection updates
---
 release notes/v0.49.0.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/release notes/v0.49.0.md b/release notes/v0.49.0.md
index fe0dc1c7c45..a25adc7ab9f 100644
--- a/release notes/v0.49.0.md	
+++ b/release notes/v0.49.0.md	
@@ -157,9 +157,10 @@ Thanks to @Azhovan! :bow: :tada:
 
 ### Collect usage data on imported internal modules and outputs [#3525](https://github.com/grafana/k6/pull/3525)
 
-// TODO fill with info
-
+Added the data collection of the used modules and outputs when the [usage report](https://grafana.com/docs/k6/latest/misc/usage-collection) is enabled. The data collection is only related to the built-in k6 modules and outputs. Private, custom modules and extensions [are never collected](https://github.com/grafana/k6/blob/f35e67902605877ebf2c5e9c8673cd7faf4cdc1e/cmd/report.go#L33-L57). The usage report is enabled by default in k6, but it is possible to opt-out using the [no-usage-report](https://grafana.com/docs/k6/latest/using-k6/k6-options/reference/#no-usage-report) option.
 
+We always want to improve the product, but at the same time we need to pay attention where we allocate our resources. Having data of what are the most used modules and outputs give us a better confidence to make decisions because we are supported by data.
+It will let us know what is the percentage of our users that will benefit from the introduction of a new feature and on the other side, in case of a breaking change, how many of them would be impacted.
 
 ## UX improvements and enhancements