Description

After the Soak Tests completed, a performance degradation was revealed for commit 01c4956 of the refs/heads/main branch for the (flask, auto) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

The threshold violation should also be noticeable on our graph of Soak Test average results per commit.

Description

After the Soak Tests completed, a performance degradation was revealed for commit 01c4956 of the refs/heads/main branch for the (flask, none) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

The threshold violation should also be noticeable on our graph of Soak Test average results per commit.

Description

During Soak Tests execution, a performance degradation was revealed for commit 8a92ecf of the refs/heads/main branch for the (flask, auto) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

Description

The AWS X-Ray developer guide talks about Trace ID Injection. Trace ID Injection allows services like CloudWatch Service to link X-Ray segments to X-Ray segment Service Graphs. This is accomplished by injecting the current AWS X-Ray segment Trace ID into the log that is sent to CloudWatch under the AWS-XRAY-TRACE-ID key (the key is not important since the query is done on the Trace ID, but this is just an example). For example, as seen in the docs:

2019-09-10 18:58:30.844 [nio-5000-exec-4]  AWS-XRAY-TRACE-ID: 1-5d77f256-19f12e4eaa02e3f76c78f46a@1ce7df03252d99e1 WARN 1 - Your logging message here

The problem is, that we do not currently have a package that does this. This is unlike ADOT Java, which publishes a package for log4j and other logging libraries as well.

We should distribute a package like this which gives an OpenTelemetry Instrumentor that injects X-Ray formatted Trace IDs from the current OpenTelemetry Python span. Since we want to do X-Ray specific Trace IDs, the package should be hosted in this repo and not OTel Python Contrib.

NOTE: We need to set up publishing to PIP before we can work on this issue.

Description

After the Soak Tests completed, a performance degradation was revealed for commit 8680fa3 of the refs/heads/main branch for the (flask, none) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

The threshold violation should also be noticeable on our graph of Soak Test average results per commit.

Description

During Soak Tests execution, a performance degradation was revealed for commit e8388c3 of the refs/heads/main branch for the (flask, none) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

Description

During Soak Tests execution, a performance degradation was revealed for commit b219983 of the refs/heads/main branch for the (flask, none) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

Update the Python sample app to have feature parity with the Java sample app. This is part of #63

Description
In case of architecture:

• function A (AWS Lambda Python)
• SQS queue
• function B (AWS Lambda Python)

Flow:

1. Function A by boto library sends a message to SQS queue
2. Function B - trigger set as SQS queue and function makes a call to RDS (postgres)

Both functions are auto instrumented by AWS ADOT Instrumentation deployed as Lambda layer

Expected behaviour:
Only 1 trace with:

• client span related to sending message to SQS queue
• consumer span related to lambda hander method (function b)
• client span related to rds call

Current behaviour:
There are two separated traces:

• First from Function A with a CLIENT span (sending message to SQS queue)
• Second from Function B but only with span related to RDS call

Note:
What I found is lack of AWSTraceHeader in SQS attributes for AWS OTEL Python Instrumentation. I believe this attribute is responsible for context propagation.
When AWS X Ray is used as tracing then AWSTraceHeader is set.

Description

During Soak Tests execution, a performance degradation was revealed for commit 653f117 of the refs/heads/main branch for the (flask, auto) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

Currently, the sample app in this repo which tests automatic instrumentation with Flask (i.e. sample-apps/auto-instrumentation/flask) cannot provide Metrics because automatic Metric tracing is not yet supported in OpenTelmetry Python. See the issue here.

This means we have a 2 code changes to do in the app once that issue is resolved:

Hello, I opened an issue regarding this on the opentelemetry-python-contrib repo but thought it would also be relevant here since it would be helpful to add instructions to this documentation.

I am trying to use the new OTEL_EXPERIMENTAL_RESOURCE_DETECTORS environment variable (introduced in open-telemetry/opentelemetry-python#3181) with the AWS resource detectors in opentelemetry-sdk-extension-aws but it is not detecting the resource detectors.

Please see this issue for more information: open-telemetry/opentelemetry-python-contrib#2370

Description

After the Soak Tests completed, a performance degradation was revealed for commit 8a92ecf of the refs/heads/main branch for the (flask, manual) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

The threshold violation should also be noticeable on our graph of Soak Test average results per commit.

Description

During Soak Tests execution, a performance degradation was revealed for commit 404aa6a of the refs/heads/main branch for the (flask, none) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

Description

During Soak Tests execution, a performance degradation was revealed for commit e8388c3 of the refs/heads/main branch for the (flask, manual) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

Problem Description

For OTel Python right now, if someone wants to use OTel SDK to send traces to AWS X-Ray, there are many packages that they have to install & environment variables they have to set. Even with auto instrumentation from OpenTelemetry Python, there are many packages to install to get started tracing with AWS X-Ray:

i.e.

boto3
requests==2.23.0
Flask==1.1.2

opentelemetry-api==0.16b1
opentelemetry-sdk==0.16b1
opentelemetry-instrumentation==0.16b1
opentelemetry-exporter-otlp==0.16b1
opentelemetry-sdk-extension-aws==0.16b1

We should consider writing a wrapper that will install all these packages for the customer and allow them to simply run the wrapper with config parameters to their needed settings. The wrapper will in turn run their application, which will make their application instrumented with OTel for AWS X-Ray.

Follow Up:

Some questions:

• How can the user uninstall the wrapper and all the packages it installed/environment variables it set?

Related:

In other repos:

• JavaScript Issue

When Python SDK goes GA for metrics make sure that:

1. The sample and tests are up to date.
2. The relevant parts of the ADOT docs are updated.

Note: this SDK is a dependency of our ADOT Lambda offering.

Description

During Soak Tests execution, a performance degradation was revealed for commit 653f117 of the refs/heads/main branch for the (flask, manual) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

Description

After the Soak Tests completed, a performance degradation was revealed for commit 01c4956 of the refs/heads/main branch for the (flask, manual) Sample App. Check out the Action Logs from the Soak Testing workflow run on GitHub to view the threshold violation.

Useful Links

Snapshots of the Soak Test run are available on the gh-pages branch. These are the snapshots for the violating commit:

The threshold violation should also be noticeable on our graph of Soak Test average results per commit.