[skill-drift] feat(sentry-dotnet-sdk): add OTLP export integration#142
Merged
HazAT merged 1 commit intoMay 29, 2026
Conversation
Automated drift-fix run. Co-Authored-By: Claude (claude-sonnet-4-5) <noreply@anthropic.com>
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Comment on lines
+356
to
366
| }) | ||
| .ConfigureServices(services => | ||
| { | ||
| services.AddOpenTelemetry().WithTracing(builder => | ||
| { | ||
| builder | ||
| .AddHttpClientInstrumentation() | ||
| .AddSentryOtlpExporter("___YOUR_DSN___"); // route spans to Sentry OTLP endpoint | ||
| }); | ||
| }) | ||
| .Build(); |
There was a problem hiding this comment.
Bug: The documentation for Azure Functions instructs users to install Sentry.OpenTelemetry but provides a code example that requires the Sentry.OpenTelemetry.Exporter package, causing a compilation failure.
Severity: MEDIUM
Suggested Fix
Update the package installation instructions for Azure Functions to specify Sentry.OpenTelemetry.Exporter instead of Sentry.OpenTelemetry. Also, update the package mapping table around line 79 to reflect this change, ensuring consistency throughout the document.
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: skills/sentry-dotnet-sdk/SKILL.md#L337-L366
Potential issue: The installation guidance for Azure Functions in `SKILL.md` directs
users to install the `Sentry.OpenTelemetry` package. However, the accompanying code
example (lines 338-365) uses `AddSentryOtlpExporter()` and `UseOtlp()`, which are
exclusive to the `Sentry.OpenTelemetry.Exporter` package. A developer following these
instructions will encounter compilation errors because the installed package does not
contain the required methods. The package mapping table and installation commands were
not updated to reflect the change to an OTLP-based example.
Did we get this right? 👍 / 👎 to inform future reviews.
HazAT
deleted the
skill-drift/sentry-dotnet-sdk-skill-drift-feat-sentry-dotnet-sdk-add-o-1780044237
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Warning
Auto-generated from external SDK content. Review all links and code suggestions before acting on them.
Summary
Adds documentation for the new OTLP export integration introduced in Sentry .NET SDK 6.5.0 (PR #4899). This is now the recommended approach for OpenTelemetry integration.
Changes
references/tracing.md: Added new "Option 1: OTLP Export (Recommended)" section documenting:Sentry.OpenTelemetry.ExporterpackageAddSentryOtlpExporter()TracerProvider extensionUseOtlp()SentryOptions extensionSKILL.md:Why This Matters
The OTLP export approach:
Upstream Changes
Based on:
Sentry.OpenTelemetry.Exporterpackage and OTLP supportSource PRs