sdk.name for hybrid sdks

[bruno-garcia]

This addresses the sdk.name and allows us to find out, for example:

1. Events from React Native customers
2. Events from the Cocoa SDK (regardless of hybrid SDK that bundled it)
3. By looking at an event know exactly what SDK that is: It's cocoa version X but it was part of the Unity SDK

More importantly, this is simple, solves an actual problem we have right now.
And we use this already on Unreal and Unity. Works as intended.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
develop	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 9, 2023 at 2:45PM (UTC)

[HazAT]

Let's keep it simple! This is good

[bitsandfoxes]

This worked really well for us so far.

[mattjohnsonpint]

I'm good with this, but have a question:

How far along the stack should this extend? Should we be appending ecosystem.flavor, or just ecosystem?

For example, if calling the Cocoa SDK from various .NET SDKs, appending ecosystem.flavor would result in:

• sentry.dotnet => sentry.cocoa.dotnet
• sentry.dotnet.maui => sentry.cocoa.dotnet.maui
• sentry.dotnet.extensions.logging => sentry.cocoa.dotnet.extensions.logging
• etc...

Whereas appending only ecosystem would have them all use sentry.cocoa.dotnet.

It would be great if the doc could clarify this point. Thanks.

[mattjohnsonpint]

... but now that I think about it, unity is a flavor, not an ecosystem. Right? So maybe there's no hard rule to follow?

[bruno-garcia]

... but now that I think about it, unity is a flavor, not an ecosystem. Right? So maybe there's no hard rule to follow?

yeah I think this is accurate