Version 1.3.0

1.3.0

Some slight refactors to prepare for future installments of postgres database logging.

Full Changelog: v1.1.1...v1.3.0

Version 1.2.0

New Example Logs:

File logging:

[CRITICAL] WebApplication2/WeatherForecastController - [4/19/2024 11:44:23 PM] Thread #: 13 : Getting weather forecast

Database table:

LogID	LogDate	LoggingClass	LogProject	LogLevel	ThreadId	LogMessage
1	2024-04-19 19:52:09.007	WeatherForecastController	WebApplication2	INFORMATION	10	Getting weather forecast

Features:

• Introducing ManagedThreadId tracing for enhanced logging capabilities. Now, track thread-specific information in your logs effortlessly.

Enhancements:

• Improved logging precision: Class name and calling project are now included in log entries, providing clearer context for debugging and monitoring.
• Enhanced table generation: Additional columns have been added to auto-generated tables, streamlining data visualization and analysis.

Bug Fixes:

No bug fixes were necessary for this release.

Upgrade your logging experience with these new features and enhancements. Happy logging!

v1.1.1 Add a catch to automatically return file logger if cannot connect to db

Full Changelog: v1.1.0...v1.1.1

Add SQL Server logging functionality

Our logging solution adds an adaptive feature that seamlessly adjusts its behavior to ensure uninterrupted operation, even in challenging scenarios. By harnessing this capability, the system automatically provisions a logging table within the specified SQL Server database, eliminating the need for manual setup.

In the event of connectivity issues or if the designated database is unreachable, our system gracefully transitions to a file-based logging mechanism. This dynamic fallback strategy ensures that logging operations continue without disruption, maintaining the integrity and reliability of our logging infrastructure.

Full Changelog: v0.0.1...v1.1.0

v0.0.1

Full Changelog: https://github.com/bradyscode/LogsByBrady/commits/v0.0.1