A high-performance, structured logging and metrics library for .NET and F#, following OpenTelemetry specifications.
Logary is a high-performance, structured logging and metrics library for .NET applications. It unifies logs and metrics into a single framework, providing professional observability, health monitoring, and analytics capabilities. It follows OpenTelemetry specifications for tracing and structured logging.
.NET and F# developers building applications that require robust logging, metrics collection, and observability features, particularly those in need of structured logging and health monitoring.
Developers choose Logary for its exception-free design, low overhead, and seamless integration of logs and metrics, along with its support for OpenTelemetry standards and idiomatic F# and C# APIs.
Logs and metrics are one! Professional logging, metrics and analytics for your apps.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Full support for structured logging and tracing following OpenTelemetry specifications, ensuring interoperability with modern observability tools as highlighted in the README.
Never throws exceptions and evaluates messages only when log level is enabled, reducing overhead and maintaining application flow, as stated in the key features.
Native F# design with a dedicated Logary.CSharp package, providing idiomatic APIs for both languages, making it versatile for .NET teams.
Unifies logs and metrics in a single framework, allowing developers to add health checks and analytics directly to services, as emphasized in the value proposition.
Setup requires referring to external documentation, and hierarchical logging rules can be intricate, potentially deterring users accustomed to simpler libraries like LibLog.
Has fewer adapters and community extensions compared to established alternatives like Serilog, which may restrict integration options for niche use cases.
While C# is supported via Logary.CSharp, the library's idioms are optimized for F#, leading to potentially awkward usage in pure C# codebases without F# familiarity.