Skip to content

Adds E2E tracing test for RDS database interactions for Python #128

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 18 commits into from
Aug 2, 2024

Conversation

georgeboc
Copy link
Contributor

@georgeboc georgeboc commented Jul 23, 2024

Issue description: This commit adds a tracing test for the RDS database interactions for the Python programming language.

Description of changes: We are validating the traces returned against a template to the end-to-end test to ensure we detect any regressions, similarly as we are doing for Java in this other PR. We are particularly interested in the following fields:

  • aws.remote.resource.type
  • aws.remote.resource.identifier
  • aws.remote.service
  • aws.remote.operation

This change was tested in this fork.

Ensure you've run the following tests on your changes and include the link below:
To do so, create a test.yml file with name: Test and workflow description to test your changes, then remove the file for your PR. Link your test run in your PR description. This process is a short term solution while we work on creating a staging environment for testing.

NOTE: TESTS RUNNING ON A SINGLE EKS CLUSTER CANNOT BE RUN IN PARALLEL. See the needs keyword to run tests in succession.

  • Run Java EKS on e2e-playground in us-east-1 and eu-central-2
  • Run Python EKS on e2e-playground in us-east-1 and eu-central-2
  • Run metric limiter on EKS cluster e2e-playground in us-east-1 and eu-central-2
  • Run EC2 tests in all regions
  • Run K8s on a separate K8s cluster (check IAD test account for master node endpoints; these will change as we create and destroy clusters for OS patching)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This commit adds tracing test for rds database interactions for
Python programming language.
Copy link
Contributor

@jerry-shao jerry-shao left a comment

Choose a reason for hiding this comment

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

For the trace template, we probably don't want the E2E test fail if the EKS cluster name changed. Let's use some variables.

@georgeboc georgeboc marked this pull request as draft August 1, 2024 11:20
@georgeboc georgeboc marked this pull request as ready for review August 1, 2024 17:49
@georgeboc georgeboc marked this pull request as draft August 1, 2024 23:05
@georgeboc georgeboc marked this pull request as ready for review August 2, 2024 17:27
@majanjua-amzn majanjua-amzn merged commit 0cd976e into aws-observability:main Aug 2, 2024
1 check passed
georgeboc added a commit to georgeboc/aws-application-signals-test-framework that referenced this pull request Aug 2, 2024
georgeboc added a commit to georgeboc/aws-application-signals-test-framework that referenced this pull request Aug 2, 2024
georgeboc added a commit to georgeboc/aws-application-signals-test-framework that referenced this pull request Aug 2, 2024
georgeboc added a commit to georgeboc/aws-application-signals-test-framework that referenced this pull request Aug 2, 2024
georgeboc added a commit to georgeboc/aws-application-signals-test-framework that referenced this pull request Aug 9, 2024
georgeboc added a commit to georgeboc/aws-application-signals-test-framework that referenced this pull request Aug 12, 2024
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.

3 participants