55A complete Remote Config proxy system for browser Live Debugger consisting of:
66
77### 1. RC Proxy Service (` sandbox/rc-proxy/ ` )
8+
89- ** Client Tracker** : Tracks active browser clients with 30s TTL (like Datadog Agent)
910- ** RC Client** : Communicates with Datadog RC backend using protobuf
1011- ** Express Server** : Serves probes via HTTP GET endpoints
1112- ** Background Polling** : Automatically polls RC when clients are active
1213
1314### 2. Browser SDK Integration (` packages/live-debugger/ ` )
15+
1416- ** Remote Config Module** : Polls proxy and syncs probes automatically
1517- ** Init Configuration** : Added ` remoteConfigProxyUrl ` option
1618- ** Probe Synchronization** : Adds, removes, and updates probes dynamically
1719
1820### 3. Test Page (` sandbox/live-debugger-test.html ` )
21+
1922- Simple UI to test the RC proxy integration
2023- Shows active probes, proxy health, and fired probes
2124- Test functions to trigger instrumented code
@@ -44,6 +47,7 @@ npm start
4447The proxy will start on http://localhost:3030
4548
4649You should see:
50+
4751```
4852✅ Server running on port 3030
4953 - Probes endpoint: http://localhost:3030/probes?service=my-app
@@ -74,6 +78,7 @@ This creates `packages/live-debugger/bundle/live-debugger.js`
7478Open ` sandbox/live-debugger-test.html ` in your browser.
7579
7680The page will:
81+
7782- Initialize Live Debugger with RC proxy URL
7883- Start polling the proxy every 5 seconds
7984- Display active probes from Datadog
@@ -106,18 +111,22 @@ The page will:
106111## Troubleshooting
107112
108113### Proxy says "No active clients"
114+
109115This is normal when no browsers are connected. Open the test page and it will start polling.
110116
111117### Browser not receiving probes
118+
1121191 . Check browser console for errors
1131202 . Verify ` remoteConfigProxyUrl ` is correct
1141213 . Check proxy ` /health ` endpoint
1151224 . Ensure probes are configured in Datadog for service ` browser-test-app `
116123
117124### Proxy returning 401 from Datadog
125+
118126Check your ` DD_API_KEY ` in ` .env ` file is valid and has RC scope.
119127
120128### Probes not firing
129+
1211301 . Verify probes are loaded (check "Current Probes" section)
1221312 . Ensure probe targets match function names
1231323 . Check browser console for Live Debugger errors
@@ -143,18 +152,21 @@ Check your `DD_API_KEY` in `.env` file is valid and has RC scope.
143152## Architecture Details
144153
145154### RC Proxy Files
155+
146156- ` index.js ` - Main Express server and endpoints
147157- ` rc-client.js ` - Datadog RC protocol client (protobuf)
148158- ` client-tracker.js ` - Active client tracking with TTL
149159- ` config.js ` - Environment configuration
150160- ` remoteconfig.proto ` - Protobuf schema
151161
152162### Browser SDK Files
163+
153164- ` packages/live-debugger/src/entries/main.ts ` - Init with RC config
154165- ` packages/live-debugger/src/domain/remoteConfig.ts ` - RC polling and sync
155166- ` packages/live-debugger/src/domain/probes.ts ` - Probe management
156167
157168### Key Features
169+
158170- ✅ Dynamic client tracking (30s TTL)
159171- ✅ Protobuf protocol compatibility
160172- ✅ Hardcoded to LIVE_DEBUGGING only
@@ -165,6 +177,7 @@ Check your `DD_API_KEY` in `.env` file is valid and has RC scope.
165177## Support
166178
167179For questions or issues:
180+
1681811 . Check the proxy logs for errors
1691822 . Check browser console for SDK errors
1701833 . Verify RC is enabled in your Datadog org
@@ -173,4 +186,3 @@ For questions or issues:
173186## License
174187
175188Apache-2.0
176-
0 commit comments