grafana / grafana/pyroscope-dotnet

Expose native linking issues in some way

Open
#115 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
38
Forks
13
Avg merge
20h 15m
Merged PRs (30d)
10

Description

https://github.com/grafana/pyroscope-dotnet/blob/0c17634653af09befa7bc07b2e1c420b5dc8578c/Pyroscope/Pyroscope/Profiler.cs#L85

Here we swallow an exception silently. We should expose the information of these errors in some way, an logging statement or a metric or a method

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at Pyroscope/Pyroscope/Profiler.cs around line 85 and inspect the exception that is currently swallowed. Determine which error-exposure approach fits the issue—logging, a metric, or a method—and define done as making native linking failures visible to users or operators without silently discarding them.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.