Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Flatest-updates%2Fdeprecations%2Fdotnet-sdk-deprecation.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Flatest-updates%2Fdeprecations%2Fdotnet-sdk-deprecation.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

# Deprecation of Coralogix .NET SDK

**Published**: January 12, 2026

**Effective**: June 30, 2026

## Deprecation notice[​](#deprecation-notice "Direct link to Deprecation notice")

As part of our continued investment in open standards and long-term observability best practices, Coralogix will deprecate the **Coralogix .NET SDK** on **June 30, 2026**.

The Coralogix .NET SDK is deprecated in favor of the **OpenTelemetry .NET SDK**, which is now the recommended and supported approach for collecting logs, metrics, and traces from .NET applications.

**Action is required** to ensure continued support and compatibility.

## Why this is happening[​](#why-this-is-happening "Direct link to Why this is happening")

The observability ecosystem has converged on **OpenTelemetry** as the industry standard for telemetry collection. Maintaining a proprietary SDK alongside OpenTelemetry creates duplication and limits access to new capabilities.

By standardizing on OpenTelemetry, Coralogix can provide:

* A vendor-neutral, CNCF-backed standard
* Unified collection of logs, metrics, and traces
* Faster access to new ecosystem features and integrations
* Long-term stability and community-driven innovation
* Consistent configuration across languages and platforms

## What’s affected[​](#whats-affected "Direct link to What’s affected")

The following Coralogix-maintained .NET SDKs are deprecated:

* `Coralogix.SDK` (for .NET Framework)
* `CoralogixCoreSDK` (for .NET Core)

These SDKs may currently be used in:

* .NET Framework or .NET Core applications
* Custom logging implementations using `CoralogixLogger`
* Applications configured with `CORALOGIX_LOG_URL`
* CI/CD pipelines or deployment scripts that install Coralogix NuGet packages

After the effective date, these SDKs will no longer be supported or maintained.

## What you need to do[​](#what-you-need-to-do "Direct link to What you need to do")

### Migrate to OpenTelemetry for .NET[​](#migrate-to-opentelemetry-for-net "Direct link to Migrate to OpenTelemetry for .NET")

Replace the Coralogix .NET SDK with **OpenTelemetry .NET instrumentation**.

The OpenTelemetry .NET SDK is **stable** and fully supported by Coralogix for:

* Logs
* Metrics
* Traces

You can choose between:

* **Auto-instrumentation** (zero code changes)
* **Manual instrumentation** (full control and customization)

Follow the official guide here:<br />[.NET OpenTelemetry Instrumentation](https://coralogix.com/docs/docs/opentelemetry/instrumentation-options/dotnet-opentelemetry-instrumentation/.md)

### Update endpoint configuration[​](#update-endpoint-configuration "Direct link to Update endpoint configuration")

OpenTelemetry uses Coralogix regional **[ingress endpoints](https://coralogix.com/docs/docs/integrations/coralogix-endpoints/.md#ingress-endpoints)**:

```
https://ingress.<CORALOGIX_REGION>.coralogix.com:443
```

### Update authentication[​](#update-authentication "Direct link to Update authentication")

Replace legacy SDK authentication with OpenTelemetry headers:

* **New**: `Authorization: Bearer <your-api-key>`

Ensure all environment variables, containers, and scripts are updated accordingly.

## What will happen after June 30, 2026?[​](#what-will-happen-after-june-30-2026 "Direct link to What will happen after June 30, 2026?")

* The Coralogix .NET SDK will no longer be supported
* No bug fixes, updates, or security patches will be provided
* Compatibility with newer .NET versions is not guaranteed
* Support requests related to the deprecated SDK may be declined

Existing applications may continue to function, but migration is strongly recommended.

## Additional resources[​](#additional-resources "Direct link to Additional resources")

* [.NET OpenTelemetry Instrumentation Guide](https://coralogix.com/docs/docs/opentelemetry/instrumentation-options/dotnet-opentelemetry-instrumentation/.md)
* [OpenTelemetry .NET Documentation](https://opentelemetry.io/docs/languages/dotnet/)
* [Coralogix Ingress Endpoints](https://coralogix.com/docs/docs/integrations/coralogix-endpoints/.md#ingress-endpoints)

## Need help?[​](#need-help "Direct link to Need help?")

Our team is here to help you migrate smoothly.

Reach out via our **24/7 in-app support** or contact your **Technical Account Manager**, and we’ll guide you through the transition step by step.