zipkin-api-example
proposal-async-context
| zipkin-api-example | proposal-async-context | |
|---|---|---|
| 1 | 3 | |
| 9 | 462 | |
| - | 6.3% | |
| 10.0 | 6.3 | |
| over 6 years ago | 5 days ago | |
| Go | HTML | |
| Apache License 2.0 | Creative Commons Zero v1.0 Universal |
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.
zipkin-api-example
-
OpenTelemetry in 2023
Yes, I really agree, and I've gone through the same pain, but try using the alternatives that claim to be better because they have OpenAPI specifications [1]
The example shows you how to use the swagger tool, parse the OpenAPI spec [2], auto-generate GoLang glue code, call __one__ of those auto-generated functions and log a trace.
However, there is zero documentation, zero other examples, and I'm left scratching my head whether there's even one person in the world using this approach. I eventually ended up just directly using the service APIs [3] via REST calls.
OTEL is painful, but the alternatives are no better :( I really wish there's some interest in this space, since SLO's and SLI measurements are becoming increasingly important.
[1] https://github.com/openzipkin/zipkin-api-example
[2] https://github.com/openzipkin/zipkin-api/blob/master/zipkin2...
[3] https://zipkin.io/zipkin-api/#/
proposal-async-context
-
OpenTelemetry in 2023
You can follow [0] which is currently stage 2 to fix this
[0]: https://github.com/tc39/proposal-async-context
-
React Server Components with Dan Abramov, Joe Savona, and Kent C. Dodds
Yeah in the stream they talk about using AsyncContext to sorta do that.
-
Updates from the 94th TC39 meeting
Async Context: proposal is to provide a mechanism to ergonomically track async contexts in JavaScript.
What are some alternatives?
docs - Prometheus documentation: content and static site generator
terraform-aws-jaeger - Terraform module for Jeager
aws-otel-lambda - AWS Distro for OpenTelemetry - AWS Lambda
proposal-symbols-as-weakmap-keys - Permit Symbols as keys in WeakMaps, entries in WeakSets and WeakRefs, and registered in FinalizationRegistries
odigos - Distributed tracing without code changes. 🚀 Instantly monitor any application using OpenTelemetry and eBPF
proposal-symbol-proto - TC39 proposal for mitigating prototype pollution
opentelemetry-lambda - Create your own Lambda Layer in each OTel language using this starter code. Add the Lambda Layer to your Lamdba Function to get tracing with OpenTelemetry.
proposal-symbol-predicates - A proposal to introduce ways to differentiate symbols
openobserve - 🚀 10x easier, 🚀 140x lower storage cost, 🚀 high performance, 🚀 petabyte scale - Elasticsearch/Splunk/Datadog alternative for 🚀 (logs, metrics, traces, RUM, Error tracking, Session replay).
community - OpenTelemetry community content
opentelemetry-js-contrib - OpenTelemetry instrumentation for JavaScript modules
proposal-import-assertions - Proposal for syntax to import ES modules with assertions [Moved to: https://github.com/tc39/proposal-import-attributes]