Comments (6)
Hi @imanol-uribe - the issue may be that you need to remove the batch
processor - we currently need additional support from the Lambda runtime to enable asynchronous flushing of data, so in the meantime all data needs to be flushed for each lambda request. This means the batch processor can't be used, which implies an asynchronous flush outside the scope of a lambda request, which generally wouldn't happen while the lambda runtime is frozen between requests.
Also to confirm, are you seeing the traces in the Lambda logs (via the logging
exporter you have configured)? That will confirm your file is getting picked up.
from aws-otel-lambda.
Hi @anuraaga. I removed the batch
processor and tried the memory-limiter
processor also without success. Do you recommend any processors?
I see the X-Ray traces in the Lambda UI (when I select my Lambda in the Lambda dashboard and then click monitor).
When I trigger the lambda I can see using debug print statements, in the cloudwatch logs, that the file is in the path that I specified for the environment variables. Where else could the logging
exporter show up?
Thanks for your help, I really appreciate it.
from aws-otel-lambda.
@imanol-uribe With the logging
exporter, we would expect to see the actual payloads for the spans printed to the Cloudwatch logs. We'd expect this to work independent of the setup of the data prepper. Did you also try without any processors at all? The memory limiter also introduces a queue so may cause the flushing to not work correctly - it's not really needed in our current setup because we flush on every request.
Just to confirm, you've added debug logging to verify the path /var/task/collector.yaml/collector.template.yaml
exists? I tried a custom configuration yesterday with the documented environment variable and it worked OK, and also if setting the environment variable to a non-existent path it fails properly. I can't see anything wrong with your config except the possibility of the memory-limiter.
from aws-otel-lambda.
By the way I sent open-telemetry/opentelemetry-lambda#128 so hopefully this will be a bit more transparent in the next release of the layer.
from aws-otel-lambda.
@anuraaga I have tried without the processor as well, and nothing related to open telemetry traces or spans appears in the Cloudwatch Logs.
Yes I add debug logging to verify the path /var/task/collector.yaml/collector.template.yaml
exists.
That's interesting that it works on your end with the custom config file. Just to make sure, you are using this layer: arn:aws:lambda:us-west-2:901920570463:layer:aws-otel-java-wrapper-ver-1-2-0:2
.
Thank you for the continued support.
from aws-otel-lambda.
We debugged offline and found this to be caused by open-telemetry/opentelemetry-lambda#88 - changing the runtime fixed it.
from aws-otel-lambda.
Related Issues (20)
- Documentation for included Processors is incorrect HOT 1
- Error exporting traces from Python lambda HOT 2
- Logging exporter does not log metrics or traces HOT 4
- node.js lambda -> aws-otel-lambda -> ADOT collector doesn't work HOT 10
- First set of counter value ignored after lambda cold boot
- Auto-instrumentation Agent only in Lambda HOT 5
- nodejs spans not exported when upgrading aws otel lambda layer to 1.15.0 HOT 7
- How to configure NodeJs auto-instrumentation to use tracecontext instead of xray? HOT 4
- Error invoking Lambda function after adding latest layer (1-28-1) for java HOT 5
- Steps to build and download a private Python lambda layer as a local .zip or .tar file? HOT 1
- Trace is broken in Lambda Java17 Runtime HOT 2
- Traces are not flushed to the server before the lambda terminates HOT 6
- Unable to access Lambda layer for Python with x86_64 architecture HOT 5
- docs: document of supported python version is old HOT 1
- 53612: bind: address already in use HOT 3
- [nodejs lambda layer] no metrics is exported to cloudwatch logs HOT 2
- Decouple processor needs to be added HOT 9
- Does not work with custom metrics HOT 2
- Request to include the awskinesisexporter HOT 2
- awsemf exporter won't create any log group, nor generating any metrics HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aws-otel-lambda.