"Diagnostics" vs. "Cloud Diagnostics" integrations

DevOps
,
1

Can someone explain to me “Diagnostics” vs “Cloud Diagnostics”? I’m so lost here!

[1] I thought “Diagnostics” was the new one but I can’t find it in my dashboard?

Screenshot 2026-06-17 at 09.44.56
Screenshot 2026-06-17 at 09.44.56527×417 27.1 KB

[2] Of which one is “User Reports” a feature? Is it deprecated? What is happening?

I am using Unity.Services.UserReporting; . Is that a feature of Diagnostics or Cloud Diagnostics?

[3] My Slack integration messages for “User Reports” no longer link to the report. In general, the messages seem broken.

Screenshot 2026-06-17 at 09.48.03
Screenshot 2026-06-17 at 09.48.03955×407 60.6 KB

[4] What is up with deprecation of “Diagnostics Bug Report Received”?

Screenshot 2026-06-17 at 09.49.38
Screenshot 2026-06-17 at 09.49.381344×1014 150 KB

[5] Is “Diagnostics Bug Report” the same as “User Report” ?

2

Hi @noio,

I would be happy to help clarify these points for you! Here is a breakdown of what is happening with the Diagnostics services:

[1] Diagnostics vs. Cloud Diagnostics — Which is which and where is it?

Diagnostics is the new successor to Cloud Diagnostics, introduced in Unity 6.2. The legacy Cloud Diagnostics service is currently deprecated and being phased out.

The new Diagnostics experience is built on the Developer Data framework and no longer appears as a separate menu section in the left navigation of the dashboard. Instead, you can find it here: cloud.unity.com → Select your project → Project Overview → “Diagnostics” widget → “View Diagnostics”

If you don’t see it there, ensure your project is on Unity 6.2+. It is enabled by default for new projects, but for existing projects migrating to 6.2+, you need to enable it manually in the Editor under Edit → Project Settings → Services → Diagnostics.

[2] Unity.Services.UserReporting — Which service does it belong to, and is it deprecated?

User Reporting is NOT deprecated. Historically, it was bundled as a sub-feature of the legacy Cloud Diagnostics suite. However, it is now maintained as a separate, standalone package rather than being built into the new Engine Diagnostics service dashboard.

It is not going away, and you can continue using it by ensuring you have the Unity User Reporting package installed:

  • Package: com.unity.services.user-reporting
  • Namespace: Unity.Services.UserReporting
  • Recommended version for Unity 6: 2.0.15 or newer

It remains fully compatible with the new Diagnostics service, and you don’t need to change your code if you’re already using v2.0+.

[3] Slack messages for User Reports are broken

We have seen similar reports regarding this issue in Unity 6.2 and 6.3. However, a fix has recently been deployed, and your Slack notifications should now properly include the link to the report.

If you are still experiencing broken messages, please submit a support ticket so our team can investigate further: Diagnostics support ticket

[4] The deprecation of “Diagnostics Bug Report Received”

The warnings in your screenshot indicate that these specific event topics belong to the legacy Cloud Diagnostics service, which is being phased out.

Event topics that use legacy terminology like “Problem” or “Bug Report” (e.g., Diagnostics New Problem, Diagnostics Bug Report Received) are tied specifically to the old infrastructure. As users transition to the new Diagnostics service, these are being deprecated in favor of new event topics that use updated terminology, such as Diagnostics New Issue and Diagnostics New Issue Version.

[5] Is “Diagnostics Bug Report” the same as “User Report”?

Yes, in the context of Unity’s diagnostic services, “Diagnostics Bug Report” and “User Report” refer to the same underlying system, but they represent different parts of the pipeline:

  • User Reporting (The Service/SDK): This is the Unity service and SDK feature that allows testers and players to submit feedback, screenshots, and bug reports directly from within your application.
  • Diagnostics Bug Report (The Event Topic): When you set up integrations (like Slack or email notifications), “Diagnostics Bug Report Received” is the specific name of the event topic that gets triggered whenever a player successfully submits a User Report.

I hope this helps clear things up! Please let me know if you have any other questions.

3

Huh.

I am still confused.

  • “Diagnostics New Problem :warning:” becomes “New Issue” ?
    • :backhand_index_pointing_right: Issues are the uncaught exception stack traces reported on the diagnostics dashboard, yeah?
  • What is the new name for “Bug Report” then? Since “Diagnostics Bug Report Received :warning:” is marked as deprecated.

Should I now be using “Cloud Diagnostics Bug Report Received” or Diagnostics Bug Report Received :warning: ? The former does not have a deprecated marker, but Cloud Diagnostics is entirely deprecated?

Just rephrasing all of the above: Where is the webhook for User Reports going?