trace-context-w3c
proposal-explicit-resource-management
trace-context-w3c | proposal-explicit-resource-management | |
---|---|---|
11 | 22 | |
4 | 703 | |
- | 4.0% | |
0.0 | 6.5 | |
about 1 year ago | 22 days ago | |
C# | JavaScript | |
- | BSD 3-clause "New" or "Revised" 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.
trace-context-w3c
-
Implementing OTel Trace Context Propagation Through Message Brokers with Go
The answer is Context Propagation. The HTTP example is a classic and W3C even covers it. The propagation is adding the important fields from the context into the HTTP headers and having the other application extract those values and inject them into its trace context. This concept applies to any other way of communication. Here, we will focus on message brokers and how you can achieve context propagation for those.
-
OpenTelemetry in 2023
I've been playing with OTEL for a while, with a few backends like Jaeger and Zipkin, and am trying to figure out a way to perform end to end timing measurements across a graph of services triggered by any of several events.
Consider this scenario: There is a collection of services that talk to one another, and not all use HTTP. Say agent A0 makes a connection to agent A1, this is observed by service S0 which triggers service S1 to make calls to S2 and S3, which propagate elsewhere and return answers.
If we limit the scope of this problem to services explicitly making HTTP calls to other services, we can easily use the Propagators API [1] and use X-B3 headers [2] to propagate the trace context (trace ID, span ID, parent span ID) across this graph, from the origin through to the destination and back. This allows me to query the metrics collector (Jaeger or Zipkin) using this trace ID, look at the timestamps originating at the various services and do a T_end - T_start to determine the overall time taken by one call for a round trip across all the related services.
However, this breaks when a subset of these functions cannot propagate the B3 trace IDs for various reasons (e.g., a service is watching a specific state and acts when the state changes). I've been looking into OTEL and other related non-OTEL ways to capture metrics, but it appears there's not much research into this area though it does not seem like a unique or new problem.
Has anyone here looked at this scenario, and have you had any luck with OTEL or other mechanisms to get results?
[1] https://opentelemetry.io/docs/specs/otel/context/api-propaga...
[2] https://github.com/openzipkin/b3-propagation
[3] https://www.w3.org/TR/trace-context/
-
End-to-end tracing with OpenTelemetry
-- https://www.w3.org/TR/trace-context/
-
Event Driven Architecture — 5 Pitfalls to Avoid
For context propagation, why not just reuse the existing trace context that most frameworks and toolkits generate for http requests? I've had to apply some elbow grease to get it play nice but once it does you're able to use tools like Jeager, etc as part of your asynchronous flow as well.
- W3C Recommendation – Trace Context
-
OpenTelemetry and Istio: Everything you need to know
(Note that OpenTelemetry uses, by default, the W3C context propagation specification, while Istio uses the B3 context propagation specification – this can be modified).
-
What is Context Propagation in Distributed Tracing?
World Wide Web Consortium (W3C) has recommendations on the format of trace contexts. The aim is to develop a standardized format of passing trace context over standard protocols like HTTP. It saves a lot of time in distributed tracing implementation and ensures interoperability between various tracing tools.
- My Logging Best Practices
- Validação de entrada de dados e respostas de erro no ASP.NET
-
[c#] Using W3C Trace Context standard in distributed tracing
The main objective is to propagate a message with traceparent id throw two APIs and one worker using W3C trace context standard. The first-api calls the second-api by a http call while the second-api has an asynchronous communication with the worker by a message broker (rabbitmq was chosen for that). Furthermore, zipkin was the trace system chosen (or vendor as the standard call it), being responsible for getting the application traces and building the distributed tracing diagram:
proposal-explicit-resource-management
- Cooperation between Cloudflare Workers has become amazing thanks to RPC support
-
Proposal: Signals as a Built-In Primitive of JavaScript
The standard doesn't have anything to do with TypeScript, not sure where you got that from? https://github.com/tc39/proposal-explicit-resource-managemen...
-
How does TypeScript's explicit resource management work?
The explicit resource management proposal tries to make it a bit easier for us, by allowing the resource to declare how it should be managed, rather than expecting us to clean everything up when we use the resource. We get a new keyword using to define a variable (rather than const or let), which tells the runtime to clean up the resource at the end of the function.
-
Using using in TypeScript for resource management
Enter the explicit resource management proposal, which describes — among many other things — a new using operator that was introduced in TypeScript 5.2 and is making its way into JavaScript. From the top of the README file, here’s what this proposal aims to do:
-
OpenTelemetry in 2023
In addition to this, is the new (stage 3 even!)explicit resource management proposal[0], supported by TypeScript version >= 5.2[1]
Though I agree that async context is better fit for this generally, the RMP should be good for telemetry around objects that have defined lifetime semantics, which is a step in the right direction you can use today
[0]: https://github.com/tc39/proposal-explicit-resource-managemen...
[1]: https://www.totaltypescript.com/typescript-5-2-new-keyword-u...
- ECMAScript Explicit Resource Management Proposal
-
Why is JavaScript so hated?
It's too early for that, https://github.com/tc39/proposal-explicit-resource-management
-
TypeScript 5.2's New Keyword: 'using'
[3]: https://github.com/tc39/proposal-explicit-resource-managemen...
-
Douglas Crockford: “We should stop using JavaScript”
I'm not _entirely_ sure which RAII you mean, but if you mean something like C#'s `using` or Java's `try-with-resources` or Python's `with`, then https://github.com/tc39/proposal-explicit-resource-managemen... and https://github.com/tc39/proposal-async-explicit-resource-man... are in stage 3 (of 4 stages) in ECMAScript's language proposal lifecycle and will be coming to a JS engine near you behind a flag soon-ish.
What are some alternatives?
b3-propagation - Repository that describes and sometimes implements B3 propagation
librope - UTF-8 rope library for C
opentelemetry-dotnet - The OpenTelemetry .NET Client
caniuse - Raw browser/feature support data from caniuse.com
Serilog.Exceptions - Log exception details and custom properties that are not output in Exception.ToString().
pidove
zipkin - Zipkin is a distributed tracing system
proposal-class-method-parameter-decorators - Decorators for ECMAScript class method and constructor parameters
opentelemetry-specification - Specifications for OpenTelemetry
search-benchmark-game - Search engine benchmark (Tantivy, Lucene, PISA, ...)
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
proposal-iterator-helpers - Methods for working with iterators in ECMAScript