aws-otel-lambda VS tempo

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/...

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 😉 .

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!

Shimmer is a monkeypatching library that a telemetry extension for AWS Lambda was using.

Grafana Tempo also switched from Protobuf storage format to Apache Parquet last year. It's fully open source, and the proposal is here: https://github.com/grafana/tempo/blob/main/docs/design-propo...

disclosure: I work for Grafana!

By combining Grafana Tempo with Tracetest, you can create a robust solution for monitoring and testing APIs with distributed tracing.

Last point: There's already a major open source project in the backend space called Tempo. You may want to reconsider the name.

I started the day with some Rust and spent the rest of the day in the Monitoring and Observability DevRoom. Most of the talks I attended were about OpenTelemetry and were very Grafana Labs-heavy. I knew Grafana and, to a less extent, Loki, and I had never seen Tempo (distributed tracing) and Phlare (profiling), and Mimir (backend for metrics, more backend-y than Prometheus?).

Grafana Tempo yes. Integrates seamlessly with Grafana (the dashboarding)