Topic
Observability
Instrument systems with logs, metrics and traces. Follow requests and measure the cost of collecting evidence.

Observability in .NET: Telemetry Cost, Schema Drift and One Trace
A map of .NET observability: what telemetry costs before the sampler decides, what a full pipeline drops, how its schema ages, and how one order reads as one trace across a queue.

Telemetry Is a Schema: One Contract for a .NET AI Platform
A library upgrade renamed gen_ai.system and zeroed a dashboard. Treat .NET AI telemetry as a schema: contract tests, an adapter, cardinality limits and redacted prompts.

Trace One Order Across HTTP, a Queue and Retries in .NET
Make an Aspire service explain itself before the first incident: carry trace context through RabbitMQ, keep failed retries visible, and know what survives when traces are sampled out.

Telemetry Event Formats: Units, Versions, Bytes and CPU in .NET
One latency sample in five encodings, byte by byte: why tolerant readers turn 1.5 ms into 1.5 s, and what JSON, Protobuf, MessagePack and OTLP cost on .NET 9.

The Observer Effect: What .NET Telemetry Costs Before Sampling
A sampled-out span can still build its payload, and a stalled exporter silently drops spans. Measure both with OpenTelemetry .NET and add the guards and counters that fix them.