Synergy.Monitor.Client 1.0.1

Synergy.Monitor.Client

Drop-in Wolverine middleware for Synergy Bounded Contexts. Automatically captures every Wolverine handler execution and publishes a WorkMonitoringEvent to the monitor.domain-events Kafka topic — with zero changes to your existing handlers.

Quick Start

1. Install the package

dotnet add package Synergy.Monitor.Client

2. Register services in Program.cs

// Register monitor services (before builder.Build())
builder.Services.AddSynergyMonitoring(builder.Configuration);

// Add middleware to Wolverine
builder.Host.UseWolverine(opts =>
{
    opts.AddSynergyMonitoringMiddleware();
});

3. Add configuration to appsettings.json

{
  "SynergyMonitor": {
    "BoundedContext": "YourBCName",
    "KafkaBootstrapServers": "your-kafka-broker:9092",
    "TopicName": "monitor.domain-events",
    "Enabled": true
  }
}

That's it. Every Wolverine handler in your application is now automatically monitored.

What Gets Captured Automatically

Before/After Diff Tracking (Optional)

For update operations where you need old vs new entity state, inject KafkaMonitorPublisher directly into your handler and publish manually:

public class UpdateUserCommandHandler(
    IUserRepository repo,
    KafkaMonitorPublisher monitorPublisher)
{
    public async Task Handle(UpdateUserCommand command, CancellationToken ct)
    {
        var existing = await repo.GetByIdAsync(command.Id, ct);
        var oldJson  = JsonSerializer.Serialize(existing);

        existing.Update(command);
        await repo.SaveAsync(existing, ct);

        await monitorPublisher.PublishAsync(new WorkMonitoringEvent(
            BoundedContext: "Admin",
            EventType:      "UpdateUser",
            TenantId:       command.TenantId,
            OccurredAt:     DateTime.UtcNow,
            ActorUserId:    command.ActorUserId,
            ActorName:      command.ActorName,
            SubjectId:      existing.Id,
            SubjectType:    "User",
            OldValues:      oldJson,
            NewValues:      JsonSerializer.Serialize(existing),
            EventId:        Guid.NewGuid()
        ), ct);
    }
}

Configuration Reference

Safety Guarantee

The middleware never throws and never blocks your handler. If Kafka is unavailable, the event is silently logged and dropped. Your handler always completes successfully regardless of monitoring state.

Requirements

• .NET 8
• WolverineFx 5.x
• ASP.NET Core (for IHttpContextAccessor — registered automatically by AddControllers())

License

MIT