The OpenTelemetry (OTel) project for .NET provides regular releases and updates for its APIs, SDKs, language agents, and Collector. The release schedule includes a mix of feature releases, bug fixes, and maintenance updates. Here are some possible options for understanding the release schedule and upcoming features:
- Check the official OpenTelemetry documentation: The OTel documentation for .NET provides information on the latest release, as well as previous releases. The documentation also includes a roadmap that outlines the project’s future plans and priorities. (Source)
- Follow the OpenTelemetry blog: The OTel blog features announcements and updates about new releases, features, and community initiatives. The blog also includes articles about best practices, use cases, and other topics related to distributed tracing and monitoring. (Source)
- Join the OpenTelemetry community: The OTel project has an active community of contributors, users, and vendors who participate in discussions, working groups, and other events. Joining the community is a great way to stay informed about the project’s progress and provide feedback on its direction. (Source)
- Monitor the OpenTelemetry repository: The OTel repository on GitHub includes information about upcoming releases, as well as issues and pull requests related to new features and bug fixes. Monitoring the repository is a good way to stay up-to-date on the project’s development and contribute to its growth. (Source)
For example, the latest release of OpenTelemetry .NET Automatic Instrumentation is version 1.0.0, which includes support for sending traces, metrics, and logs from .NET applications and services to observability backends without modifying their source code. The release also includes installer scripts and a NuGet package that simplify the task of deploying and configuring the collection of telemetry. (Source)
To get started with OpenTelemetry .NET, you can download installation scripts from the opentelemetry-dotnet-instrumentation repository and execute them in your development environment. You can also import the OpenTelemetry module in PowerShell and install the OpenTelemetry core. (Source)
For troubleshooting, you can set environment variables to enable console exporters for logs, metrics, and traces. You can also refer to the OpenTelemetry .NET SDK and specification documentation for supported libraries and frameworks. (Source)
