HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dotnet
diagnostics
C++2019–2024
dotnet / diagnostics

diagnostics

This repository contains the source code for various .NET Core runtime diagnostic tools and documents.

2Distinct people
2Mentions
0Explicit recommenders
1.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This repository contains the source code for various .NET Core runtime diagnostic tools and documents.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year2 dated mentions

Observed mentions: 2019-05-20 09:20:22 UTC to 2024-09-25 20:11:56 UTC.

012019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC110
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

2 sources
There are multiple ways to go about this in .NET - the instrumentation for the networking stack is not missing: https://learn.microsoft.com/en-us/dotnet/fundamentals/networ... https://learn.microsoft.com/en-us/dotnet/fundamentals/networ... It is, however, not dependent on VS Code and exists standalone, so it requires integration work if there's custom tooling at play. It is what most vendor SDKs that offer observability do. There are CLI tools which consume the EventSource events and the EventPipe itself which can be used to access them in and out of process: https://learn.microsoft.com/en-us/dotnet/core/diagnostics/ev... EventPipe/EventSource and DiagnosticPort are very powerful APIs however that cover much deeper instrumentation scenarios, so they are going to require writing a connector for the product that wants to integrate with them
Read the rest
. There is already an implementation in shared code that is used by e.g. dotnet-trace which can be found here https://github.com/dotnet/diagnostics/tree/main/src/Microsof... but it can be a bit convoluted to read through.
In Launch HN: Haystack (YC S24) – Visualize and edit code on an infinite canvas

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.