SSI: Java Crash tracking

[robertomonteromiguel]

Motivation

Enable crash tracking tests for DOCKER_SSI_CRASHTRACKING.
Example of crash tracking in AWS for the HOST_AUTO_INJECTION_INSTALL_SCRIPT scenario.

To run the SSI tests locally and reproduce the issue:

AWS SSI

1. Run: utils/scripts/ssi_wizards/aws_onboarding_wizard.sh
2. Select:
   • Language: Java
   • Weblog: test-app-java
   • Scenario: HOST_AUTO_INJECTION_INSTALL_SCRIPT

Docker SSI

1. Run: utils/scripts/ssi_wizards/docker_ssi_wizard.sh
2. Select:
   • Language: Java
   • Weblog: jetty-app
   • Scenario: DOCKER_SSI_CRASHTRACKING

Changes

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• Anything but tests/ or manifests/ is modified ? I have the approval from R&P team
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added, removed or renamed?
  • Get a review from R&P team

[github-actions]

CODEOWNERS have been resolved as:

lib-injection/build/docker/java/jetty-app/CrashServlet.java             @DataDog/system-tests-core
lib-injection/build/docker/java/jetty-app/JettyServletMain.java         @DataDog/system-tests-core
tests/auto_inject/test_auto_inject_install.py                           @DataDog/system-tests-core
tests/docker_ssi/test_docker_ssi_crash.py                               @DataDog/system-tests-core
utils/scripts/ci_orchestrators/docker_ssi.json                          @DataDog/system-tests-core

[datadog-datadog-prod-us1]

⚠️ Tests

✨ Fix all issues with Cursor

⚠️ Warnings

❄️ 2 New flaky tests detected

tests.parametric.test_process_discovery.Test_ProcessDiscovery.test_metadata_content_without_process_tags[library_env0, parametric-python] from system_tests_suite (Datadog) (Fix with Cursor)

AssertionError: assert Version('4.3.0-rc1') == Version('4.3.0+rc1')
  Full diff:
  - Version('4.3.0+rc1')
  ?               ^
  + Version('4.3.0-rc1')
  ?               ^

self = <tests.parametric.test_process_discovery.Test_ProcessDiscovery object at 0x7fa8411660f0>
test_library = <utils.docker_fixtures._test_clients._test_client_parametric.ParametricTestClientApi object at 0x7fa80ee7b6b0>
library_env = {'DD_AGENT_HOST': 'localhost', 'DD_ENV': 'second-test', 'DD_EXPERIMENTAL_PROPAGATE_PROCESS_TAGS_ENABLED': 'false', 'DD_SERVICE': 'b', ...}
...

tests.parametric.test_process_discovery.Test_ProcessDiscovery.test_metadata_content_with_process_tags[library_env0, parametric-python] from system_tests_suite (Datadog) (Fix with Cursor)

AssertionError: assert Version('4.3.0-rc1') == Version('4.3.0+rc1')
  Full diff:
  - Version('4.3.0+rc1')
  ?               ^
  + Version('4.3.0-rc1')
  ?               ^

self = <tests.parametric.test_process_discovery.Test_ProcessDiscovery object at 0x7fa843ae0710>
test_library = <utils.docker_fixtures._test_clients._test_client_parametric.ParametricTestClientApi object at 0x7fa80eb80d70>
library_env = {'DD_AGENT_HOST': 'localhost', 'DD_ENV': 'test', 'DD_EXPERIMENTAL_PROPAGATE_PROCESS_TAGS_ENABLED': 'true', 'DD_SERVICE': 'a', ...}
...

ℹ️ Info

🧪 All tests passed

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: c75db96 | Docs | Datadog PR Page | Was this helpful? Give us feedback!}