Add css obfuscation test [APMSP-2764]

[Eldolfin]

• requires feat!: integrate obfuscation to the stats exporter [APMSP-2764] libdatadog#1819 to me merged, a libdatadog bump and one tracer updating libdd-data-pipeline to test it

btw I don't get the fail in test_the_tests because the new scenario TRACE_STATS_COMPUTATION_OBFUSCATION_DISABLED has agent_env variables that the existing TRACE_STATS_COMPUTATION doesn't so they're not equivalent.

Motivation

• Test that libraries obfuscate spans before sending them to /stats

Changes

• Add one testcase (is this considered a new feature ?)
• Fix 2 small issues I found while looking at the repo

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:

.github/workflows/run-end-to-end.yml                                    @DataDog/system-tests-core
tests/stats/test_stats.py                                               @DataDog/system-tests-core
utils/_context/_scenarios/__init__.py                                   @DataDog/system-tests-core
utils/_context/_scenarios/endtoend.py                                   @DataDog/system-tests-core
utils/_context/containers.py                                            @DataDog/system-tests-core
utils/proxy/mocked_response.py                                          @DataDog/system-tests-core

[VianneyRuhlmann]

I think you should check for >=1 to make sure the test still passes if a tracer updates to a v2 someday

[VianneyRuhlmann]

Out of curiosity, is there something that can cause len(sql_stats) to not be 4 (1,2,admin,test), or is it just to make it easier to add more values to test_user_ids ?

[Eldolfin]

For some reason stats appear to be sent twice by dd-trace-py so len(sql_stats) == 8 but I feel like other tracers might send them only once which would also be correct for this test. I could however assert that each bucket has 4 stats entry if you want

[Eldolfin]

Ok I just tried it again and what I just said was something I misremembered from when I started working on this. it is indeed == 4 so I just change it to that instead

[VianneyRuhlmann]

I don't see anything about disabling the obfuscation in the spec is it done by setting the obfuscation version to 0 (if not maybe we need a scenario for the missing/version 0 case)

[Eldolfin]

It's not a setting from the CSS spec but to avoid breaking changes in the obfuscation behavior when switching from agent obfuscation to client obfuscation I decided that following as much of the config as possible would be preferable.

https://github.com/DataDog/datadog-agent/blob/main/pkg/config/config_template.yaml#L1633