Currently, "usage" reports are sent, which are aggregated.
This adds an "event" variant, which won't be aggregated.
For compatibility, the "usage" events remain and nothing has
changed in terms of how they parse the command args, for example.
This will ensure continued functioning of anything that relies
on these metrics.
For the "event" variants, the CLI parsing is slightly different
in an attempt to improve data analysis capabilities while still
being respectful of user privacy (i.e. only known values of Docker
CLI commands/flags are ever recorded). Additionally, execution
duration information is now reported with these events.
Currently, "usage" reports are sent, which are aggregated. This adds an "event" variant, which won't be aggregated.
For compatibility, the "usage" events remain and nothing has changed in terms of how they parse the command args, for example. This will ensure continued functioning of anything that relies on these metrics.
For the "event" variants, the CLI parsing is slightly different in an attempt to improve data analysis capabilities while still being respectful of user privacy (i.e. only known values of Docker CLI commands/flags are ever recorded). Additionally, execution duration information is now reported with these events.