Skip to content

Don't send settings with all telemetry events#3045

Merged
rgrunber merged 1 commit intoredhat-developer:masterfrom
fbricon:less-verbose-telemetry
Apr 4, 2023
Merged

Don't send settings with all telemetry events#3045
rgrunber merged 1 commit intoredhat-developer:masterfrom
fbricon:less-verbose-telemetry

Conversation

@fbricon
Copy link
Copy Markdown
Collaborator

@fbricon fbricon commented Apr 4, 2023

Fixes #3044

@fbricon fbricon requested a review from rgrunber April 4, 2023 15:31
Copy link
Copy Markdown
Member

@rgrunber rgrunber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change looks fine to me. Can you just rename getNonDefaultJavaSettings to something like getJavaSettingsForTelemetry ? Initially I may have wanted just the setting if they aren't the default, but it's probably easier to just emit the settings regardless of default or not.

Signed-off-by: Fred Bricon <fbricon@gmail.com>
@fbricon fbricon force-pushed the less-verbose-telemetry branch from 4cfdace to 9527ed1 Compare April 4, 2023 17:29
@fbricon
Copy link
Copy Markdown
Collaborator Author

fbricon commented Apr 4, 2023

Change looks fine to me. Can you just rename getNonDefaultJavaSettings to something like getJavaSettingsForTelemetry ? Initially I may have wanted just the setting if they aren't the default, but it's probably easier to just emit the settings regardless of default or not.

done

@rgrunber rgrunber merged commit d0f4f5b into redhat-developer:master Apr 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Java settings don't need to be sent with all telemetry events

2 participants