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

Track SDK feature usage #83

Closed
5 tasks done
philipphofmann opened this issue Apr 23, 2024 · 2 comments
Closed
5 tasks done

Track SDK feature usage #83

philipphofmann opened this issue Apr 23, 2024 · 2 comments
Assignees
Milestone

Comments

@philipphofmann
Copy link
Member

philipphofmann commented Apr 23, 2024

Description

Some of our SDKs use integrations, SDK names, or packages to communicate if certain features are turned on, but that doesn’t work for smaller features, such as performanceV2 for mobile, which slightly changes span durations.

To make this happen, we can add a new field features similar to integrations to the SDK event payload and index it in Looker:

"sdk": {
  "name": "sentry.cocoa",
  "version": "8.24.0",
  "integrations": [
    "Crash",
    "MetricKit"
  ], 
  "features": [
      "performanceV2"
  ]
}

Tasks

Preview Give feedback
  1. philipphofmann
  2. philipphofmann

SDKS

Preview Give feedback
  1. philipphofmann

Why should we be doing this?

We want to know about the adoption of our features.

Why now?

Mobile starfish needs to know how many users use performanceV2, a feature flag that changes how SDKs send performance data.

Stakeholder(s)

All SDK teams.

Team(s)

All SDK teams, the data team for indexing the data in Looker, and ingest to accept this data in Relay.

@philipphofmann philipphofmann self-assigned this Apr 23, 2024
philipphofmann added a commit to getsentry/relay that referenced this issue Apr 25, 2024
This PR adds features to the ClientSDKInfo. Related develop docs PR:
getsentry/develop#1244 and team SDK GH issue:
getsentry/team-sdks#83.
@stephanie-anderson stephanie-anderson modified the milestones: [2] Specification, Meta, Protocol Jul 4, 2024
@smeubank
Copy link
Member

Related jira ticket is done ✅

closing unless there is need, and we can reopen to look into any more data needs

@philipphofmann
Copy link
Member Author

It's an optional SDK payload. Thanks for following up on this and closing the issue, @smeubank 💯.

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

3 participants