semantic-conventions
Defines standards for generating consistent, accessible telemetry across a variety of domains (by open-telemetry)
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. (by open-telemetry)
| semantic-conventions | opentelemetry-lambda | |
|---|---|---|
| 1 | 8 | |
| 189 | 245 | |
| 11.1% | 1.6% | |
| 9.6 | 9.3 | |
| 3 days ago | 6 days ago | |
| Roff | Go | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
semantic-conventions
Posts with mentions or reviews of semantic-conventions.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-08-28.
-
OpenTelemetry in 2023
[2] https://github.com/open-telemetry/semantic-conventions/issue...
opentelemetry-lambda
Posts with mentions or reviews of opentelemetry-lambda.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-01-12.
-
Did OpenTelemetry deliver on its promise in 2023?
I mean, sure, you can improve performance a bit by increasing the RAM/compute capacity on the Lambda. But it always adds a pretty steep overhead right now, no matter how much capacity you throw at it.
https://github.com/open-telemetry/opentelemetry-lambda/issue...
https://github.com/aws-observability/aws-otel-lambda/issues/...
-
Instrumenting AWS Lambda functions with OpenTelemetry SDKs
OpenTelemetry AWS Lambda repository
- OpenTelemetry in 2023
-
Serverless Spy Vs. Spy Chapter 3: X-Ray vs Jaeger - Send Lambda traces with open telemetry
With the sample apps from the opentelemetry-lambda repository the Lambda part itself was easy to implement. What took me some time was to provide the jaeger Fargate service with IaC ouside of an k8s environment. But with ECS and ServiceDiscovery that was easy in the end. This should be even more simple in an EKS environment with the jaegertracing helm-charts.
-
AWS Lambda tracing with OpenTelemetry and OpenSearch
OpenTelemetry recently released https://github.com/open-telemetry/opentelemetry-lambda, but they also have this in the official docs https://opentelemetry.io/docs/instrumentation/js/serverless/. What do you consider to be the better option?
-
Serverless Spy Vs. Spy Chapter 2: AWS Distro for OpenTelemetry Lambda vs X-Ray SDK
opentelemetry-lambda
-
How to Instrument AWS Services with OpenTelemetry
You don’t have to create an opentelemetry configuration file such as this for each of your lambdas. In fact, you shouldn’t. In AWS, you can use Lambda Layers. You can define the OpenTelemetry tracing piece of code as a Lambda layer and use it in any Lambda you want. Furthermore, OpenTelemetry went ahead and implemented this opentelemetry-lambda layer for us. All we need to do is use it with our config.
-
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!
What are some alternatives?
When comparing semantic-conventions and opentelemetry-lambda you can also consider the following projects:
opentelemetry-specificatio
terraform-aws-lambda - Terraform module, which takes care of a lot of AWS Lambda/serverless tasks (build dependencies, packages, updates, deployments) in countless combinations 🇺🇦
b3-propagation - Repository that describes and sometimes implements B3 propagation
deploy-aws-lambda-to-vpc-with-terraform - Terraform module with all the cloud resources needed to run Lambda within a VPC
opentelemetry-proto - OpenTelemetry protocol (OTLP) specification and Protobuf definitions
sqs-consumer - Build Amazon Simple Queue Service (SQS) based applications without the boilerplate
proposal-async-context - Async Context for JavaScript
opentelemetry-examples
opentelemetry-js-contrib - OpenTelemetry instrumentation for JavaScript modules
aws-otel-js - AWS Distro for OpenTelemetry JavaScript SDK
proposal-explicit-resource-managemen
helm-charts - Helm Charts for Jaeger backend
semantic-conventions vs opentelemetry-specificatio
opentelemetry-lambda vs terraform-aws-lambda
semantic-conventions vs b3-propagation
opentelemetry-lambda vs deploy-aws-lambda-to-vpc-with-terraform
semantic-conventions vs opentelemetry-proto
opentelemetry-lambda vs sqs-consumer
semantic-conventions vs proposal-async-context
opentelemetry-lambda vs opentelemetry-examples
semantic-conventions vs opentelemetry-js-contrib
opentelemetry-lambda vs aws-otel-js
semantic-conventions vs proposal-explicit-resource-managemen
opentelemetry-lambda vs helm-charts