Mateusz "mat" Rumian
Mateusz "mat" Rumian
I would like to suggest adding a builder for opentelemetry-collector configuration file for testing purposes. In current implementation https://github.com/open-telemetry/opentelemetry-collector/blob/master/testbed/tests/scenarios.go#L34 config file is generated based on the provided string. This can...
PR can be merged only after https://github.com/open-telemetry/opentelemetry-operator/pull/961 PR update Python auto-instrumentation injection because of changes in `opentelemetry-distro` package which sets `OTEL_METRICS_EXPORTER` to `otlp_proto_grpc`. Accordingly to the [comment](https://github.com/open-telemetry/opentelemetry-operator/blob/main/autoinstrumentation/python/requirements.txt#L2) we have to...
Currently [documentation](https://github.com/open-telemetry/opentelemetry-operator#opentelemetry-auto-instrumentation-injection) is not mentioning default exporters. This could be the reason for many issues that users have with spans exporting.
Currently Instrumentation e2e tests configuration content is random e.g. OTEL_EXPORTER_OTLP_ENDPOINT should always point to the default exporter port used in the supported instrumentation. e.g. [instrumentatio-python](https://github.com/open-telemetry/opentelemetry-operator/blob/main/tests/e2e/instrumentation-python/00-install-instrumentation.yaml#L30) points to `OTLP gRPC` port...
In case of lambda function invoking other function there is a problem with instrumentation of the `invoke` method. **Example lambda code:** ```python import json import os import boto3 FUNCTION_NAME =...
I've observed many differences in case of context propagation between instrumentations and type of invoke. *Reqs:* * AWS XRAY Disabled on lambdas * OTEL_TRACES_SAMPLER = always_on | Instrumentation | INSTRUMENTED...
As it is OpenTelemetry Lambda instrumentation project which is using OpenTelemetry SDKs it would be nice to have an OT context propagation enabled by default in the AWS Lambda instrumentation....
In every AWS Lambda instrumentation `cloud.account.id` tag is present only in the "handler span". It would be very useful to have this tag in every span coming from the AWS...