feat: disable client-side LD metric forwarding #286
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ntiner1
approved these changes
Nov 6, 2025
Vadman97
force-pushed
the
vadim/no-client-ld-fwd
branch
from
639978b to
2febce0
Compare
Merged
Vadman97
pushed a commit
that referenced
this pull request
Nov 12, 2025
🤖 I have created a release *beep* *boop* --- <details><summary>observability: 0.4.9</summary> ## [0.4.9](observability-0.4.8...observability-0.4.9) (2025-11-12) ### Dependencies * The following workspace dependencies were updated * dependencies * highlight.run bumped to 9.23.0 </details> <details><summary>session-replay: 0.4.9</summary> ## [0.4.9](session-replay-0.4.8...session-replay-0.4.9) (2025-11-12) ### Dependencies * The following workspace dependencies were updated * dependencies * highlight.run bumped to 9.23.0 </details> <details><summary>highlight.run: 9.23.0</summary> ## [9.23.0](highlight.run-9.22.5...highlight.run-9.23.0) (2025-11-12) ### Features * disable client-side LD metric forwarding ([#286](#286)) ([648ad26](648ad26)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Releases @launchdarkly/observability and session-replay 0.4.9 and upgrades highlight.run to 9.23.0 (adds option disabling client-side LD metric forwarding). > > - **Releases**: > - `sdk/@launchdarkly/observability` → `0.4.9` > - `sdk/@launchdarkly/session-replay` → `0.4.9` > - **Dependency upgrade**: > - `sdk/highlight-run` → `9.23.0` > - Feature: disable client-side LaunchDarkly metric forwarding > - **Metadata**: > - Update versions in `.release-please-manifest.json` and package changelogs/package.json files. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 5b82de8. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
After https://github.com/launchdarkly/observability/pull/320 is shipped, we can
switch to server-emitted metrics for the Web SDK.
How did you test this change?
CI
Are there any deployment considerations?
need to make sure server metrics are flowing
Note
Stops forwarding metrics and errors from the LaunchDarkly client; metrics now handled on ingest while init and track events remain.
sdk/highlight-run/src/integrations/launchdarkly/index.tsrecordGaugeanderrornow no-ops (metrics handled on ingest).LD_METRIC_EVENT,LD_ERROR_EVENT,MetricCategory).LD_INITIALIZE_EVENTandLD_TRACK_EVENTviatrack().Written by Cursor Bugbot for commit 2febce0. This will update automatically on new commits. Configure here.