Pedro Ramos

> to have in docs a new markdown document dedicated to this topic Do you mean in a separate markdown document just related to metrics collection? @smoya and I were...

> I think we should be as transparent as possible here. If someone wants to find out what are we measuring and where are we putting this information they should...

@smoya @derberg @fmvilas > to have in docs a new markdown document dedicated to this topic Markdown document dedicated to metrics collection is ready for review [here](https://github.com/smoya/cli/pull/9). > We should...

> @peter-rr I don't think standard is `process.env.NODE_ENV !== 'CI'` > I think it is env called `CI` (`process.env.CI === true`) that once set to `true` - metrics should not...

> * Ask users to `export ASYNCAPI_METRICS="false"` This is the easiest solution I think, and can be done easily by editing the informational message. > * Add a new command...

@Amzani At the moment I've changed the previous warning message to and informational message, and "How to disable tracking" section at markdown document has been updated in https://github.com/smoya/cli/pull/9 Working in...

@Amzani Both `asyncapi config analytics` command and `.asyncapi-analytics` config file are already implemented and ready for review: https://github.com/asyncapi/cli/pull/859/commits/e3fc3c79476703c9f78c52ee1c585510df0bfebd

@Amzani Integration tests already added. Let me know if something else missing :)

@Amzani Should we use safer alternatives, such as `SHA-256`, as recommended [by Sonarcloud](https://github.com/asyncapi/cli/pull/859#issuecomment-1978684899)? Or should we ignore it?

Hey @Souvikns, could you take a look so we can get the final review on this PR? 💪 I'm working now on fixing the current conflict regarding the `package-lock.json`.