opentelemetry-specification
Express
Our great sponsors
opentelemetry-specification | Express | |
---|---|---|
99 | 674 | |
3,602 | 63,771 | |
1.2% | 0.7% | |
9.2 | 8.3 | |
1 day ago | 1 day ago | |
Makefile | JavaScript | |
Apache License 2.0 | MIT License |
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.
Express
-
Building a GitHub activity feed with Node.js and Socket.io
First, we import express. The Express framework allows us to create routes that will respond to webhook POST requests and serve an HTML file when a GET request is made to the root of the site.
-
How to Build an AI FAQ System with Strapi, LangChain & OpenAI
Basic Knowledge of Express
-
Building a RESTful API with Node.js and Express
Express.js Documentation
-
7 Frameworks, One SAML Jackson - Your Open Source Single Sign-On Solution
In the JavaScript ecosystem, there are guides for enabling SAML-based enterprise single sign-on in AdonisJS, Express.js, Next.js, Remix, and React with an Express.js backend.
-
8 NPM Packages for JavaScript Beginners [2024][+tutorials]
Starting off strong with Express.js, the cool kid on the block for building web apps. It's lightweight, flexible, and doesn't throw a tantrum when you ask it to scale. With Express, you can handle HTTP requests like a pro, play around with middleware, set up routes without breaking a sweat, and render views that make your app look stunning. Big names like Netflix and Uber are already on board, and if it's good enough for them, it's definitely worth a peek.
-
Full Stack Web Development Concept map
express - one of the most popular middleware tools, lightweight and easy to learn. docs
-
Screen Sharing with WebRTC: Harnessing JavaScript for Seamless Streaming
Now we can install both Express and Socket.io libraries:
-
Express.js: Introduction and Basic Routing
app.listen(3000); ``` Now you can run your server by executing `node index.js`. Your web application will be accessible at http://localhost:3000/, where you'll see "Hello, world!" displayed in your browser. Congratulations! 🎉 You've successfully set up basic routing with Express.js! This guide covered only the tip of the iceberg when it comes to utilizing Express.js features. Explore its extensive documentation (https://expressjs.com/) to discover more possibilities. Remember, with Express.js, you have the power to build efficient and scalable web applications. Happy coding!
-
How to convert exist nodejs/expressjs app from javascript to typescript, the painless way
Converting a large Express.js application from JavaScript to TypeScript can be a challenging task. For many applications, this represents a significant portion of their technical debt, as the process may span many days, if not months, and new changes are typically not allowed during the conversion.
-
Why I keep an eye on the Vue ecosystem and you should too
Nitro is a nice https webserver that you can deploy everywhere. Comparing it to express, it doesn't need weird middlewares for json, it has a simple way to support caching, a file system router, tasks and scheduled tasks that avoid quite a few shell scripts, db:migrations etc, plugins, KV storages, SQL connectors, websockets...
What are some alternatives?
Sentry - Developer-first error tracking and performance monitoring
Next.js - The React Framework
Serilog - Simple .NET logging with fully-structured events
SvelteKit - web development, streamlined
zipkin - Zipkin is a distributed tracing system
Nuxt.js - Nuxt is an intuitive and extendable way to create type-safe, performant and production-grade full-stack web apps and websites with Vue 3. [Moved to: https://github.com/nuxt/nuxt]
pino - 🌲 super fast, all natural json logger
AdonisJs Application
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
Restify - The future of Node.js REST development
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.
fastify - Fast and low overhead web framework, for Node.js