Pedro Ramos

@francocm @mfroberg After the `@asyncapi/bundler` dependency upgrade, the file we are getting when running `asyncapi bundle main.yaml` looks like: ```` asyncapi: 3.0.0 info: title: Account Service version: 1.0.0 description: This...

> Should there be a separate mode in `Bundler` that will dereference only external `$ref`s, leaving internal `$ref`s intact (previous behavior?) IMO, that should be the default behaviour. In case...

Still relevant. Waiting for https://github.com/asyncapi/cli/pull/1389 to be solved.

> I don't care if it failed or succeeded. Just want to know it was called. So yeah, we can send the metric as soon as the command is invoked....

/progress 65 Working now on the implementation of a new metric in order to collect the "most popular commands", as mentioned above, regardless the command failed or succeeded.

/progress 80 New metric `action.invoked` already implemented. Now working on unifying the logic so that the metrics are collected in every CLI command when invoked.

/progress 90 Message to warn users about metrics collection already implemented. Now working on unifying the logic so that the metric `action.executed` is collected for every CLI command after being...

Metrics `action.invoked` and `action.executed` already collected in code. PR #859 ready for review. cc @smoya Next actions to be completed: - [x] Test all commands on local env. - [x]...

/progress 95 Metrics already working correctly at both local and production (New Relic) environments, and markdown document about metrics collection created. Now working on a DX-friendly solution like `asyncapi config...

/progress 99 New command `asyncapi config analytics` already implemented. Also metadata related to user ID and AsyncAPI files identification (SHA-256) have been included. Just missing the final review for #859