opentelemetry-specification
opentelemetry-ext-js
Our great sponsors
opentelemetry-specification | opentelemetry-ext-js | |
---|---|---|
99 | 13 | |
3,596 | 167 | |
0.9% | 1.8% | |
9.2 | 3.8 | |
about 17 hours ago | 3 days ago | |
Makefile | TypeScript | |
Apache License 2.0 | Apache License 2.0 |
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
-
OpenTelemetry Journey #00 - Introduction to OpenTelemetry
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
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
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
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
OpenTelemetry Specification GitHub
-
OpenTelemetry vs. OpenMetrics: Which semantic convention should you use?
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.
-
OpenTelemetry Logs status?
This is your best bet if you want to track status updates: https://github.com/open-telemetry/opentelemetry-specification/issues/2911
-
Distributed Tracing with OpenTelemetry - Part I
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
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
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.
opentelemetry-ext-js
-
How to Instrument AWS Services with OpenTelemetry
AWS has good tools for tracing, but in this example, I will use another remote and distributed tracing platform – Aspecto.
-
Distributed Tracing for Kafka with OpenTelemetry in Python
For this article, I will be using Aspecto to visualize my traces. You can follow along by quickly creating a free account.
-
How to Get Started with OpenTelemetry Go
If we drill down into one of these traces, we can see in more detail how long each request took and clear visualization of the entire workflow.
-
Distributed Tracing for Kafka with OpenTelemetry in Node
For the purposes of this guide, I chose to use Aspecto as my visualization tool. This is because Aspecto provides built-in support for visualizing messaging systems like Kafka (and, of course, any other part of our microservice architectures).
-
Guide to OpenTelemetry Distributed Tracing in Rust
To follow along, you can open a new free-forever Aspecto account or log in to your existing one.
-
OpenTelemetry Java: Getting Started Guide
That’s about it for this OpenTelemetry Java guide, folks. If you have any questions or issues with any of these steps, feel free to reach out to us via chat or join our OpenTelemetry Slack channel (part of the CNCF Slack).
-
OpenTelemetry Collector: A Friendly Guide for Devs
At Aspecto, you can sign up for free and use our generous free-forever plan (no limited features).
-
Jaeger Tracing: The Ultimate Guide
Aspecto has a free-forever tier and provides everything included in Jaeger and more. Sort of like Jaeger on steroids.
-
Distributed Tracing for RabbitMQ with OpenTelemetry
However, you can take your tracing visualization to the next level with Aspecto. Try it yourself with the free-forever plan that has no limited features.
-
OpenTelemetry kafkajs instrumentation for Node.js
Hi all, we wanted to share some love back to the Kafka community. We hope you'd find this instrumentation helpful, check it out on GitHub 🌟and npm
What are some alternatives?
Sentry - Developer-first error tracking and performance monitoring
nagios-plugins - 450+ AWS, Hadoop, Cloud, Kafka, Docker, Elasticsearch, RabbitMQ, Redis, HBase, Solr, Cassandra, ZooKeeper, HDFS, Yarn, Hive, Presto, Drill, Impala, Consul, Spark, Jenkins, Travis CI, Git, MySQL, Linux, DNS, Whois, SSL Certs, Yum Security Updates, Kubernetes, Cloudera etc...
Serilog - Simple .NET logging with fully-structured events
testcontainers-spring-boot - Container auto-configurations for Spring Boot based integration tests
zipkin - Zipkin is a distributed tracing system
malabi - Tracing Based JavaScript Assertions
pino - 🌲 super fast, all natural json logger
es-clip-image-search - Sample implementation of natural language image search with OpenAI's CLIP and Elasticsearch or Opensearch.
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
stompjs - Javascript and Typescript Stomp client for Web browsers and node.js apps
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.
upstash-kafka - HTTP based Kafka Client for Serverless and Edge Functions