From 7889fc4d99e582e666e8103704e09d9eb647401e Mon Sep 17 00:00:00 2001 From: venkateshwaransf5013 Date: Mon, 29 Jun 2026 20:18:38 +0530 Subject: [PATCH 1/4] Added the Telemetry.md file in UG --- Document-Processing-toc.html | 3 + Document-Processing/Telemetry.md | 173 +++++++++++++++++++++++++++++++ 2 files changed, 176 insertions(+) create mode 100644 Document-Processing/Telemetry.md diff --git a/Document-Processing-toc.html b/Document-Processing-toc.html index f56b1cd9b9..bf520fe38f 100644 --- a/Document-Processing-toc.html +++ b/Document-Processing-toc.html @@ -186,6 +186,9 @@ +
  • + Telemetry +
  • NuGet Packages
    • diff --git a/Document-Processing/Telemetry.md b/Document-Processing/Telemetry.md new file mode 100644 index 0000000000..9d8aa1a9e7 --- /dev/null +++ b/Document-Processing/Telemetry.md @@ -0,0 +1,173 @@ +--- +title: Telemetry in .NET | Syncfusion +description: Syncfusion® Telemetry collects anonymous usage data in .NET to improve product quality, track feature adoption, and guide product planning. +platform: document-processing +control: general +documentation: UG +--- + +# Syncfusion® Telemetry + +Syncfusion® Telemetry library collects anonymous usage data to improve product quality and user experience. This data helps us better understand product usage, feature adoption, usage trends, and make better product roadmap decisions. + +Telemetry is enabled by default. However, you can disable it at any time if required. + +N> Telemetry is automatically disabled in production environments. No data is collected from deployed applications or end users. + +## Why do we collect anonymous telemetry? + +We collect anonymous telemetry data to: + +* Understand feature adoption and usage trends +* Identify frequently used components and frameworks +* Prioritize future product investments and roadmap decisions +* Detect compatibility trends across: + * .NET versions + * Operating systems + * Development environments + +## What data is collected? + +Syncfusion® collects only a limited set of anonymous usage data during development to understand product usage and improve product planning. The following anonymous data is collected **only in development mode:** + +The following data fields are collected by the Syncfusion® Telemetry Library: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldDescription
    ArchitectureSystem architecture information (e.g., x64, x86)
    ComponentNameName of the component
    Assembly NameAssembly containing the telemetry module
    SdkNameName of the SDK being used
    SdkVersionVersion of the SDK
    FrameworkFramework (e.g., .NET, .NET Core)
    FrameworkVersionVersion of the framework (e.g., .NET 10.0.9)
    OperatingSystemTarget operating system
    SessionIDUnique session identifier (hashed value)
    EventNameAnonymous product events
    + +N> No user-generated content (e.g., code, files, or personal data) is collected. + +## Where Does Telemetry Apply? + +Telemetry applies only to the use of Syncfusion® products during development. + +* It is limited to developer environments +* It focuses on product and feature usage +* It does not apply to production applications +* It does not collect any data from end users + +Telemetry is designed solely to help improve the development experience and product quality, without impacting productions applications or users. + +## Telemetry in Development Mode Only + +Telemetry is designed to run only in development environments. +* Enabled by default during development +* Automatically disabled in production builds +* No data is collected from deployed applications +This ensures that telemetry does not affect your application users or production systems + +## How to Disable Telemetry (Opt-out)? + +You can disable telemetry in Syncfusion® .NET products by calling the Telemetry.Disable() API before using any Syncfusion® product APIs in your application. + +### Step 1: Add the telemetry namespace + +Add the following namespace in the file where your application starts using Syncfusion® components or libraries: + +{% tabs %} + +{% highlight c# tabtitle="C#" %} +using Syncfusion.Telemetry; +{% endhighlight %} + +{% endtabs %} + + +### Step 2: Disable telemetry at application startup + +Call the Telemetry.Disable() method before initializing or using any Syncfusion® product APIs. + +{% tabs %} + +{% highlight c# tabtitle="C#" %} +using Syncfusion.Telemetry; + +// Disable Syncfusion telemetry data collection. +Telemetry.Disable(); +// Your Syncfusion product code follows here after disabling the telemetry. +{% endhighlight %} + +{% endtabs %} + +Now, the telemetry is disabled, you can continue using Syncfusion® .NET products based on your application requirements. The Syncfusion® product will work normally, but telemetry data will not be collected or sent. + +N> The Telemetry.Disable() API should be called, before creating or using any Syncfusion® components, or document-processing library objects. + +## FAQs + + + + + + + + + + + + + + + + + + +
    ExceptionWhy am I getting "System.Net.Http.HttpRequestException - No such host is known" error?
    Reason +

    This error may occur in the following scenarios:

    +
      +
    • 'Your application does not have internet connectivity'
      • +
    • 'Exception settings are enabled in your application'
      • +
    +

    When exception handling is enabled and the application lacks internet access, the telemetry module attempts to send data to Azure Application Insights, which can trigger this exception.

    +
    Solution +

    To resolve this error and prevent the exception from being thrown, you can disable the telemetry in your application. This will turn off telemetry data collection entirely.

    +
    + From 6cb4aa810710246c3d51410eb20614f350845d41 Mon Sep 17 00:00:00 2001 From: venkateshwaransf5013 Date: Mon, 29 Jun 2026 20:40:39 +0530 Subject: [PATCH 2/4] Modified lines --- Document-Processing/Telemetry.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Document-Processing/Telemetry.md b/Document-Processing/Telemetry.md index 9d8aa1a9e7..d9b3ab9d1a 100644 --- a/Document-Processing/Telemetry.md +++ b/Document-Processing/Telemetry.md @@ -8,7 +8,7 @@ documentation: UG # Syncfusion® Telemetry -Syncfusion® Telemetry library collects anonymous usage data to improve product quality and user experience. This data helps us better understand product usage, feature adoption, usage trends, and make better product roadmap decisions. +Syncfusion® Telemetry library collects anonymous usage data to improve product quality and user experience. This data helps us better understand product usage, feature adoption, usage trends, and make informed decisions about future product planning. Telemetry is enabled by default. However, you can disable it at any time if required. @@ -20,7 +20,7 @@ We collect anonymous telemetry data to: * Understand feature adoption and usage trends * Identify frequently used components and frameworks -* Prioritize future product investments and roadmap decisions +* Prioritize future product planning and investments. * Detect compatibility trends across: * .NET versions * Operating systems From 62300742ac84a231777eb8208976247092010d73 Mon Sep 17 00:00:00 2001 From: venkateshwaransf5013 Date: Mon, 29 Jun 2026 21:01:10 +0530 Subject: [PATCH 3/4] Added changes --- Document-Processing/Telemetry.md | 46 ++++++++++++++++---------------- 1 file changed, 23 insertions(+), 23 deletions(-) diff --git a/Document-Processing/Telemetry.md b/Document-Processing/Telemetry.md index d9b3ab9d1a..a0285e209d 100644 --- a/Document-Processing/Telemetry.md +++ b/Document-Processing/Telemetry.md @@ -8,9 +8,9 @@ documentation: UG # Syncfusion® Telemetry -Syncfusion® Telemetry library collects anonymous usage data to improve product quality and user experience. This data helps us better understand product usage, feature adoption, usage trends, and make informed decisions about future product planning. +Syncfusion® Telemetry library collects **anonymous usage data** to improve product quality and user experience. This data helps us better understand product usage, feature adoption, usage trends, and make informed decisions about future product planning. -Telemetry is enabled by default. However, you can disable it at any time if required. +Telemetry is **enabled by default**. However, you can disable it at any time if required. N> Telemetry is automatically disabled in production environments. No data is collected from deployed applications or end users. @@ -20,7 +20,7 @@ We collect anonymous telemetry data to: * Understand feature adoption and usage trends * Identify frequently used components and frameworks -* Prioritize future product planning and investments. +* Prioritize future product planning and investments. * Detect compatibility trends across: * .NET versions * Operating systems @@ -45,39 +45,39 @@ The following data fields are collected by the Syncfusion® Teleme System architecture information (e.g., x64, x86) -ComponentName -Name of the component +Component Name +Syncfusion component being used Assembly Name -Assembly containing the telemetry module +Syncfusion assembly or package in use -SdkName -Name of the SDK being used +SDK Name +Syncfusion SDK being used -SdkVersion -Version of the SDK +SDK Version +SDK version shipped with the product Framework -Framework (e.g., .NET, .NET Core) +Target development framework (e.g., .NET, .NET Core) -FrameworkVersion -Version of the framework (e.g., .NET 10.0.9) +Framework Version +Version of the target framework (e.g., .NET 10.0.9) -OperatingSystem -Target operating system +Operating System +Operating system used during development -SessionID +Session ID Unique session identifier (hashed value) -EventName +Event Name Anonymous product events @@ -89,10 +89,10 @@ N> No user-generated content (e.g., code, files, or personal data) is collected. Telemetry applies only to the use of Syncfusion® products during development. -* It is limited to developer environments -* It focuses on product and feature usage -* It does not apply to production applications -* It does not collect any data from end users +* It is limited to **developer environments** +* It focuses on **product and feature usage** +* It does **not apply to production applications** +* It does **not collect any data from end users** Telemetry is designed solely to help improve the development experience and product quality, without impacting productions applications or users. @@ -123,7 +123,7 @@ using Syncfusion.Telemetry; ### Step 2: Disable telemetry at application startup -Call the Telemetry.Disable() method before initializing or using any Syncfusion® product APIs. +Call the `Telemetry.Disable()` method before initializing or using any Syncfusion® product APIs. {% tabs %} @@ -139,7 +139,7 @@ Telemetry.Disable(); Now, the telemetry is disabled, you can continue using Syncfusion® .NET products based on your application requirements. The Syncfusion® product will work normally, but telemetry data will not be collected or sent. -N> The Telemetry.Disable() API should be called, before creating or using any Syncfusion® components, or document-processing library objects. +N> The `Telemetry.Disable()` API should be called, before creating or using any Syncfusion® components, or document-processing library objects. ## FAQs From 74ec5b3d64cd3c225212f4dc6356b9f79f1657bb Mon Sep 17 00:00:00 2001 From: venkateshwaransf5013 Date: Mon, 29 Jun 2026 21:05:57 +0530 Subject: [PATCH 4/4] Added colon --- Document-Processing/Telemetry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Document-Processing/Telemetry.md b/Document-Processing/Telemetry.md index a0285e209d..7763827d24 100644 --- a/Document-Processing/Telemetry.md +++ b/Document-Processing/Telemetry.md @@ -106,7 +106,7 @@ This ensures that telemetry does not affect your application users or production ## How to Disable Telemetry (Opt-out)? -You can disable telemetry in Syncfusion® .NET products by calling the Telemetry.Disable() API before using any Syncfusion® product APIs in your application. +You can disable telemetry in Syncfusion® .NET products by calling the `Telemetry.Disable()` API before using any Syncfusion® product APIs in your application. ### Step 1: Add the telemetry namespace