Am 08.06.2018 um 11:07 schrieb Jeff King: > On Thu, Jun 07, 2018 at 11:10:52PM +0200, Johannes Sixt wrote: > >> Am 07.06.2018 um 16:53 schrieb g...@jeffhostetler.com: >>> From: Jeff Hostetler <jeffh...@microsoft.com> >>> >>> I've been working to add code to Git to optionally collect telemetry data. >>> The goal is to be able to collect performance data from Git commands and >>> allow it to be aggregated over a user community to find "slow commands". >> >> Seriously? "add code to collect telemetry data" said by somebody whose email >> address ends with @microsoft.com is very irritating. I really don't want to >> have yet another switch that I must check after every update that it is >> still off. > > If you look at the design document, it's off by default and would write > to a file on the filesystem. That doesn't seem all that different from > GIT_TRACE.
The patch also includes the following part +telemetry.plugin +---------------- + +If the config setting "telemetry.plugin" contains the pathname to a shared +library, the library will be dynamically loaded during start up and events +will be sent to it using the plugin API. + +This plugin model allows an organization to define a custom or private +telemetry solution while using a stock version of Git. + +For example, on Windows, it allows telemetry events to go directly to the +kernel via the plugin using the high performance Event Tracing for Windows +(ETW) facility. + +The contrib/telemetry-plugin-examples directory contains two example +plugins: + * A trivial log to stderr + * A trivial ETW writer which is not a file but, if enabled, some windows internal thingie where the data is gone/duplicated/sent out/whatever. I for my part would much rather prefer that to be a compile time option so that I don't need to check on every git update on windows if this is now enabled or not.
