SLAカバレッジ
The proportion of services or integrations governed by a formal Service Level Agreement, typically tracked for compliance and contractual obligations.
View termCategories
Site Reliability Engineering
Browse Site Reliability Engineering terms for IT and DevOps professionals.
Languages
SLO違反
An event where the service's actual reliability or performance falls short of the agreed Service Level Objective, triggering error budget consumption and potential incident response.
View termSLO違反
An event or period in which actual service performance falls below the established Service Level Objective, often triggering incident response and escalation.
View termSREキャリブレーション
A formal review and alignment process where SRE teams adjust monitoring, incident response, and reliability metrics to ensure consistent standards across services.
View termアップタイムコミットメント
A contractual or operational guarantee specifying the minimum service availability, often expressed as a percentage (e.g., 99.9%) over a defined period.
View termアップタイムトラッキング
Continuous monitoring and reporting of system or integration availability, often presented as dashboards and compliance metrics against SLAs and SLOs.
View termアラート疲労
A state where operators or engineers become desensitized due to excessive or repetitive alerts, risking delayed or missed responses to real incidents.
View termインシデントアーカイブ
A centralized, searchable repository storing records, timelines, and postmortem analyses for all past incidents, supporting compliance, audit, and learning.
View termインシデントラーニング
The process of analyzing incidents to identify root causes, systemic gaps, and actionable improvements for reliability, feeding back into SRE practices and runbooks.
View termインシデントロガー
A tool or service for real-time recording and tracking of incident events, communications, actions, and status updates during active outages.
View termインシデントローテーション
A scheduled process in site reliability and IT operations where on-call responsibilities for incident response are rotated among team members according to a predefined roster or policy.
View termインシデント・ウォールーム
A dedicated virtual or physical space where stakeholders, engineers, and incident commanders collaborate in real time to coordinate resolution of major incidents.
View termインシデント訓練
A simulated incident event conducted by IT operations or SRE teams to practice and evaluate readiness, coordination, and effectiveness of incident response procedures.
View termインパクトマトリックス
A visual or tabular tool mapping the severity and probability of incidents or risks, guiding prioritization in response and remediation planning.
View termウォールームデブリーフ
A retrospective meeting following an incident warroom to review actions taken, identify lessons learned, and assign follow-up items for process improvement.
View termエスカレーションパス
The documented sequence of escalation steps, contacts, and actions to be followed as an incident increases in severity or complexity.
View termエスカレーションマトリックス
A documented framework detailing incident severity levels, responsible roles, and the stepwise escalation path for critical incidents across support tiers.
View termエスカレーションラダー
A structured hierarchy that defines the sequence and roles for escalating unresolved incidents to higher support or management levels within IT operations or SRE organizations.
View termエスカレーションルート
A predefined path or sequence of roles to which incidents are escalated based on severity, ensuring prompt resolution and accountability.
View termオンコールシフト
A defined time period during which a designated team member is responsible for responding to alerts and incidents as the primary on-call engineer.
View termカオスシミュレーション
The controlled practice of deliberately introducing faults or failures into production-like environments to test system resilience, observability, and incident response procedures.
View termカオス注入
The deliberate introduction of faults, errors, or failures into a system to test and validate its resilience, observability, and incident response mechanisms.
View termキャパシティイベント
An incident or alert triggered by a system, application, or integration exceeding its predefined resource limits, such as CPU, memory, or connection thresholds.
View termサービスエスカレーション
A formal process in IT operations and incident management by which unresolved service issues or incidents are elevated to higher support tiers, subject-matter experts, or management levels according to escalation policy.
View termサービスエスカレーション
A formal incident management process by which unresolved issues are elevated to higher-tier support or management according to predefined escalation policy.
View termシフト表
A published schedule that allocates on-call duties, support shifts, and escalation responsibilities among operations and SRE team members.
View termトイル削減
The ongoing effort to minimize repetitive, manual, and low-value operational work in site reliability engineering by automating tasks and streamlining workflows.
View termバーンレート
The rate at which error budget or SLO allowance is consumed over time, indicating the pace of reliability degradation in SRE practice and the urgency of corrective actions.
View termブレームレス文化
An SRE and incident management principle that emphasizes learning and systemic improvement over assigning personal blame for incidents or failures.
View termプレイブック自動化
The automated execution of operational procedures and incident response workflows using predefined runbooks, scripts, or orchestration platforms to ensure standardized and repeatable responses across IT systems, integrations, or service monitoring environments.
View termヘルスバジェット
A quantitative limit representing allowable error or degradation in system health, used in SRE for monitoring, alerting, and balancing feature deployment risk.
View termページャーポリシー
A formal set of rules and expectations in site reliability engineering that governs the assignment, escalation, and response to pager or alert notifications for operational incidents.
View termページャー引き継ぎ
The formal process of transferring incident response and alert monitoring responsibilities to the next scheduled on-call engineer, typically at shift change.
View termポストモーテム分析
A structured review conducted after a major incident to analyze root causes, assess response effectiveness, and document corrective actions for future prevention.
View termランブックライブラリ
A centralized repository containing versioned, actionable runbooks for routine tasks, troubleshooting, and incident response in IT operations and SRE.
View termランブック参照
A specific pointer or hyperlink to a documented runbook procedure for rapid access during incident diagnosis or resolution.
View termレイテンシ予算
The maximum allowable time allocated for a transaction, operation, or request in an IT system before breaching service-level objectives or user expectations.
View termレスポンスプレイブック
A detailed set of documented procedures and best practices for handling specific incident types or operational anomalies in IT and integration environments.
View termレスポンスローテーション
A scheduled system for rotating on-call or incident response responsibilities among team members to ensure fair distribution of operational workload.
View term信頼性スコア
A quantitative indicator representing the operational reliability of a service, integration, or system, often based on uptime, incident frequency, and SLO compliance.
View term信頼性監査
A formal assessment of systems, integrations, and processes to verify compliance with reliability standards, SLOs, and operational policies.
View term信頼性目標
A quantifiable goal set for the availability, performance, or correctness of a system or integration, typically expressed as a percentage (e.g., 99.9% uptime) to guide engineering and operational decisions.
View term可用性目標
A specific level of service uptime expressed as a percentage (e.g., 99.99%), used as an operational or contractual benchmark for system reliability.
View term安定性目標
A quantifiable goal specifying the desired level of system stability, typically measured by the frequency and impact of failures, for SRE and integration operations.
View term疲労管理
The process of reducing operational overload and alert fatigue for IT and SRE teams by optimizing on-call scheduling, alert thresholds, and workload distribution.
View term緩和ワークフロー
A defined sequence of steps and automated tasks for responding to, containing, and resolving incidents, usually documented in runbooks or incident playbooks.
View term緩和計画
A documented set of actions designed to reduce the impact or likelihood of future incidents, typically produced during incident response or postmortem analysis.
View term障害レビュー
A collaborative meeting or process to analyze a system or service failure, uncover contributing factors, and recommend improvements for reliability.
View term障害訓練
A planned exercise simulating system or integration failure scenarios to validate incident response procedures, team readiness, and recovery playbooks.
View term