SplatDev.Logger 1.0.2

SplatDev.Logger

Lightweight, static-class, database-backed logger using Entity Framework Core with SQL Server. Fire-and-forget logging that never crashes the application — all exceptions are silently swallowed.

Compatibility

Installation

dotnet add package SplatDev.Logger

What's implemented

Logging API

The static SplatDev.Logger.Logger class provides two overloads:

• Log(string message, string details = "", LogType type = LogType.Info, string user = "System") — writes a log entry with message, optional details, severity, and user identifier.
• Log(string message, Exception exception, LogType type = LogType.Error, string user = "System") — writes a log entry from an exception, capturing Message, StackTrace, and InnerException.Message in the Details column.

Each call creates a short-lived LoggerDbContext, inserts the entry, saves changes, and disposes. All exceptions are caught and discarded — logging failures never propagate.

Log entity

The Log entity maps to a SQL Server table:

LogType enum

LoggerDbContext

A standard EF Core DbContext with DbSet<Log> Logs. Constructed with DbContextOptions<LoggerDbContext>. The static Logger creates instances internally using UseSqlServer(ConnectionString).

Configuration

Connection string

Set the static ConnectionString property before any logging calls:

SplatDev.Logger.Logger.ConnectionString = "Server=localhost;Database=MyDb;...";

This is typically done once at application startup.

Database table

Create the Logs table using EF Core migrations or raw SQL:

CREATE TABLE [Logs] (
    [Id]       INT IDENTITY(1,1) NOT NULL PRIMARY KEY,
    [DateTime] DATETIME2         NOT NULL,
    [LogType]  INT               NOT NULL,
    [Message]  NVARCHAR(MAX)     NULL,
    [Details]  NVARCHAR(MAX)     NULL,
    [User]     NVARCHAR(450)     NULL
);

Appsettings

No appsettings keys are required. The package does not bind any options POCO. Connection string management is the consumer's responsibility — wire it from IConfiguration, environment variables, or a secrets manager:

var connectionString = builder.Configuration.GetConnectionString("DefaultConnection");
SplatDev.Logger.Logger.ConnectionString = connectionString;

Usage

using SplatDev.Logger;

// Info log
Logger.Log("User registered", details: "email=user@example.com");

// Warning log
Logger.Log("Rate limit approaching", type: LogType.Warning);

// Error log from exception
try
{
    // ... risky operation
}
catch (Exception ex)
{
    Logger.Log("Checkout failed", ex, type: LogType.Error, user: "customer@example.com");
}

Dependencies

Caveats

• No DI integration. Logger is a static class. It does not support ILogger<T> or structured logging. For ILogger-based logging, configure the standard ASP.NET Core logging pipeline instead.
• Swallowed exceptions. All catch { } blocks silently discard logging failures. This guarantees logging never crashes the application, but it means database connection failures or schema mismatches go completely undetected. Monitor your Logs table periodically to confirm entries are being written.
• Short-lived DbContext. Each Log() call creates and disposes its own DbContext. This is fine for low-to-moderate volume but may create connection pressure at scale. For high-throughput scenarios, consider a queued background writer.
• No migration support. The package does not include EF Core migrations. You are responsible for creating the Logs table in your database.
• DateTime.Now. Timestamps use server-local time, not UTC. If your servers span time zones, convert to UTC at query time.

SplatDev.Logger — part of the SplatDev.Umbraco.Plugins suite. Licensed under MIT. © SplatDev Ltda.

Changelog

1.0.2 — 2026-08-24

Removes a dashboard screenshot that showed an error toast. It was captured against a site where this plugin's API was unreachable, so it advertised a broken dashboard. No screenshot is better than a misleading one; a replacement will be taken against a working install.

1.0.1 — 2026-08-24

Package metadata only: the listing now carries an icon and search tags, and the project and repository links point at the organisation that actually hosts this code. No code changes.

1.0.0 — 2026-08-24

This package now keeps a changelog. Earlier releases predate it and are not reconstructed here — consult the repository history for those. From this version on, every release records what changed for someone using it.