The OpenTelemetry .NET Client (by open-telemetry)

Opentelemetry-dotnet Alternatives

Similar projects and alternatives to opentelemetry-dotnet

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better opentelemetry-dotnet alternative or higher similarity.

opentelemetry-dotnet reviews and mentions

Posts with mentions or reviews of opentelemetry-dotnet. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-04.
  • ASP.NET Core: Monitoreo con OpenTelemetry y Grafana
    7 projects | | 4 Jun 2023
    open-telemetry/opentelemetry-dotnet: The OpenTelemetry .NET Client (
  • Guide to Distributed Tracing with OpenTelemetry Dotnet
    2 projects | | 25 Jan 2023
    💡Good to know -- If you wish to export traces to Jaeger, you should use the AddJaegerExporter instead of the AddOtlpExporter. Visit the opentelemetry-dotnet repository to see how it's done.
  • Observability with Grafana Cloud and OpenTelemetry in .net microservices
    9 projects | | 6 Oct 2022
    We're going to use OpenTelemetry .NET SDK. Add following nuget dependencies to the project:
  • OpenTelemetry in Action: Identifying Database Dependencies
    3 projects | | 8 May 2022
    We instrument the application with the OpenTelemetry SDK and SqlClient instrumentation library for .NET. First, we add the following NuGet package references to the API’s project file:
  • [c#] Using W3C Trace Context standard in distributed tracing
    9 projects | | 13 Jun 2021
    Besides that, the propagation fields (traceparent and tracestate) were added in the message header. In the last article, I said that the standard (in the Working Draft (WD) step of the w3c process) recommends to add the propagation fields in the application-properties section by the message publisher. For the current example, I chose to propagate that context in the message header even for AMQP calls as was done in the dotnet OpenTelemetry example. It's important to reinforce that Trace Context: AMQP protocol is not a W3C Recommendation yet. Take a look at the place where the propagation fields were added:
  • Tracing End-to-End Data from Power Apps to Azure Cosmos DB
    4 projects | | 24 May 2021
    As long as the Azure Functions app knows the instrumentation key from an Application Insights instance, it traces almost everything. OpenTelemetry.NET is one of the Open Telemetry implementations, has recently released v1.0 for tracing. Both metrics and logging are close to GA. However, it doesn't work well with Azure Functions. Therefore, in this post, let's manually implement the tracing at the log level, which is sent to Application Insights.
  • A note from our sponsor - InfluxDB | 24 Sep 2023
    Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge. Learn more →


Basic opentelemetry-dotnet repo stats
6 days ago
Updating dependencies is time-consuming.
Solutions like Dependabot or Renovate update but don't merge dependencies. You need to do it manually while it could be fully automated! Add a Merge Queue to your workflow and stop caring about PR management & merging. Try Mergify for free.