feat : Metrics - Remove all data collection from Stride.Engine

[Jklawreszuk]

PR Details

reopen of #2261

Description

Goodbye telemetry! 👋

Motivation and Context

Metrics feature in Stride.Engine can be considered as leftover from the time Xenko (now Stride Engine) was closed-source. While telemetry may be useful in commercial products, Stride Engine is being developed as free and open source software by independent volunteers.

Thus, information about current needs, bugs and errors is being frequently gathered by making requests on Github or directly through discussions with others on our Discord channel and there is no need to do any much more.

PR updates also Stride.Editor.CrashReporter. Previously, user could send anonymized report to support.stride3d.net, but this service has been forgotten and is useless since we are commonly use Github. Now it is possible to view and save the created report containing metrics that can be analyzed and - if the submitter wants it - attached to a new Github issue.

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My change requires a change to the documentation.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have built and run the editor to try this change out.

[xen2]

So, overall I agree with removing metrics client and EULA from startup (I think it was the consensus from discussions as well)
But I wanted to quickly rediscuss it again to make sure since it was a while ago.

About metrics

Overall I like that if we get rid of it, that's one less thing to maintain, remove privacy/hack/leak risks, etc.
We can always see trends with nuget downloads, website traffic, etc.
OTOH, detailed stats could have been useful.
Important ones could be:

• which platforms people develop for (to know which one to prioritize)
• versions they use (to know how long to support/migrate)
• how often they use (people trying once vs long-term user)
• etc.
  Are we sure beyond doubt we can be OK without that data? If we remove metrics, there's likely no return.

Note: if we were to keep it, we could look into how to anonymize it as much as possible (while still making sure it's not being faked).
And at least a way to opt-out.
Also, is there an existing system we could reuse nowadays?

Crash report

I still think that longer-term, we might want proper & easy crash report without user needing a github account.
It's much more targeted than Metrics and could have its own mini privacy check when reporting.

We could look into using Sentry or GlitchTip (either using their server or self-hosted; I would favor their server using OSS account to simplify our maintenance/IT).
One important feature is to be able to aggregate many similar looking crash/callstack.
A specific EULA could be part of the crash report dialog (and it can be much smaller than current one, and flowing well with user report).
Of course, adding this feature could be a fair amount of work so it could come later (that's where your github report comes in handy to fill the gap). Also it is just a proposal and will likely need further discussion/decision.

[Kryptos-FR]

Note: this PR will conflict with #3276 where the metrics have also been removed (from the launcher) and the crash report rewritten.