Feature request: PDB upload and symbolication support for .NET error tracking
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
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
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
- Original report and implementation discussion: #166
- Frame-naming improvements (separate from this request): #303
- Original limitation documentation: https://github.com/PostHog/posthog.com/pull/17466
- Dominant language
- C#
- Stars
- 47
- Forks
- 23
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 30
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PostHog/posthog-dotnet
-
Flush pending events on AppDomain.ProcessExitPossibly taken @hpouillot claimed this 3 days ago. Openenhancement feature/error-tracking
Difficulty 5/5 Over a week Newbie friendliness 45/100
PostHog/posthog-dotnet#385 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement feature/error-tracking
Difficulty 5/5 Over a week Newbie friendliness 35/100
PostHog/posthog-dotnet#384 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement team/llm-analytics
Difficulty 5/5 Over a week Newbie friendliness 25/100
PostHog/posthog-dotnet#224 ·
Maintainers usually reply within 1 day
-
SDK referencesOpendocumentation
Difficulty 3/5 1-2 days Newbie friendliness 45/100
PostHog/posthog-dotnet#212 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
PostHog/posthog-dotnet#210 · 2 reactions ·
Maintainers usually reply within 1 day
All issues in PostHog/posthog-dotnet
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
quality 提案 要トリアージ
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
The Language and Region lists in Options read to a screen reader as "LanguageInfo { Id = ar, ... }"Openbug localization small ui
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hexide-io/HexIDE#4176 · 1 comment ·
Maintainers usually reply within 1 day
-
kind/chore status/draft
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Altinn/altinn-profile#1102 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MarcelRoozekrans/Rag.NET#1030 ·
Maintainers usually reply within 1 day