The Anyshift Blog.

Deep dives into Site Reliability Engineering, AI in production, and scaling infrastructure gracefully. Written by the team building the future of SRE.

Browse by Category

Articles

One Graph, Two Jobs: How Our Infrastructure Graph Doubles as a Tuning Ground for AI SREs

One Graph, Two Jobs: How Our Infrastructure Graph Doubles as a Tuning Ground for AI SREs

We say modeling infrastructure as a graph is optimal for AI, and almost nobody gets why. It's not that models like graphs. It's that a graph is an interface you can simulate: every production incident Annie investigates can be rebuilt as a graph state, at scale, for nearly free. OpenAI's Sol 6.1 maxed out our old eval set, so we built a harder one from real production failures and tuned Annie's brain on half of it. Sol went from 64% to 92% on the held-out half. All made seamless thanks to our graph.

Ghazi Felhi
Ghazi Felhi
Oct 23, 2026 · 8 min read
AI Context for Prod, Optimized by AIs in Prod

AI Context for Prod, Optimized by AIs in Prod

Annie (our AI SRE agent) had institutional memory from ACE, the agentic context-engineering loop that curates cheatsheets from past runs. It worked, but clients kept catching her trusting stale entries or missing answers buried in her own bloated context. So we added five things on top: (1) a fixed set of memory items always presented to the agent, (2) per-query retrieval over the rest of the memory store, (3) an agent-optimized index of that store, (4) the ability for the agent to query the store mid-run, and (5) tried-and-true memory freshness mechanisms. Production context, now optimized by the AI using it. Here's the reasoning and what a few weeks in production say.

Ghazi Felhi
Ghazi Felhi
Jun 10, 2026 · 10 min read
My Workers Stopped Polling: a K8s + Temporal Whodunit

My Workers Stopped Polling: a K8s + Temporal Whodunit

Temporal workflows stuck in Running with zero pollers, and Temporal still reports a healthy task queue. The root cause lives one layer down: a CrashLoopBackOff in the Kubernetes worker pod, caused by a single bad environment variable. A walkthrough of debugging Temporal workers on Kubernetes the manual way (10 minutes), then with an infrastructure context layer that bridges the two systems (seconds).

Louis Fradin
Louis Fradin
Apr 8, 2026 · 6 min read
5 Key Reasons You're Struggling to Debug Your Infrastructure in Under an Hour

5 Key Reasons You're Struggling to Debug Your Infrastructure in Under an Hour

Most infrastructure debugging sessions blow past the one-hour mark for the same five structural reasons: scattered visibility across cloud accounts, missing historical state, terraform plan output that hides downstream impact, runbooks that lag the live infrastructure, and post-merger environments that no one has fully mapped. A walkthrough of each, with concrete examples and what reduces the time.

Roxane Fischer
Roxane Fischer
Jul 30, 2024 · 4 min read

Stay ahead of the pager.

Get a monthly digest of our best engineering articles, SRE case studies, and Anyshift product updates. No spam, just signal.