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.

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

SDK Telemetry Data #5

Open
jdorn opened this issue Jan 22, 2023 · 0 comments
Open

SDK Telemetry Data #5

jdorn opened this issue Jan 22, 2023 · 0 comments

Comments

@jdorn
Copy link
Member

jdorn commented Jan 22, 2023

The Problem

The GrowthBook App has no visibility into how the SDKs are being implemented. Because of this, we can't help debug implementation issues, offer hints and warnings, or surface feature usage data within GrowthBook.

Example hints / warnings we could show in GrowthBook:

Error: the id attribute you are passing into the SDK is a number, but it's set up in GrowthBook as a string. < Fix Now >

The feature X hasn't been used in production in over 2 weeks. Do you want to archive it?

Warning: This experiment won't have correct results because you are missing a trackingCallback in your implementation.

Warning: You are using an old version of the Javascript SDK, which has security vulnerabilities. < View Update Instructions >

How the Proxy can Help

Like we do with SSE support, the proxy can broadcast to the SDKs that it supports telemetry events. Then, the SDKs can POST events to the Proxy as it's being used. The proxy can cache and aggregate these events across all of the connected clients and report back to the GrowthBook instance through the REST API periodically.

Note: The telemetry events would not contain any PII. For example, it would only send back the names of attributes being used, not the attribute values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant