Feature request: PDB upload and symbolication support for .NET error tracking

Open
#333 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
backend

Research direction

Start by reviewing the existing .NET client SDK code, particularly error handling and stack trace processing. Examine the symbol upload tooling in the PostHog ecosystem to understand the integration point. The goal is to extend the backend to accept PDB files and use them to resolve stack traces. Check the linked issues #166 and #303 for historical context on frame naming and previous limitations.

Written by the indexing model from the issue text.

Description

enhancement feature/error-tracking

Feature request

Add PDB (Program Database) upload and server-side symbolication support for .NET error tracking, so production exception stack traces can resolve source filenames and line numbers when matching symbols are available.

Problem

The .NET error tracking documentation lists missing PDB support as a limitation and currently links to the closed issue #166. The frame-naming improvements in #303 do not address PDB uploading or symbolication, so that feature needs a dedicated tracker.

As reported by @awright022 in https://github.com/PostHog/posthog-dotnet/issues/166#issuecomment-5779750562, the remaining limitation makes detailed production exception tracing harder and the closed documentation target is misleading.

Proposed scope

  • Provide a supported workflow for uploading .NET PDB symbols, ideally through the existing symbol upload tooling.
  • Capture the identifiers and frame metadata needed to match exceptions to the correct build's symbols.
  • Add backend symbolication support to resolve source filenames and line numbers where matching PDBs provide that information.
  • Consider source-code context when source is optionally included; document supported PDB formats and any limitations.
  • Document the build/upload setup and update the .NET error tracking documentation to point to this feature request instead of #166.

Expected outcome

A production exception with matching uploaded PDBs displays source filenames and line numbers for resolvable frames. Missing or mismatched symbols are handled gracefully without incorrect source attribution.

Context

Dominant language
C#
Stars
47
Forks
23
Avg merge
2d 12h
Merged PRs (30d)
30

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PostHog/posthog-dotnet

All issues in PostHog/posthog-dotnet

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.