opentelemetry-specification VS opentelemetry-dotnet

Compare opentelemetry-specification vs opentelemetry-dotnet and see what are their differences.

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
opentelemetry-specification opentelemetry-dotnet
99 7
3,580 2,932
1.3% 4.0%
9.2 9.7
7 days ago 3 days ago
Makefile C#
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

opentelemetry-specification

Posts with mentions or reviews of opentelemetry-specification. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-25.
  • OpenTelemetry Journey #00 - Introduction to OpenTelemetry
    4 projects | dev.to | 25 Feb 2024
    It means that the OpenTelemetry project provides not only a specification to define the contract between the applications, collectors, and telemetry databases, but also a set of APIs, SDKs, and tools like instrumentation libraries (for different languages), collectors, operators, etc. OpenTelemetry is open-source and vendor-agnostic, so the project is not tied to any specific vendor or cloud provider.
  • Migrating to OpenTelemetry
    8 projects | news.ycombinator.com | 16 Nov 2023
    Sure, happy to provide more specifics!

    Our main issue was the lack of a synchronous gauge. The officially supported asynchronous API of registering a callback function to report a gauge metric is very different from how we were doing things before, and would have required lots of refactoring of our code. Instead, we wrote a wrapper that exposes a synchronous-like API: https://gist.github.com/yolken-airplane/027867b753840f7d15d6....

    It seems like this is a common feature request across many of the SDKs, and it's in the process of being fixed in some of them (https://github.com/open-telemetry/opentelemetry-specificatio...)? I'm not sure what the plans are for the golang SDK specifically.

    Another, more minor issue, is the lack of support for "constant" attributes that are applied to all metrics. We use these to identify the app, among other use cases, so we added wrappers around the various "Add", "Record", "Observe", etc. calls that automatically add these. (It's totally possible that this is supported and I missed it, in which case please let me know!).

    Overall, the SDK was generally well-written and well-documented, we just needed some extra work to make the interfaces more similar to the ones were were using before.

  • OpenTelemetry Exporters - Types and Configuration Steps
    5 projects | dev.to | 30 Oct 2023
    OpenTelemetry is an open-source collection of tools, APIs, and SDKs that aims to standardize the way we generate and collect telemetry data. It follows a specification-driven development. The OpenTelemetry specification  has design and implementation guidelines for how the instrumentation libraries should be implemented. In addition, it provides client libraries in all the major programming languages that follow the specification.
  • OpenTelemetry in 2023
    36 projects | news.ycombinator.com | 28 Aug 2023
    Two problems with OpenTelemetry:

    1. It doesn't know what the hell it is. Is it a semantic standard? Is a protocol? It is a facade? What layer of abstraction does it provide? Answer: All of the above! All the things! All the layers!

    2. No one from OpenTelemetry has actually tried instrumenting a library. And if they have, they haven't the first suggestion on how instrumenters should actually use metrics, traces, and logs. Do you write to all three? To one? I asked this question two years ago, not a single response. [1]

    [1] https://github.com/open-telemetry/opentelemetry-specificatio...

  • Tracetest Analyzer: Identify patterns and issues with code instrumentation
    3 projects | dev.to | 7 Jul 2023
    OpenTelemetry Specification GitHub
  • OpenTelemetry vs. OpenMetrics: Which semantic convention should you use?
    2 projects | /r/PrometheusMonitoring | 2 Jun 2023
    One update to this: we proposed replacing the count suffix in OpenTelemetry with total to match Prometheus/OpenMetrics. That discussion resulted in the count suffix being removed from the OpenTelemetry semantic conventions. We'll soon update our metric from being called function.calls.count to just function.calls and the generated Prometheus queries will refer to function_calls_total. That resolves one of the main conflicts between the two specs.
  • Distributed Tracing with OpenTelemetry - Part I
    2 projects | dev.to | 7 Feb 2023
    OpenTelemetry is a standard for implementing telemetry in your applications. It provides a specification, containing the requirements that all implementations should follow as well as some implementations for major languages, including an API and a SDK to interact with it.
  • Observability - ApostropheCMS, OpenTelemetry, and New Relic
    4 projects | dev.to | 16 Nov 2022
    At this point, we are about to do the real work where we have to configure OpenTelemetry and export telemetry data to New Relic. Exporting this kind of data relies on a specific protocol; the OpenTelemetry Protocol or OTLP.
  • OpenTelemetry Logs - A Complete Introduction & Implementation
    3 projects | dev.to | 20 Oct 2022
    OpenTelemetry provides instrumentation libraries for your application. The development of these libraries is guided by the OpenTelemetry specification. The OpenTelemetry specification describes the cross-language requirements and design expectations for all OpenTelemetry implementations in various programming languages.
  • An Open Source Observability Platform | SigNoz
    3 projects | dev.to | 13 Oct 2022
    It follows a specification-driven development. The OpenTelemetry specification has design and implementation guidelines for how the instrumentation libraries should be implemented. In addition, it provides client libraries in all the major programming languages which follow the specification.

opentelemetry-dotnet

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 | dev.to | 4 Jun 2023
    open-telemetry/opentelemetry-dotnet: The OpenTelemetry .NET Client (github.com)
  • Guide to Distributed Tracing with OpenTelemetry Dotnet
    2 projects | dev.to | 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 | dev.to | 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 | dev.to | 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 | dev.to | 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 | dev.to | 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.

What are some alternatives?

When comparing opentelemetry-specification and opentelemetry-dotnet you can also consider the following projects:

Sentry - Developer-first error tracking and performance monitoring

ApplicationInsights-dotnet - ApplicationInsights-dotnet

Serilog - Simple .NET logging with fully-structured events

zipkin - Zipkin is a distributed tracing system

RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins

pino - 🌲 super fast, all natural json logger

Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required

otel-with-apache-pulsar - Example of application that produces and consumes events to/from Apache Pulsar. Traces from the transactions are captured using OpenTelemetry and sent to Elastic Observability.

C# StatsD Client

ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.

signoz - SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool