Releases: logzio/opentelemetry-lambda
combined-layer-ruby/v1.0.0
This is the first official release of the Logz.io One Layer for Ruby!
This layer provides a streamlined, all-in-one solution for sending telemetry from your AWS Lambda functions to Logz.io. It bundles language-specific auto-instrumentation with an embedded OpenTelemetry Collector.
combined-layer-python/v1.0.0
This is the first official release of the Logz.io One Layer for Python!
This layer provides a streamlined, all-in-one solution for sending telemetry from your AWS Lambda functions to Logz.io. It bundles language-specific auto-instrumentation with an embedded OpenTelemetry Collector.
combined-layer-nodejs/v1.0.0
This is the first official release of the Logz.io One Layer for NodeJS!
This layer provides a streamlined, all-in-one solution for sending telemetry from your AWS Lambda functions to Logz.io. It bundles language-specific auto-instrumentation with an embedded OpenTelemetry Collector.
combined-layer-java/v1.0.0
This is the first official release of the Logz.io One Layer for Java!
This layer provides a streamlined, all-in-one solution for sending telemetry from your AWS Lambda functions to Logz.io. It bundles language-specific auto-instrumentation with an embedded OpenTelemetry Collector.
combined-layer-go/v1.0.0
This is the first official release of the Logz.io One Layer for Go!
This layer provides a streamlined, all-in-one solution for sending telemetry from your AWS Lambda functions to Logz.io. It contains an embedded OpenTelemetry Collector to process and forward your data.
Please note: Go requires manual instrumentation. You must use the OpenTelemetry Go SDK in your function code to generate traces, metrics, and logs.
1.1.0
This release refactors the telemetryapireceiver into a production-ready component.
- Full Metrics Support: Processes
platform.reportevents into OTel Gauge metrics for key performance indicators like duration and memory usage. - Complete Tracing: Generates trace spans for the entire Lambda
init(cold start) andinvokelifecycle. - Buffer Configuration: Allows users to configure Telemetry API buffer settings (
maxItems,maxBytes,timeoutMs).
Lambda Layers for OpenTelemetry Collector (v0.130.1)
The following Lambda layers are available for this release. Use the appropriate ARN for your Lambda architecture:
🖥️ amd64 (x86_64)
arn:aws:lambda:<region>:486140753397:layer:logzio-opentelemetry-collector-amd64-v0_130_1:2
📱 arm64
arn:aws:lambda:<region>:486140753397:layer:logzio-opentelemetry-collector-arm64-v0_130_1:2
1.0.0
- Add
tail_samplingandmetricstransformprocessorprocessors - Add support for connectors
- To allow using the
spanmetricsconnector
- To allow using the
Lambda Layers for OpenTelemetry Collector (v0.113.0)
The following Lambda layers are available for this release. Use the appropriate ARN for your Lambda architecture:
🖥️ amd64 (x86_64)
arn:aws:lambda:<REGION>:486140753397:layer:logzio-opentelemetry-collector-amd64-v0_113_0:1
📱 arm64
arn:aws:lambda:<REGION>:486140753397:layer:logzio-opentelemetry-collector-arm64-v0_113_0:1
0.1.0
First release of our fork includes critical updates and feature enhancements:
- Integrated Logz.io exporter into
lambdacomponents. - Updated AWS credentials, Lambda layer name, and specified runtimes for broader compatibility.
- Enabled publication across all AWS regions and revised layer naming convention for clarity.
This marks a significant step forward in our project's development, aligning with best practices and extending functionality.
Lambda Layers for OpenTelemetry Collector (v0.113.0)
The following Lambda layers are available for this release. Use the appropriate ARN for your Lambda architecture:
🖥️ amd64 (x86_64)
arn:aws:lambda:<REGION>:486140753397:layer:opentelemetry-collector-amd64-v0_113_0:4
📱 arm64
arn:aws:lambda:<REGION>:486140753397:layer:opentelemetry-collector-arm64-v0_113_0:4