Nicholas Blumhardt

All set up for a fun day at #ndcoslo tomorrow! Drop in and say “hi” if you’re around 👋

Anyone heading to #ndcoslo next week and packing climbing shoes? Hoping to make a side-trip to Løkka klatresenter for some relaxed bouldering, not too far from the venue :-)

Metrics support is officially ready! Download the Seq 2026.1 MSI, or pull datalust/seq:latest to upgrade. Read the release announcement at: datalust.co/blog/seq-202...

PSA, from Serilog 4.4.0, you can listen to the "Serilog" meter to receive logging pipeline counters via System.Diagnostics.Metrics: github.com/serilog/seri... #Serilog

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... 😅

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! 😀

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.

Saw this live; it's sure to strike some chords with my tool-making friends.

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), ...

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.

2025 was a year of the industry fixating on development velocity. 2026? The year of fixating on software reliability.

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 🧪

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 📈🔍

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.

Hope you're all doing okay out there 👋

I can't believe it's so rare to get a terse, sensible, un-pushy issue raised ahead of a PR that feel the need to micro-blog when it happens, but here you go 😂 github.com/serilog/seri...

Work Sharing in Seq Clusters ✨ blog.datalust.co/work-sharing...

The first 1.0M is the hardest 😉 www.nuget.org/packages/Ser...

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? 🙏

We’re about to take C# to the next level! #dotnet #csharp

After me spending years maintaining a .NET state machine library, we implemented the core node state machine in plain old C# 😅 Couldn't be happier - states as classes, trigger handlers as switch statements returning new states, it's such nice, clear, direct code I don't think I'll look back....

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! 😁

Today's the day! Seq 2025.1 is ready at datalust.co/download, and on Docker Hub/ECR 😎 Find out what's new in the release announcement 👉 blog.datalust.co/announcing-s...

Hello, world! 👋

What I've been up to for the past year: blog.datalust.co/seq-clusteri..., and one of the toughest things to ship that I've ever worked on 😅

Today's "quick-and-dirty" hack turned out quite nicely; a Seq relay (replication/forwarder) plug-in that properly handles traces, OTLP envelope properties, etc.: github.com/nblumhardt/s...

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...

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?

Well, looks like we all ended up here, so I'd better stop lurking and say "hello" 👋

A neat trick in #rustlang from @jswrenn.bsky.social ! jack.wrenn.fyi/blog/undropp...