Open biswajit-nanda opened 1 year ago
This issue was marked stale. It will be closed in 30 days without additional activity.
Still relevant. Would be nice if issues weren't marked as stale without a comment from a maintainer.
@gshpychka do you have thoughts on how you'd fix this? Open to suggestions.
This particular project doesn't have a lot of backing from big vendors, so the maintainers are mainly here on our free time. As such, we need volunteers to help push things forward.
@gshpychka do you have thoughts on how you'd fix this? Open to suggestions.
This particular project doesn't have a lot of backing from big vendors, so the maintainers are mainly here on our free time. As such, we need volunteers to help push things forward.
Oh, please don't take my comment the wrong way - I understand what you wrote, it's just a bit discouraging for issues to be closed without any response. So maybe the stale bot could be tweaked somewhat.
I tried to be very generous on the configuration for the bot. It only marks things as stale when there's been no interaction for a year, and it waits a month before closing something marked as stale. Do you have other suggestions?
I tried to be very generous on the configuration for the bot. It only marks things as stale when there's been no interaction for a year, and it waits a month before closing something marked as stale. Do you have other suggestions?
Yes, is it possible to configure it so that it doesn't mark issues as stale unless there's been a comment from a maintainer (or, if that's complicated to define, form any user)?
I have three lambda functions exactly with the same business logic written in java, node.js and python instrumented with the latest version of OpenTelemetry lambda auto-instrumentation packages. Each of these lambda functions make two outbound HTTP calls after invocation.
All the three lambda functions are being invoked exactly same way via API Gateway triggers. While they are being instrumented successfully, the spans generated from them are in completely different ways triggering inconsistencies.
Steps to reproduce a. All the three Lambda functions are attached. b. Just auto-instrument them with latest version of opentelemetry auto instrumentation libraries for lambda and configure them to send the traces to an Otel Collector. c. Configure logging exporter in the Otel Collector for trace. e. Configure API Gateway trigger for each of the lambda functions. f. Make a single invocation to each lambda function via the API gateway trigger. g. Check the OpenTelemetry collector logs.
What I expect to See: a. All three lambdas are expected to generate one SERVER type span for the handler triggered by the HTTP gateway and then generate at least two CLIENT type spans for each of the two HTTP outbound calls made. b. All the spans generated should be part of the same TraceID.
What I really see: A. Java Lambda: a. Three SERVER spans are generated from the API gateway trigger, each showing a completely different TraceID. One from instrumentation scope io.opentelemetry.aws-lambda-events-2.2 1.26.0-alpha and two from instrumentation scope io.opentelemetry.aws-lambda-core-1.0 1.26.0-alpha. b. Two CLIENT spans for two outbound HTTP calls generated from io.opentelemetry.apache-httpclient-4.0 1.26.0-alpha with the same TraceID as the SERVER Span generated from io.opentelemetry.aws-lambda-events-2.2 1.26.0-alpha.
Below is the Otel Collector log snippet for a single invocation:
B. Node.js Lambda: a. No SERVER type spans are being generated at all. b. Two INTERNAL spans from instrumentation scope @opentelemetry/instrumentation-net 0.32.0 and two CLIENT spans from instrumentation scope @opentelemetry/instrumentation-http 0.41.1 are being generated. The TraceId of one INTERNAL span matches with one of the CLIENT spans and the TraceId of another INTERNAL span matches with the TraceID of the other CLIENT span.
Below is the Otel Collector log snippet for a single invocation:
B. Python Lambda: a. One SERVER type span is generated corresponding to the API Gateway trigger from instrumentation scope opentelemetry.instrumentation.aws_lambda 0.40b0. b. No CLIENT type spans are generated at all. So the two outbound HTTP calls are not being tracked.
Below is the Otel Collector log snippet for a single invocation:
What version of collector/language SDK version did you use? Collector: Latest Version Auto instrumentation library: Latest version Runtime: Java 11, Node.js 18.x, Python 3.11
sourcecode.zip otelcol_log_snippet.zip