Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Forwarding events can produce incorrect user counts #53

Closed
eli-darkly opened this issue Dec 19, 2018 · 1 comment
Closed

Forwarding events can produce incorrect user counts #53

eli-darkly opened this issue Dec 19, 2018 · 1 comment

Comments

@eli-darkly
Copy link
Contributor

It's come to our attention that when ld-relay is configured to proxy analytics events, it always forwards the events to the same LaunchDarkly endpoint—the one that is normally used by server-side SDKs—even if the events came from a mobile or browser client. LaunchDarkly still accepts the events, but the problem is that your usage statistics are partly based on how the events are received, so if 50% of the users were coming from a server-side client and 50% from a mobile client, they will be incorrectly counted as 100% server-side.

This will be fixed in the next release of ld-relay.
@eli-darkly eli-darkly mentioned this issue Dec 20, 2018
Merged
@eli-darkly
Copy link
Contributor Author

Fixed in version 5.5.1.

LaunchDarklyCI pushed a commit that referenced this issue Nov 7, 2019
@atrakh
Merge pull request #53 from launchdarkly/at/ch20965/ld-relay-add-conf…
98e41f7 
…igurable-global-datadog

Add global tag configuration for datadog exporter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eli-darkly