Shulou(Shulou.com)06/02 Report--

This article will explain in detail how to use .NET Core SDK telemetry data in Microsoft. The content of the article is of high quality, so the editor shares it for you as a reference. I hope you will have some understanding of the relevant knowledge after reading this article.

Microsoft released the original telemetry data set collected from. NET Core SDK users. The time span of the dataset is from the third quarter of 2016 to the second quarter of 2017, providing a perspective on how developers are using SDK. According to Microsoft's Rich Lander, Microsoft will provide telemetry data sets on a quarterly basis, which will be provided under the Open data sharing signature license (ODC-By,Open Data Commons Attributions License).

The data reflects the use of the .NET Core from the command line, so the Visual Studio users of the .NET Core are not involved. .net Core SDK 1.x collects the following application information:

Commands in use (e.g. build, restore, etc.)

Exit code of the command (ExitCode)

The test runner used on the test project

Timestamp of the call

Whether there is a runtime ID in the runtime node

The version of CLI being used

Operating system version.

Lander pointed out that for the .NET Core SDK 2.x series, telemetry further captures the following application information. It should be noted that each machine that runs the. NET Core SDK from the command line corresponds to an anonymous and unique ID:

The parameters and options of the dotnet command are used to determine more details about using the product. For example, collect the template name of dotnet new and the frame specified by dotnet build-framework netstandard2.0. Telemetry only collects some given parameters and options, not arbitrary strings.

Container, which is used to determine whether SDK is running in the container. This helps Microsoft determine whether further support for container work should be provided.

The duration of a command, which is used to determine how long a command will run. This is useful for identifying performance issues that deserve in-depth investigation.

The target .NET framework, which is used to determine which target framework is used, and whether multiple frameworks are specified. This application information is useful for understanding the most widely used version of the .NET standard and what kind of guidance is needed.

The hash ID address, which is used to determine the encrypted MAC of the machine. The ID is anonymous and unique. This is useful for determining the overall number of machines using the .NET Core. Considering the feedback from users, Lander said the data would not be released to the public.

It must be reiterated that participation in the .NET Core SDK telemetry project is an optional behavior, but in a way that defaults to participation. This means that if the developer does not want to be involved, he will have to set an environment variable (that is, DOTNET_CLI_TELEMETRY_OPTOUT) to enable disable. In addition, Lander reiterated that telemetry is not part of the .NET Core runtime, so application information collection is only for .NET Core SDK users.

Microsoft's .NET Core team has not only expanded the scope of the application information data collected, but is also improving the .NET Core 2 SDK based on the practical experience they have gained from it. First, the team will provide a unified build for different Linux, rather than a separate version for each release it supports (such as Red Hat, Debian, and so on). Second, the good news for macOS users is that OpenSSL is no longer necessary. The team is making some improvements (not previously mentioned) to build. NET Core 2 from source code to make it easier for the .NET Core 2 SDK to be added to the package architecture of the Linux release.

Interestingly, the commands that are used most often vary from operating system to operating system.

OS X (macOS): "restore" is the most used

Linux: "run" is the most used (11 million times, much higher than the 3 million times in second place "restore")

Windows: "build" is used the most.

The .NET Core SDK itself does not record the user's IP address, but Microsoft's server does. The customer's IP is truncated to three octets, which allows Microsoft to track SDK usage worldwide. At the operating system level, .NET Core SDK developers use Windows the most, accounting for 71%, using Linux for 18%, and using macOS for 11%.

If you are interested in these provided datasets, you can get them directly from Microsoft. (it should be noted that these datasets are very large files, ranging in size from 188m to 516m. )

About how to use .NET Core SDK telemetry data in Microsoft to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.