One of the most visible benefits of the Developer Data framework is its native support for diagnostics. This new capability relies on your project’s diagnostic data—data that’s essential to maintain the Unity engine and improve performance and stability at scale. Introduced in Unity 6.2 and enabled by default for new projects, this data allows for detailed insights into the health of your game in the wild.

When visualized via Diagnostics in the Unity Dashboard, you gain access to real-time visibility into your game’s health across platforms, devices, and builds. You can filter crash reports by Unity version, group issues by root cause, and even drill into performance trends by geography or OS. It also includes crash reports, exception logs, basic telemetry, and other signals related to performance and responsiveness. In addition, it includes much-requested reporting on Application Not Responding (ANR) errors. Learn more about the data available in Diagnostics.

This essential data is also the foundation for the Developer Data, more broadly, that Unity collects on your behalf. The collection of diagnostic data establishes the channel through which all Developer Data is collected. And since diagnostic data is still your data, and you may need to disable collection in certain contexts (for example, based on a specific platform’s certification requirements) you can do so at the Platform and Build Profile levels, along with for the entire project via the Unity Editor. For more information, refer to Configure diagnostics in the Editor.

Diagnostics is at the forefront of Unity’s investments in performance and stability. The previous Cloud Diagnostics service is still available for existing users, but in future this will be replaced by the new Diagnostics experience.