MTTA (mean time to acknowledge)
MTTA (mean time to acknowledge) is the average time between an alert going out and a person acknowledging that they are working on it.
MTTA measures the human part of incident response. A long MTTA usually means alerts go to a channel nobody watches at night, or that so many alerts fire that people stop looking.
Acknowledging also tells everyone else that someone has it, which stops duplicate work and stops further pages.
At a glance
MTTA = sum of (acknowledged at − alerted at) ÷ number of incidents
In OpenUptime
OpenUptime incidents can be acknowledged in the app, through the API or the MCP server. Until then, reminders repeat the alert and escalation sends it to further channels you choose.
Questions
What is a good MTTA?
For services with on-call, a few minutes. If acknowledging takes longer than your monthly error budget, the target cannot be met by people alone.
How do you lower MTTA?
Send alerts where someone is watching, cut noisy alerts so the real ones stand out, and escalate automatically when nobody responds.
Related terms
Monitor it with OpenUptime
Checks from one or several regions, alerts to the tools you use, and a status page for your customers. Free to start, open source under the MIT license.
MTTA（平均确认时间）
MTTA（平均确认时间）是从告警发出，到有人确认正在处理之间的平均时长。
MTTA 衡量的是事件响应中“人”的那部分。MTTA 长，通常意味着告警发到了夜里没人看的频道，或者告警太多，大家已经不再关注。
确认还能让其他人知道已经有人在处理，避免重复劳动，也会停止后续的告警通知。
速览
MTTA = Σ（确认时间 − 告警时间）÷ 事件数
在 OpenUptime 中
OpenUptime 的事件可以在应用中、通过 API 或 MCP 服务确认。在确认之前，提醒会重复发送告警，升级机制会把告警发送到你指定的其他渠道。
常见问题
MTTA 多少算好？
有值班机制的服务，几分钟以内。如果确认所需时间比每月的错误预算还长，单靠人工是达不到目标的。
怎样缩短 MTTA？
把告警发到有人盯着的地方，减少噪音告警让真正的告警更醒目，并在无人响应时自动升级。