🐛 [RUM-3598] Ignore collecting requests to logs PCI intake as RUM resources

[N-Boutaib]

Motivation

Requests to PCI compliant endpoint are captured by RUM as resources, while they shouldn't be.

Changes

RUM initialisation doesn't have access to Logs config. Thus, PCI endpoint requests are not skipped and are captured as RUM resources.

When the provided site is datadoghq.com, push PCI intake url to the intake prefixes used to ignore resources

Testing

• Local
• Staging
• Unit
• End to end

---

I have gone over the contributing documentation.

[cit-pr-commenter]

Bundles Sizes Evolution

📦 Bundle Name	Base Size	Local Size	𝚫%
Rum	155.94 kB	156.03 kB	+0.06%
Logs	55.15 kB	55.24 kB	+0.16%
Rum Slim	101.53 kB	101.61 kB	+0.08%
Worker	25.21 kB	25.21 kB	0.00%

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.92%. Comparing base (cdcd13d) to head (07da283).
Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2655   +/-   ##
=======================================
  Coverage   92.91%   92.92%           
=======================================
  Files         239      239           
  Lines        6931     6937    +6     
  Branches     1517     1518    +1     
=======================================
+ Hits         6440     6446    +6     
  Misses        491      491           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[N-Boutaib]

/merge

[dd-devflow]

🚂 MergeQueue

Pull request added to the queue.

This build is going to start soon! (estimated merge in less than 34m)

Use /merge -c to cancel this operation!

[dd-devflow]

❌ MergeQueue

Build pipeline has failing jobs for f02eb2b

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected before the end of the pipeline.

You should have a look at the pipeline, wait for the build to finish and investigate the failures.
When you are ready, re-add your pull request to the queue!

⚠️ Do NOT retry failed jobs directly.

They were executed on a temporary branch created by the merge queue. If you retry them, they are going to fail because the branch no longer exists.

Details

List of failed jobs:

• build-and-lint

Go to failed Gitlab pipeline.

If you need support, contact us on Slack #ci-interfaces with those details!

[N-Boutaib]

/merge

[dd-devflow]

🚂 MergeQueue

Pull request added to the queue.

This build is going to start soon! (estimated merge in less than 34m)

Use /merge -c to cancel this operation!

[dd-devflow]

❌ MergeQueue

Build pipeline has failing jobs for 1653547

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected before the end of the pipeline.

You should have a look at the pipeline, wait for the build to finish and investigate the failures.
When you are ready, re-add your pull request to the queue!

⚠️ Do NOT retry failed jobs directly.

They were executed on a temporary branch created by the merge queue. If you retry them, they are going to fail because the branch no longer exists.

Details

List of failed jobs:

• check-staging-merge
• e2e
• compatibility
• build-bundle
• build-and-lint
• woke
• format

Go to failed Gitlab pipeline.

If you need support, contact us on Slack #ci-interfaces with those details!