🔉 add trace sample rate in events

[BenoitZugmeyer]

Motivation

Be informed, at the session level, of the configured trace sample rate.

Changes

Similarly to replay, session and profiling, report traceSampleRate within events.

Test instructions

Open the sandbox. Look at generated events. They should have the _dd.configuration.trace_sample_rate property.

Checklist

• Tested locally
• Tested on staging
• Added unit tests for this change.
• Added e2e/integration tests for this change.

[cit-pr-commenter]

Bundles Sizes Evolution

📦 Bundle Name	Base Size	Local Size	𝚫	𝚫%	Status
Rum	162.78 KiB	162.83 KiB	+49 B	+0.03%	✅
Rum Recorder	19.78 KiB	19.78 KiB	0 B	0.00%	✅
Rum Profiler	4.84 KiB	4.84 KiB	0 B	0.00%	✅
Logs	56.62 KiB	56.62 KiB	0 B	0.00%	✅
Flagging	944 B	944 B	0 B	0.00%	✅
Rum Slim	119.90 KiB	119.94 KiB	+41 B	+0.03%	✅
Worker	23.60 KiB	23.60 KiB	0 B	0.00%	✅

🚀 CPU Performance

Action Name	Base CPU Time (ms)	Local CPU Time (ms)	𝚫%
RUM - add global context	0.0045	0.0053	+17.78%
RUM - add action	0.0123	0.0161	+30.89%
RUM - add error	0.0146	0.0136	-6.85%
RUM - add timing	0.0036	0.0027	-25.00%
RUM - start view	0.0037	0.0037	0.00%
RUM - start/stop session replay recording	0.0007	0.0008	+14.29%
Logs - log message	0.0153	0.0144	-5.88%

🧠 Memory Performance

Action Name	Base Memory Consumption	Local Memory Consumption	𝚫
RUM - add global context	25.73 KiB	25.48 KiB	-252 B
RUM - add action	46.34 KiB	47.39 KiB	+1.04 KiB
RUM - add timing	25.03 KiB	24.74 KiB	-290 B
RUM - add error	51.20 KiB	49.87 KiB	-1.33 KiB
RUM - start/stop session replay recording	24.21 KiB	24.45 KiB	+246 B
RUM - start view	421.93 KiB	421.74 KiB	-201 B
Logs - log message	41.22 KiB	42.28 KiB	+1.05 KiB

🔗 RealWorld