feat(Unity): Added Metrics

[bitsandfoxes]

Following the 4.1.0 release and the docs for .NET

• docs(dotnet): Add .NET to metrics getting started #16262
• docs(dotnet): Add metrics documentation for .NET #16054

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
sentry-docs	Ready	Preview, Comment	Feb 11, 2026 2:41pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ignored		Feb 11, 2026 2:41pm

[sentry]

Bug: The Unity metrics usage documentation incorrectly states that metrics are enabled by default, but the setup guide requires explicit enablement, leading to silent failures for users.
_{Severity: MEDIUM}

Suggested Fix

In platform-includes/metrics/usage/unity.mdx, change the first line from "Metrics are enabled by default. Once you initialize the SDK..." to "Once metrics are enabled, you can send metrics...". This removes the false claim and directs users to the setup guide implicitly.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: platform-includes/metrics/usage/unity.mdx#L1

Potential issue: The documentation file `platform-includes/metrics/usage/unity.mdx`
claims "Metrics are enabled by default." However, the corresponding setup documentation
(`platform-includes/metrics/setup/unity.mdx`) provides explicit steps to enable them,
implying they are disabled by default. This contradiction will cause developers who
follow the usage guide to see their metrics fail to be sent silently, as they will miss
the required setup step. This leads to a confusing user experience and wasted debugging
time.

_{Did we get this right? 👍 / 👎 to inform future reviews.}