Skip to content

Remove amazon-cloudwatch delete and call APIs before remote sample app #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 29, 2024

Conversation

harrryr
Copy link
Contributor

@harrryr harrryr commented Apr 29, 2024

Issue #, if available:
Metric limiter is having frequent failures due to two issues:

  1. remote-sample-app /healthcheck is called before the sample-app generates two APIs, causing the metric to have the actual value instead of AllOtherRemoteOperation (Sample Link)
  2. during amazon-cloudwatch delete namespace, the amazon-cloudwatch-observability-controller doesn't restart properly and ADOT isn't installed. (Sample Link)

Description of changes:

  1. Call two sample app APIs before pinging the remote sample app
  2. Do not delete amazon-cloudwatch. It is not a necessary operation

Test run: https://github.com/aws-observability/aws-application-signals-test-framework/actions/runs/8886143322

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Copy link
Contributor

@majanjua-amzn majanjua-amzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved, but I find the removal of the delete/wait lines concerning. Why would deleting the pods cause ADOT not to be installed properly?

@harrryr
Copy link
Contributor Author

harrryr commented Apr 29, 2024

I believe amazon-cloudwatch-observability-controller is responsible for installing ADOT onto the sample applications. I'm not sure why it sometimes doesn't restart after deleting though.

@harrryr harrryr merged commit 0e48219 into main Apr 29, 2024
@harrryr harrryr deleted the fix-metric-limiter branch April 29, 2024 23:38
zzhlogin pushed a commit to zzhlogin/aws-application-signals-test-framework that referenced this pull request Jun 6, 2024
…tric-limiter

Remove amazon-cloudwatch delete and call APIs before remote sample app
zzhlogin pushed a commit to zzhlogin/aws-application-signals-test-framework that referenced this pull request Jun 6, 2024
…tric-limiter

Remove amazon-cloudwatch delete and call APIs before remote sample app
zzhlogin pushed a commit to zzhlogin/aws-application-signals-test-framework that referenced this pull request Jun 6, 2024
…tric-limiter

Remove amazon-cloudwatch delete and call APIs before remote sample app
zzhlogin pushed a commit to zzhlogin/aws-application-signals-test-framework that referenced this pull request Jun 6, 2024
…tric-limiter

Remove amazon-cloudwatch delete and call APIs before remote sample app
georgeboc pushed a commit to georgeboc/aws-application-signals-test-framework that referenced this pull request Jul 8, 2024
*Issue #, if available:*

1. change tox.ini `py3{7,8,9,10,11}` to `3.{7,8,9,10,11}` so that the
workflow can run unit test.
2. change project Dokerfile to use python 3.10, because we are using
opentelemetry-exporter-otlp-proto-grpc, it use grpcio as dependencies.
It seems like grpc has a strict dependency on the OS / Python version.
Also mentioned in [Docker build template in
upstream](https://github.com/open-telemetry/opentelemetry-operator/blob/b5bb0ae34720d4be2d229dafecb87b61b37699b0/autoinstrumentation/python/requirements.txt#L2).
When we use python 3.11 to build the docker file, we receive `"Cannot
import name 'cygrpc' from 'grpc._cython'"` in EKS auto-instrumentation
injection. As
[https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/recover-python-functions.md#the-python-interpre[…]tions-python-worker](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/recover-python-functions.md#the-python-interpreter-isnt-supported-by-azure-functions-python-workerr)
suggested, Azure Functions support python 3.6 - 3.9, but while testing,
3.10 also worked. So change to 3.10 here.
3. As we change the python version for Dockerfile we also change
main_build and release_build workflow to align with Dock build.


By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants