You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/telemetry.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Every instrument is **zero-cost when no listener is attached**: counters and act
6
6
7
7
## Activity (Distributed Tracing)
8
8
9
-
A single span is emitted from `ExpressiveSharp.ActivitySource`:
9
+
A single span is emitted from the `ExpressiveSharp``ActivitySource` (the source's name is also exposed as the constant `ExpressiveDiagnostics.SourceName`):
Copy file name to clipboardExpand all lines: docs/reference/troubleshooting.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -324,12 +324,17 @@ public double TotalWithTax => Total * (1 + TaxRate); // Total is inlined
324
324
325
325
### How do I see what ExpressiveSharp is doing at runtime?
326
326
327
-
Subscribe to the `ExpressiveSharp``ActivitySource`, `Meter`, or `EventSource`. The metrics surface cache hit/miss ratios and per-expansion timings; the EventSource surfaces failure paths that ExpressiveSharp recovers from silently — registry static-ctor failures, hot-reload reset failures, and `[ExpressiveFor]` collisions.
328
-
329
-
The fastest path is `dotnet-trace`, which needs no code changes:
327
+
ExpressiveSharp emits three independent signals on the `ExpressiveSharp` source name — each requires a different out-of-process tool:
0 commit comments