Tyrvexon

Tyrvexon

Long-form technical notes, written by operators for operators.

Operations

What Good Observability Actually Looks Like

May 17, 2026

Dashboards multiply like rabbits and answer questions nobody asked this month. Good observability starts from the opposite direction: the alert fired, a human is awake, and the tooling should answer 'what changed' within a minute.

In practice that means a small set of high-cardinality traces on the request path, deployment markers on every graph that matters, and logs structured enough that you can pivot from a customer ID to a timeline without five grep commands.

Continue reading →

Operations

Reading Latency Percentiles Without Fooling Yourself

April 26, 2026

Arithmetic averages hide the extreme tail latencies that percentiles make evident. Even if an endpoint posts an average duration of fifty milliseconds, one out of twenty calls might experience a grueling two-second delay; customers subjected to cold paths and overloaded database shards are the ones …

Networking

HTTP/3 and QUIC: What Changed for Operators

July 14, 2026

Implementing transport logic inside user space alongside encrypted protocol framing gives QUIC superior privacy while frustrating network operators relying on packet sniffers. Diagnostic data such as congestion state and window allocations are obscured behind cryptographic boundaries.…

Security

Managing Secrets Without Losing Sleep

August 21, 2026

Infrastructure teams generally experience two stages of secret maturity: storing variables in local encrypted repositories until an audit demands accountability. Crossing that divide entails rigorous credential turnover, verifiable access logs, and eliminating direct human access to runtime secrets.…

Engineering

The Operator's Guide to Load Testing

May 23, 2026

Load tests fail to predict production for a consistent reason: the traffic shape is wrong. Uniform random requests against one endpoint tell you about that endpoint. The production killer is the burst of clients retrying in sync after a thirty-second blip, or the cache-cold crawl at 5 a.m. when the …

More reading

About us

We are a small team of infrastructure engineers and technical writers. We publish what we learn running production systems: incident retrospectives, protocol deep-dives and tooling notes.

More about the project →