aws-otel-lambda
zipkin-api
Our great sponsors
aws-otel-lambda | zipkin-api | |
---|---|---|
4 | 1 | |
133 | 59 | |
10.5% | - | |
8.9 | 3.4 | |
9 days ago | about 2 months ago | |
HCL | Thrift | |
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.
aws-otel-lambda
-
OpenTelemetry in 2023
OpenTelemetry is being pushed as a replacement for AWS X-Ray SDKs by AWS, but it's in such a broken state for Lambda right now. A 200-500% performance penalty for using it is insane[1][2].
[1]: https://github.com/aws-observability/aws-otel-lambda/issues/...
-
Serverless Spy Vs. Spy Chapter 2: AWS Distro for OpenTelemetry Lambda vs X-Ray SDK
The documentation for Lambda gives example code for the different languages. To shorten the long way from example code to running code, I will show you ready-to-run CDK code for Python, Node and GO with a serverless architecture. With Lambda, we are using the AWS X-Ray exporter in the collector. If you want to build your own layer, clone the repo AWS-managed OpenTelemetry Lambda Layers. To do that, learn GO here. You might know the creator of the site 😉 .
-
Struggling to connect the dots - ADOT with Lambda using aws-otel-nodejs Lambda layer, not sure how to go from here to using custom instrumentation (e.g. instrumentation-pg, instrumentation-graphql, etc).
Sorry you're having trouble working with the ADOT Lambda Layers :(. Have you had a chance to open an issue on the GitHub repo for OTel Lambda or ADOT Lambda? You should add your expected vs your actual output!
-
How to solve "Cannot redefine property: handler" on AWS Lambda
Shimmer is a monkeypatching library that a telemetry extension for AWS Lambda was using.
zipkin-api
-
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/#/
What are some alternatives?
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
oteps - OpenTelemetry Enhancement Proposals
opentelemetry-js-contrib - OpenTelemetry instrumentation for JavaScript modules
opentelemetry-specificatio
b3-propagation - Repository that describes and sometimes implements B3 propagation
opentelemetry-go - OpenTelemetry Go API and SDK
skywalking - APM, Application Performance Monitoring System
tempo - Grafana Tempo is a high volume, minimal dependency distributed tracing backend.
aws-otel-js - AWS Distro for OpenTelemetry JavaScript SDK
proposal-async-context - Async Context for JavaScript
terraform-aws-jaeger - Terraform module for Jeager
odigos - Distributed tracing without code changes. 🚀 Instantly monitor any application using OpenTelemetry and eBPF