Sidemark: Active Telemetry Comments for C#
Sidemark introduces a novel approach to telemetry in C# by using comments as non-invasive instrumentation. This method allows developers to maintain code clarity while still capturing essential telemetry data. By utilizing specific comment syntaxes, Sidemark transforms comments into telemetry calls during the build process without altering the original source code.
- ▪Sidemark uses comment syntaxes to create telemetry calls in C# code.
- ▪The approach aims to reduce code clutter caused by traditional telemetry instrumentation.
- ▪Sidemark operates as an MSBuild task, rewriting annotated code into telemetry calls at build time.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/david_whitney/sidemark-active-telemetry-comments-for-c-1bai |
| Publication time | Fri, 29 May 2026 12:42:17 +0000 |
| Retrieval time | 2026-05-29T12:50:00.410Z |
| Last seen | 2026-05-29T12:50:00.410Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 6nM4nPqfPfvh |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 370904) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } David Whitney Posted on May 29 • Originally published at davidwhitney.co.uk Sidemark: Active Telemetry Comments for C# #dotnet #opensource #opentelemetry #observability OpenTelemetry has quietly become table stakes. That's a good thing, but if you've instrumented a real codebase, you know the tax. A method that does one obvious thing slowly fills up with StartActivity, SetTag, AddEvent, SetStatus.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).