Skip to content

docs(dotnet): Document RecordTransaction for already-completed transactions#18743

Open
jamescrosswell wants to merge 1 commit into
masterfrom
docs/dotnet-record-transaction
Open

docs(dotnet): Document RecordTransaction for already-completed transactions#18743
jamescrosswell wants to merge 1 commit into
masterfrom
docs/dotnet-record-transaction

Conversation

@jamescrosswell

Copy link
Copy Markdown
Collaborator

DESCRIBE YOUR PR

Documents the new SentrySdk.RecordTransaction API from getsentry/sentry-dotnet#5333, which records transactions and spans that already completed elsewhere (e.g. work measured on another machine and replayed through a proxy) with explicit start timestamps and durations.

  • Adds a new Record Already-Completed Transactions section as the third section of the .NET custom instrumentation page, via a new platform-includes/performance/record-completed-transactions/dotnet.mdx include.
  • Covers the differences from StartTransaction: explicit timing, sampling skipped (BeforeSendTransaction still runs), and clean-scope capture with ConfigureScope for attaching origin-trace data.

Note: the version alert says 6.8.0 — the SDK PR merged just after the 6.7.0 release cut, so this assumes it ships in the next release. Should be confirmed (and this PR held) until that release is out.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

  • Urgent deadline (GA date, etc.):
  • Other deadline:
  • None: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
    Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

🤖 Generated with Claude Code

…ctions

Adds a third section to the .NET custom instrumentation page covering the
RecordTransaction API added in getsentry/sentry-dotnet#5333, which records
transactions and spans that completed elsewhere (e.g. replayed through a
proxy) with explicit timing.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 16, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
sentry-docs Ready Ready Preview Jul 16, 2026 8:59am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
develop-docs Ignored Ignored Jul 16, 2026 8:59am

Request Review

@codeowner-assignment
codeowner-assignment Bot requested a review from a team July 16, 2026 08:51
@jamescrosswell
jamescrosswell marked this pull request as ready for review July 17, 2026 03:02
@@ -0,0 +1,40 @@
## Record Already-Completed Transactions

<Alert>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The documentation references version 6.8.0 for a new .NET SDK feature, but this version is tentative and unconfirmed. The feature may ship in a different release.
Severity: MEDIUM

Suggested Fix

Hold the merge of this pull request until the .NET SDK version containing the RecordTransaction feature is officially released. Once the version is confirmed, update the availableSince alert in the documentation to reflect the correct version number.

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/performance/record-completed-transactions/dotnet.mdx#L3

Potential issue: The documentation for the new `RecordTransaction` feature in the .NET
SDK specifies it is available since version `6.8.0`. However, this version number is an
unconfirmed assumption, as noted in the pull request description. Publishing this
documentation before the SDK version is finalized could lead to users on version `6.8.0`
not finding the API if it ships later, or users on earlier versions encountering runtime
errors. This will likely cause user confusion and support tickets.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant