Metrics in fman

To improve your experience, fman collects statistics about the features you use. No personal data is collected. Not even your IP is stored.

Transparency

In the spirit of full transparency, fman lets you see which data is shared. To enable this, edit the file Metrics.json in the Local/ subdirectory of your data directory. Add the setting logging_enabled with a value of true. Your file will then likely look as follows:

{"uuid": "...", "logging_enabled": true}

Start fman and perform some actions. Close fman again. You should now have a file Metrics.log next to Metrics.json with entries similar to the following:

{
	"event": "Started fman",
	"uuid": "4915c932-6ca7-4aef-834b-630d3ebc6929",
	"os": "Mac",
	"app_version": "1.7.3"
}

Note how there is absolutely no personally identifiable information. The above merely says that some person started fman.

Letting you see your data holds us accountable and ensures that we are always acting in your best interest.

Why metrics?

You may wonder why metrics are needed at all. The reason is that they let us answer important questions like "How many first-time users never actually run a command?" (meaning that we need to improve fman's onboarding), or "How long does it take to start fman?" (meaning that we need to improve startup performance). Sharing your metrics with us lets us optimise for your usage.

Disabling metrics

You can disable metrics by setting enabled to false in Metrics.json. The file will then likely look as follows:

{"uuid": "...", "enabled": false}