Feat: Enable anonymized analytics for the SQLMesh core

[izeigerman]

We prioritize our development work based on the needs of SQLMesh users. Some users share their needs via our Slack or Github communities, but many do not. We have added some simple anonymized usage information (telemetry) to SQLMesh to ensure the needs of all users are heard.

All information is anonymized with hash functions, so we could not link data to a specific company, user, or project even if we wanted to (which we don't!). No information is related to credentials or authentication.

We collect anonymized information about SQLMesh project complexity and usage - for example, number of models, count of model kinds, project load time, whether an error occurred during a plan/run (no stacktraces or error message), and names (but not values) of the arguments passed to CLI commands.

The collection of anonymized usage information can be disabled with these methods:

• Set the root disable_anonymized_analytics: true key in the SQLMesh project configuration file
• Execute SQLMesh commands with an environment variable SQLMESH__DISABLE_ANONYMIZED_ANALYTICS set to 1, true, t, yes, or y

[tobymao]

why did you choose to do this pattern? should collector instead be a constant like COLLECTOR, which can then be disabled?

[izeigerman]

This allowed me to reuse existing constructs (eg dispatcher) without explicitly adding disable API to the collector. I don't feel strongly about either approach. Do you see any advantages to doing this the way you suggested?

[tobymao]

no