Hello everyone! This is a brief note to let you know that our recent silence hasn't been for a lack of activity, but quite the opposite: we're so enthusiastic about native OpenTelemetry metrics support in Seq that we're heads-down working to get it into your hands.
Metrics will be the centerpiece of the Seq 2026.1 release, planned for late Q1/early Q2, 2026.
We're aiming at three big goals:
- Make it easy and efficient to ingest and view metrics from a wide array of sources,
- Dramatically speed up analytic use cases such as dashboarding and threshold-based alerting, and
- Substantially reduce the storage requirements associated with collecting data from regularly-repeating events.
Early on in the process, we decided to embrace metrics with the same degree of commitment that we apply to logs and traces. We're applying this principle to everything in Seq 2026.1 from the UI through to bytes-on-disk storage, and while it's a huge task, we're confident the results will be worth it.
On main today, Seq can receive metrics through its native OTLP endpoint and plug-in app inputs, ingest them into compressed, column-oriented storage, execute queries over them using the same query language as for logs and traces, and render metrics alongside log- or trace-driven charts on Seq dashboards.
What's missing, then? Two major pieces are still unfinished. First, we're leaning on the row-oriented query execution engine for end-to-end query processing while the column-oriented execution engine is built. This is a large and complex component, but it's one we've already made huge strides towards completing. Second, we have a new metric visualization experience in the works, and likewise there's a lot to do there.
We're breaking (on) through to the other side, though! From today through to the 2026.1 release, we'll be posting a monthly engineering update and progress report. Watch this space! 😁