Name: Production Incident Commander
Brand: Tetrees AI
Availability: InStock

Hướng dẫn Tetrees Agent

Agent này làm gì

During an outage, responders jump between alerts, logs, metrics, traces, topology, and recent changes; weak timelines and untested hunches create noisy investigations and risky remediation.

Dành cho

On-call engineers and incident commanders
SRE and platform teams
Teams building runbooks and synthetic incidents
Engineering managers reviewing postmortems

Dữ liệu đầu vào

Alert, symptom, severity, and incident time window
Metrics, logs, traces, topology, deploys, and events
Service objectives, ownership, and runbooks
Approved-action boundaries and rollback options

Kết quả nhận được

Incident timeline and blast-radius map
Ranked hypothesis table with evidence
Reversible mitigation and rollback plan
Root-cause and contributing-factor report
Postmortem action and monitoring checklist

Quy trình hoạt động

1Establish incident scope, customer impact, severity, time window, and immediate safety constraints.
2Build a normalized timeline from independent observability and change sources.
3Rank hypotheses by explanatory coverage, temporal fit, topology, and contradicting evidence.
4Separate symptom relief from root-cause repair and choose the safest reversible mitigation.
5Require owner confirmation before any write, production, or customer-impacting action.
6Produce an evidence-linked incident report, residual-risk watch plan, and durable learning candidates.

Ví dụ sử dụng

Bắt đầu với một yêu cầu bên dưới rồi thay chi tiết bằng dữ liệu của bạn.

Diagnose a database connection storm

API latency and error rate rose after a deployment while database CPU and connection metrics disagree.

Yêu cầu mẫu

Use these alert, CloudWatch metrics, deploy events, and application logs to rank causes. Distinguish DB saturation, connection leakage, and retry amplification, then propose the safest mitigation.

Kết quả dự kiến: A normalized timeline, correlated evidence, ranked hypotheses, disconfirming checks, a reversible mitigation, rollback criteria, and no unapproved production action.

Review whether a noisy alert is causal

Several infrastructure alerts fire together and the team risks treating the loudest one as the root cause.

Yêu cầu mẫu

Analyze this incident bundle. Identify which alerts are causal, consequential, coincidental, or unsupported, and give the next three evidence-gathering steps.

Kết quả dự kiến: A topology- and time-aware correlation report, evidence gaps, confidence, safe next checks, and a bounded incident status update.

Một lần chạy thành công cần

✓ Timeline and topology support the root-cause claim
✓ Counterevidence is recorded
✓ Mitigation is reversible and has rollback criteria
✓ No production write occurs without explicit approval
✓ Postmortem actions are specific and testable

Phạm vi và giới hạn

• Hosted mode is read-only and cannot mutate infrastructure
• Incomplete telemetry can prevent a confident diagnosis
• Correlation is not proof of causation
• Human incident command remains responsible for production decisions

Năng lực

incident triageevidence correlationroot cause analysismitigation planningpostmortem

Chọn OpenAI, Claude hoặc Z.AI trong Agent Studio rồi chạy bằng Điểm Tetrees hoặc BYOK.

Công cụ thực thi

Chạy trên máy chủ chỉ dùng bộ công cụ đã ký này. MCP cục bộ có thể thêm công cụ do bạn tự cấu hình và phê duyệt.

recall pack memorypropose pack growthlist run attachmentsread run attachmentweb search

Agent AVCP

Báo cáo Agent AVCP

Đã kiểm thử v1.0.0

TAIP đã kiểm tra được liên kết với báo cáo và chữ ký nền tảng. Điểm số là bằng chứng kiểm thử, không bảo đảm mọi phản hồi tương lai.

Điểm tổng

9.5

trên 10

Bảo mật9.5

Chức năng10.0

Mức hoàn thiện10.0

Cổng bắt buộc

provenance✓ Đạt

costCeilings✓ Đạt

growthRollback✓ Đạt

skillExecution✓ Đạt

Đăng nhập để chạy hoặc nhận gói.

Đánh giá

Chưa có đánh giá.

Production Incident Commander