Writing
Logs and Artifacts: Pipeline Breadcrumbs
Make long-running pipelines explain their work through numbered steps, ordered artifacts and a run manifest. Preserve evidence to investigate exceptions and incorrect results.
Topic
Structured Logging
Structured logging records named properties alongside an event so people and tools can filter, correlate, and investigate failures without parsing message text.
4 pages
Writing
High Performance Logging and Custom Objects
An application logging adapter can accept a DTO and expose its fields as structured state. ILogger.Log<TState> separates that context from the formatted message.
Writing
Programming to Exceptions, Part 2: Diagnostics and Boundaries
One log record should explain a failure to the support team. Exceptions carry a message, reason, action and context, are translated where meaning is known, and are logged once.
Writing
Programming to Exceptions, Part 3: Logging and Progress
Each failure is logged once at the entry point, with its facts as Application Insights custom dimensions for KQL queries and alerts. A shared progress logger reports long-running work.