In this article, developers will learn how to build an efficient OpenTelemetry logs pipeline with .NET. They will learn the key concepts of OpenTelemetry logs, how to integrate OpenTelemetry into their .NET application, and how to configure the logs pipeline to send logs to a preferred backend for analysis and visualization. The Microsoft.Extensions.Logging library provides native support for logging in .NET applications, allowing developers to utilize its simple and extensible logging API to log messages of varying severity levels. However, OpenTelemetry focuses on augmenting the logs produced by applications and provides a mechanism to correlate the logs with other signals. The OpenTelemetry logging signal does not aim to standardize the logging interface but rather hooks into existing logging facilities already available in programming languages. Developers can arrange OpenTelemetry components in the form of a pipeline, which offers flexibility and customizability, enabling users to tailor the pipeline to their specific requirements and integrate it with their preferred telemetry analysis tools. The pipeline consists of logger providers, loggers, log records, log record processors, and log record exporters. In this example, a custom log processor was added to include state information in the application logs. Developers can use the .NET logging API to log messages, which will be collected by OpenTelemetry and exported to the configured exporters. The article concludes with an overview of how to gather information from recorded logs and provides resources for further learning.