About Syncfusion .NET Telemetry
14 Aug 20263 minutes to read
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.
NOTE
Telemetry is automatically disabled in production environments. No data is collected from deployed applications or end users.
Why do we collect telemetry?
We collect telemetry data to:
- Understand feature adoption and usage trends
- Identify frequently used components and frameworks
- Prioritize future product planning and investments.
- 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 data is collected only in development mode:
| Field | Description |
|---|---|
| Architecture | System architecture information (e.g., x64, x86) |
| Component Name | Syncfusion component being used |
| Feature Name | Syncfusion feature being used |
| Assembly Name | Syncfusion assembly or package in use |
| SDK Name | Syncfusion SDK being used |
| SDK Version | SDK version shipped with the product |
| Framework | Target development framework (e.g., .NET, .NET Core) |
| Framework Version | Version of the target framework (e.g., .NET 10.0.9) |
| Operating System | Operating system used during development |
| Session ID | Unique session identifier (hashed value) |
| Machine Name | Hashed value of machine name, so it cannot be traced back |
| Event Name | Product events name |
NOTE
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
What information is Not collected?
Syncfusion® does not collect:
- Personal information (name, email address, customer ID, company information)
- Source code
- Documents or files
- Application data
- User-generated content
- Business data
- Prompts or AI conversations
- Authentication credentials
- License keys
- Any information that can directly identify an individual
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:
using Syncfusion.Telemetry;Step 2: Disable telemetry at application startup
Call the Telemetry.Disable() method before initializing or using any Syncfusion® product APIs.
using Syncfusion.Telemetry;
// Disable Syncfusion telemetry data collection.
Telemetry.Disable();
// Your Syncfusion product code follows here after disabling the telemetry.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.
NOTE
The
Telemetry.Disable()API should be called, before creating or using any Syncfusion® components, or document-processing library objects.
FAQs
Why am I getting “System.Net.Http.HttpRequestException - No such host is known” error?
| Exception | Why am I getting "System.Net.Http.HttpRequestException - No such host is known" error? |
|---|---|
| Reason |
This error may occur in the following scenarios:
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. |