Skip to content

28 December 2025

Year-end notes: self-hosted platform resolutions and the backlog I am finally tackling

A late December reset: observability across the stack, agentic workflows, self-healing, and the certifications I am chasing in the new year.

Architectural cross-section of a workshop with four half-finished stations — observability mast, automaton chassis, self-repair mechanism, study desk — one figure with a checklist

Late December always brings clarity. I can see the gaps in my platform backlog, and I finally want to finish the work that turns the stack into a real platform, not just a collection of services.

Observability across the stack

Grafana, Loki, and Prometheus are next. I want full coverage across the stack so I can answer questions quickly and trace issues end to end. I am done with piecemeal logs and dashboards that only cover a single host.

Agentic workflows on real events

I am building automated AI workflows that trigger on events like journal updates and platform alerts. The goal is less noise, faster diagnosis, and a clean handoff when something needs a human.

Alerts and self-healing

Next year I want to go deeper on alert tuning and self-healing patterns. It is not enough to detect failures. The platform should recover when it can, and surface the right signal when it cannot.

Certifications to focus on

  • AZ-305
  • CKA

This is my new year reset. Smaller list, higher quality, real systems work. That is the goal.


What's the one platform backlog item you're finally going to tackle this year? Tell me in the comments.

Found this useful? Share on LinkedIn

Comments load automatically via GitHub (Utterances), which may set cookies. See the privacy policy.

Get new notes in your inbox

I publish a few times a month on platform engineering, Azure infrastructure, and building platforms that don't rely on heroics. No spam, unsubscribe anytime.

Your email is sent to my self-hosted endpoint and stored via Resend. See the privacy policy.