Feature description
Datadog RUM is now integrated (src/components/DatadogInit.tsx, sessionSampleRate 100, sessionReplaySampleRate 0) but only does the SDK's automatic page-view/error tracking — it doesn't instrument anything Reframe-specific yet.
Problem this solves
There's currently no visibility into real-world FFmpeg.wasm engine load times (how long does that ~30MB download actually take for real users on real connections?) or export success/failure rates in production — exactly the kind of thing that would validate or invalidate ideas like issue #181's caching proposal or #14 above.
Proposed solution
Add custom RUM actions/timings around loadFFmpeg() (engine load duration) and around export start/success/failure (useVideoEditor.ts's export flow) via datadogRum.addAction/addTiming. Eventually surface this as a small public status/performance page (even a simple one built from a scheduled export of Datadog's aggregated metrics).
Alternatives considered
Could scope the "public status page" part as a separate follow-up issue once the instrumentation itself lands — the instrumentation is the higher-value, more scoped first step.
Feature description
Datadog RUM is now integrated (
src/components/DatadogInit.tsx, sessionSampleRate 100, sessionReplaySampleRate 0) but only does the SDK's automatic page-view/error tracking — it doesn't instrument anything Reframe-specific yet.Problem this solves
There's currently no visibility into real-world FFmpeg.wasm engine load times (how long does that ~30MB download actually take for real users on real connections?) or export success/failure rates in production — exactly the kind of thing that would validate or invalidate ideas like issue #181's caching proposal or #14 above.
Proposed solution
Add custom RUM actions/timings around
loadFFmpeg()(engine load duration) and around export start/success/failure (useVideoEditor.ts's export flow) viadatadogRum.addAction/addTiming. Eventually surface this as a small public status/performance page (even a simple one built from a scheduled export of Datadog's aggregated metrics).Alternatives considered
Could scope the "public status page" part as a separate follow-up issue once the instrumentation itself lands — the instrumentation is the higher-value, more scoped first step.