Find articles, news, tools and templates by subject or by the work you need to do.
62 results for “Reduce noisy alerts” · 37–48
Guide · Observability ·
A durable queue can preserve telemetry through an outage, then take longer to catch up. Arrival rate, export capacity and event age explain what recovery looks like.
Read guide: OpenTelemetry Collector queues and the wait for fresh dataGuide · AI in production ·
A missing response can leave a worker already created. Durable operation IDs and the destination’s idempotency contract let a replacement executor recover the original request.
Read guide: Recovering an automation write after a timeoutNews · AI in production ·
GPT-6 Sol and Luna combine lower token rates with cache-write and cache-read pricing. A repeated prompt can cost less even though its first cached write carries a premium.
Read news: GPT-6 Sol and Luna change the agent cost calculationGuide · AI in production ·
An independent checkout request can contradict an agent’s recovery claim. This evaluation separates the agent’s evidence from the grader’s observations and includes a runnable Python example.
Read guide: Testing an incident-response agent against the service it must recoverNews · Platform engineering ·
Host-memory throttling can keep an inference process alive while its requests slow down. Effective kubelet settings and request deadlines explain the tradeoff.
Read news: How Kubernetes Memory QoS affects inference under pressureGuide · AI in production ·
Herdr combines agent status, terminal panes and session recovery. Its server architecture explains what continues after a disconnect and what a restart restores.
Read guide: Herdr brings coding-agent sessions into one terminalCommentary · AI in production ·
Version checks, durable operation records and independent service checks give a production agent a recovery path when approval or execution becomes uncertain.
Read commentary: How production agents handle stale approvals and uncertain writesExplainer · Platform engineering ·
A stalled rollout shows how platform repair and application recovery depend on different teams, with a handoff that keeps both investigations moving.
Read explainer: Where SRE and platform engineering need an explicit handoffExplainer · AI in production ·
A short answer can conceal document retrieval, repeated context and retries. Task-level accounting connects those costs to the work the answer actually saves.
Read explainer: Where an AI task’s tokens, time and cost goExplainer · Platform engineering ·
Power and cooling affect the work a GPU pool can sustain. Device signals, request completions and queue growth help distinguish a physical limit from a workload change.
Read explainer: GPU capacity depends on power and coolingGuide · AI in production ·
A timed-out scaling request needs a durable record and destination-state checks. Reusable operational skills need to recover unfinished work as well as start it.
Read guide: Recovering an interrupted agent skillExplainer · AI in production ·
A rollback proposal crosses from recorded evidence into a changing system. The handoff carries source references, current preconditions and unfinished actions.
Read explainer: How an AIOps finding becomes an agent action