Türker Yıldırım

monitoring

  • Lazy loading arrived in the browser

    Deep dive9 min read

    One attribute replaces an IntersectionObserver and a library — and applying it to everything makes the Largest Contentful Paint worse rather than better.

  • Redis 6 and the shared password that was everywhere

    Deep dive10 min read

    One password, six services, and FLUSHALL available to all of them. 6.0 landed in April with users — and the keyspace pattern is where the isolation actually is.

  • A sampling profiler is the one for production

    Note1 min read

    An instrumenting profiler records every call, which changes the timings it is measuring — small fast functions look disproportionately expensive because the overhead is per call. Sampling belongs…

  • An SLI is good events over valid events, and both are choices

    Note2 min read

    The numerator and the denominator are both decisions, and getting the denominator wrong is what makes an objective meaningless. Excluding health checks and monitoring traffic is uncontroversial and…

  • wp cron event list, and the hook nobody knew about

    Note1 min read

    WordPress’s scheduler is a table of events run opportunistically on page loads, and a site with a ten-year plugin history has entries pointing at functions that no longer…

  • An HTTP client that is part of the framework

    Deep dive10 min read

    Four services, four hand-rolled clients, four retry policies. 7.0 wraps Guzzle, and the wrapper is the point rather than the transport.

  • A heartbeat table is the only honest lag measurement

    Note2 min read

    Seconds_Behind_Master reports how far behind the SQL thread is on the events it has received, which is not the same as how stale the data is. The long-ALTER…

  • A runbook is more useful for what it says not to do

    Note2 min read

    An alert that states a number crossed a threshold hands the receiver a research project, and at three in the morning three sentences beat any precision in the…

  • Contract tests that live in the repository

    Deep dive10 min read

    The collection lived in one person’s account, which is not version control. An endpoint changed and the client team found out from an error.

  • Moving a pipeline to a runner you do not own

    Deep dive10 min read

    The CI server was a pet and the pipeline was a shell script nobody could read. A runner that assumes nothing is the point, and the cache is…