You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: usage.md
+14-12
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,13 @@ subtitle: Help us make Quarkus even better, anonymously.
5
5
permalink: /usage/
6
6
---
7
7
8
-
## Why does Quarkus want to gather usage analytics?
8
+
## Why does Quarkus want to gather usage analytics?
9
9
10
10
Usage analytics (telemetry collection) is invaluable for the Quarkus team and contributors to gauge which operating systems, java version, build systems, extensions and more are used. This service is provided by Red Hat and the details can be found on [usage policy](/usage/policy) page.
11
11
12
12
## How will this work?
13
13
14
-
In order to get this information, beginning in Quarkus 3.2, when you run Quarkus the first time in dev mode (`quarkus dev`, `mvn quarkus:dev`, etc.) you get asked if you agree to contribute anonymous build data to the Quarkus community.
14
+
In order to get this information, beginning in Quarkus 3.2, when you run Quarkus the first time in dev mode (`quarkus dev`, `mvn quarkus:dev`, etc.) you get asked if you agree to contribute anonymous build data to the Quarkus community.
@@ -25,29 +25,31 @@ We will share what is learned from these anonymous usage data and plan on integr
25
25
26
26
Build time analytics is not active by default. If you have opted in and would like to disable build time analytics or would like to later enable collection, you can do so in two ways:
27
27
28
-
### Set Globally
28
+
### Set globally
29
29
30
-
You can configure the global settings by editing the `io.quarkus.analytics.localconfig` file in the `.redhat` folder of your user’s home directory.
30
+
You can manually configure the global settings by editing the `io.quarkus.analytics.localconfig` file in the `.redhat` folder of your user’s home directory.
31
31
32
-
#### To active collection:
32
+
#### To enable analytics collection
33
33
34
34
```
35
35
{"disabled":false}
36
36
```
37
-
#### To de-active collection:
37
+
38
+
#### To disable analytics collection
38
39
39
40
```
40
41
{"disabled":true}
41
42
```
42
43
43
-
### Set Per Project
44
+
### Set per build
45
+
46
+
You can configure it for a given build by using the `quarkus.analytics.disabled` system property:
44
47
45
-
You can set this by project using the system property `quarkus.analytics.disabled=true`
48
+
- To disable analytics collection, set `quarkus.analytics.disabled` to `true`.
49
+
- To enable analytics collection, set `quarkus.analytics.disabled` to `false`.
46
50
47
-
Example using maven:
51
+
For instance, when using Maven, you can disable analytics collection for a single run with:
0 commit comments