Unity Cloud Diagnostics Alternatives — What to Check During the Built-In Diagnostics Transition

Unity Cloud Diagnostics is being folded into Unity 6.2+'s built-in Diagnostics. If your team relies on Cloud Diagnostics for crashes and exceptions, this transition is a natural moment to re-evaluate. Here's what stays and what you may need to fill in.

What Cloud Diagnostics gave you

• Crash and Exception Reporting — automatic collection of crashes and exceptions
• User Reporting (com.unity.cloud.userreporting) — reports carrying metadata, events, sampled metrics, a screenshot, and attachments
• Bundled with UGS — no extra cost if you're already on the platform

For teams already on UGS, "catch crashes at no extra cost" was the real value here. It's a feature you can flip on without a budget approval cycle, and that gap matters more the smaller the team. That premise doesn't change with the move to built-in Diagnostics.

The limits — no video, shallow game-state context

Cloud Diagnostics has no video capture. User Reporting carries one screenshot plus metadata and sampled metrics — nothing more. That's enough when a crash narrows down to a stack trace on its own, but for bugs where you have to reconstruct "how did it get into this state" — broken UI, a character in the wrong place — a single screenshot doesn't let you retrace the path. Say a character clips through a wall on a specific piece of terrain: the screenshot only shows the result — the character already inside the wall — not which inputs or movement path got it there. Reconstructing that path still falls to a person re-reading video or logs by hand. Shallow game-state context is the accurate way to put it.

Four axes worth checking during the transition

Whether or not you switch tools, this is a good moment to check four things.

1. Data ownership — where reports are stored and who can access them
2. On-prem requirements — is this a project where data can't leave your network?
3. Issue tracker integration — how many steps between a report and a ticket?
4. Platform coverage — are you shipping to console, mobile, and PC at once?

These four aren't independent. If a publisher contract or internal security policy means data can't leave a given region, data ownership and on-prem requirements collapse into the same question, and cloud-SaaS-only options get filtered out before you even compare features. On the other end, a small single-platform project with reports staying entirely in-house may not need to weigh any of the four seriously — in that case the transition is closer to a routine package update than a real decision point.

Alternatives split by category

We sorted the alternatives by category in Unity Bug Reporting Tools Compared. Looking only at the gap Cloud Diagnostics leaves:

• General error monitoring (Sentry) — stronger exception aggregation and trending, but still no video
• Mobile app SDKs (Bugsee) — video, network, and logs together, but built for mobile apps first
• Free combo (Unity Recorder + OBS) — no cost, but no way to sync video with logs and game state

All three only close part of the gap Cloud Diagnostics leaves behind — none of them covers crash reporting and video/timeline sync at zero cost at the same time. So the useful order is to first pin down exactly what the team is missing, then pick the category from there. A closer look at the User Reporting package itself is covered separately in our review.

Summary

The transition forces a decision point, but it doesn't force a tool switch. If crash and exception reporting is all you need, built-in Diagnostics is enough. Only reach for a different category once you need video, or a shared timeline with game state. The test is simply what you're missing right now, not the transition itself. If none of the four axes above — data ownership, on-prem, issue tracker integration, platform coverage — actually apply, this transition is an event you can let pass rather than a reason to re-pick your tooling.

Rekon is the option that fills the video and timeline gap — a Unity 2022.3+ plugin that, on one hotkey (Ctrl/Cmd + Shift + B) in Play Mode, captures roughly the last 60 seconds of video, logs, and game state (scene, device info) on one timeline, then connects to a Jira issue from the dashboard. It's not a competitor to Cloud Diagnostics — it's meant to sit next to crash reporting for the moments that need video.