Nicholas Blumhardt

@nblumhardt.com

Founder at @datalust.co, core maintainer for #serilog, original #autofac author, long-ago-.NET PM. Deep down the #rustlang rabbit hole. Also at https://nblumhardt.com/@nblumhardt. 🇦🇺

Twelve months of one of the most intense dev projects I've worked on. We had a lovely time designing our ideal interaction model, then embarked on the *massive* task of building a whole new distributed columnstore to drive it... 😅

Seq@datalust.co · 3mo ago

Seq 2026.1 previews are now shipping weekly! These add support for OpenTelemetry metrics ✨ and a completely new metrics discovery and visualization UI. Check out this post for how to get started: datalust.co/blog/metrics...

Quick question; we have a lot of variation between monitors on our dev machines. On yours, do the charts in this screenshot appear in little white boxes against a more grey background, or is the whole chart area just one big flat white canvas? Thanks! 😀

A development-time screenshot of the Seq 2026.1 Metrics screen, showing a grid of charts (and not much interesting data).

Signed up with @opentalk.eu after investigating a few Zoom alternatives; so far, so good! It's surprising just how much functionality is "table stakes" in that space, now; it's nice to see a segment with a bunch of viable offerings.

I am excited to announce SharpDbg - a new cross platform, managed .NET debugger, written completely in C#! (No C++ required 💪) ⭐ Star it on GitHub! github.com/MattParkerDe... SharpDbg implements the VS Code Debug Adapter Protocol (DAP), ...

GitHub - MattParkerDev/sharpdbg: SharpDbg is a .NET managed code debugger supporting the VSCode DAP, implemented completely in C#/.NET

SharpDbg is a .NET managed code debugger supporting the VSCode DAP, implemented completely in C#/.NET - MattParkerDev/sharpdbg

github.com

The Seq team rounded out 2025 at DDD Adelaide and then DDD Brisbane a month later, both fantastic community-oriented conferences. Here's Ashley Mannix sharing his experiences shepherding Seq's high-performance #rustlang codebase through back-to-back years of rapid growth.

Photograph of a busy lecture theater at DDD Brisbane with the presenter gesturing towards overhead slide projection.

Have you ever thought about having unit tests for your unit tests? 🤔 If so, decent chance your testing isn't catching the bugs you need and is just slowing you down ⏱️ @Ashley Mannix at #DDDAdelaide 2025 shows how to test complex software, challenging what a test is 🧪

At DDD Adelaide 2025 Ashley Mannix will be presenting Industrial Strength Testing for Complex Software

Liam McLennan shows us at #DDDAdelaide 2025 the power in using Metrics to gain observability at high volumes where logs simply don't work 📊. Join us to learn what metrics are, when they are useful, and how to actually collect and analyse them 📈🔍

At DDD Adelaide 2025 Liam McLennan will be presenting Metrics for High Performance Monitoring and Dashboarding

One thing I started noticing recently is that competent engineers give up their credibility due to AI. Twice already highly competent engineers I respect sent a PR that turned out to have very subtle issues. These issues would not be possible if a human understood it.

Building the Serilog sink for OpenTelemetry on OTLP, rather than the SDK, is turning out pretty well. It's super stable and in wide use at v4.2.0, while there's still no final SDK API for non-Microsoft loggers. Dependencies aren't inherently bad, but **schedule dependencies** almost always are.

Has anyone investigated writing an MCP server binding for System.CommandLine in #dotnet? Just poking around to keep up with what's going on in that space, seems like it could be an interesting quick bootstrapping option for existing codebases..?

Happy Firefox user, here, but I need to spend more dev time in Chromium-based browsers. Is the Chromium project itself the go-to privacy-conscious option? Any others I should take a look at? 🙏

Since data movement has such a huge impact on performance in distributed systems, we did a bit of work cleaning up Seq's query plans in 2025.1, and now explicitly show the send/receive operations that connect computations locally and over the network. Still not perfect, but getting closer! 😁

A screenshot of an `explain select distinct(Keys(@Properties)) from stream` query in the Seq UI. Indentation shows the "receive" operations outermost, and "send" operations indented below them. Receive operations are tagged with their merge strategy, e.g. "unordered", and the send operations with their partitioning strategy, e.g. "unconstrained".

Whoah, just spiked replacing Seq's internal cluster HTTP proxy with #aspnetcore's YARP, and once I remembered to register its service dependencies, it Just Works™️ first try, WebSockets and all. That's the mark of a nice piece of software, going to have to dig into this thing 😎

The option to build a complementary product or service isn't viable for everyone, but for high-use libraries, it's within reach a lot of the time. When you build one of these things, you end up a bit of a domain expert, and have a high chance of seeing the gaps and opportunities others won't...

Surprised to see a few posts like this lately. I've been strongly anti-license-switch for as long as this stuff has been going on, but perhaps not loud enough. There is no future in which this will happen. The #serilog project doesn't even accept donations! It's by the community, for the community.

iBRAR 🍉@ibrar-dev.bsky.social · 2y ago

What would break the dotnet csharp world right now, would be if #serilog followed suit and did the same thing. May companies would be forced to engineer away to alternatives or pay for license. As logging is not a straight forward thing to replace.

The apparent end of the CVE database caught me by surprise... Aside from fragmented means like GitHub tickets and mailing lists, how is everyone expecting to receive vulnerability notifications going forward? No viable replacement in the wings?