opentelemetry-js-contrib VS tempo

[2] https://github.com/open-telemetry/opentelemetry-js-contrib/t...

@opentelemetry/instrumentation-aws-lambda

As suggested in both opentelemetry-js-contrib and aws-otel-lambda issues, the solution is changing ES6 export to CommonJS module.exports.

More information about this can be found here and in the instrumentation docs.

Opentelemetry has recently made support for GraphQL available. You can find it here

Now, the exciting thing is that there is now a reference implementation to the same using GraphQL which you can find here and also an example to help you out with the same here

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)