Recovering an agent task after OpenShell containment
OpenShell can stop an agent after Kubernetes has accepted its scaling request. Recovery then depends on the Deployment state, available replicas and customer-facing result.
Reliability engineering, from service objectives to operational judgment.
OpenShell can stop an agent after Kubernetes has accepted its scaling request. Recovery then depends on the Deployment state, available replicas and customer-facing result.
Zero errors, no traffic and absent series produce different PromQL results. Synthetic tests show how ratios, fallback zeros and absence checks behave for a checkout service.
Host-memory throttling can keep an inference process alive while its requests slow down. Effective kubelet settings and request deadlines explain the tradeoff.
Kubernetes attributes connect agent calls to pods, workloads and paging routes. A processor migration can break those connections while telemetry still flows.
How Herdr keeps coding sessions available while you detach, and what changes when its server restarts.
The permissions, state and recovery paths an agent needs when its tool calls can change a running service.
Use instrumentation and context propagation to connect the evidence in an investigation.
Clarify ownership across shared platforms, service reliability, and incident response.
Separate a completed task from evidence that the underlying risk was reduced.
Account for context limits, retries, latency, and the work behind a useful result.
Evidence can split a 5 Whys investigation into several contributing causes. A concurrency example shows how to turn those explanations into useful tests.
Conflicting restart instructions show where a source-backed notebook helps: finding the relevant passages, dates and exceptions for the runbook owner.