2663 terms covering AIOps, DevOps, MLOps, FinOps, observability and cloud-native operations.
Written by AI. Published under human oversight.
Adaptive Capacity Management
A dynamic approach to resource allocation that adjusts infrastructure based on workload variability. It improves system stability during traffic spikes without overprovisioning.
Adaptive Capacity Scaling
A strategy that dynamically adjusts resource allocation based on real-time traffic and load conditions to maintain optimal performance and reliability of services, especially during peak demand periods.
Adaptive Traffic Routing
Adaptive traffic routing dynamically redirects requests based on system health, latency, or capacity conditions. SRE teams use it to improve reliability, reduce congestion, and support graceful degradation.
Audit Logging
Audit logging is the practice of recording system events and user actions for security, compliance, and operational analysis. It provides a comprehensive history that can be analyzed for troubleshooting and improving system reliability.
Automated Rollback
A practice used in deployment processes where a system automatically reverts to a previous stable version if the new deployment fails. This ensures higher uptime and reliability.
Auto-Scaling
Auto-scaling is a feature that automatically adjusts the number of active servers or resources based on current demand. It enhances service reliability and performance by ensuring adequate resources during peak loads.
Availability Target
An availability target defines the expected percentage of time a service should remain operational for users. It guides infrastructure design, redundancy planning, and reliability investments.
Blameless Postmortem
A blameless postmortem is a retrospective analysis conducted after an incident, focused on understanding what happened and how to improve systems, rather than assigning blame. It fosters a culture of learning and continuous improvement.
Blameless Retrospective
A structured review process following incidents or failures where individuals are not blamed. The focus is on identifying systemic weaknesses and implementing preventive improvements.
Canary Analysis
An evaluation technique used during progressive deployments to compare performance metrics between new and stable versions. It determines whether a release is safe to expand or must be rolled back.
Capacity Management
Capacity management involves monitoring and managing the resources needed for service delivery to ensure that the system can handle future demand without performance degradation. It includes planning for scaling and resource allocation.
Change Management
Change management in SRE focuses on controlling and managing changes to systems and software to minimize risk and impact on reliability. It involves thorough testing, validation, and monitoring of changes.
Circuit Breaker Pattern
A resilience design pattern that stops requests to a failing service after a defined threshold is reached. It allows systems to recover gracefully and prevents widespread outages.
Configuration Drift Management
The practice of detecting and correcting unintended configuration changes across environments. It helps maintain consistency and prevent reliability regressions.
Cost Management in SRE
The practice of monitoring and controlling the financial costs associated with hosting and maintaining services, ensuring that budget constraints do not compromise reliability.
Dark Launch Deployment
A dark launch deployment releases features into production without exposing them to all users. SRE teams monitor system behavior and performance before enabling broader access.
Deployment Pipeline
A set of automated processes that code changes go through from commit to deployment in production, enabling continuous integration and deployment practices crucial for maintaining service reliability and speed.
Disaster Recovery Objective (DRO)
A defined target for restoring systems after catastrophic failure, including acceptable downtime and data loss thresholds. It guides backup and replication strategies.
Error Budget Alerting
An alerting strategy based on error budget consumption rather than raw metric thresholds. It prioritizes alerts aligned with user impact and reliability goals.
Error Budget Burn Rate
The rate at which a service consumes its allocated error budget over time. Monitoring burn rate helps teams proactively address reliability risks before targets are breached.
Error Budget Freeze
A temporary halt on feature releases when a service exhausts its allocated error budget. This mechanism enforces reliability accountability before further changes are introduced.
Error Budget Governance
Error budget governance defines organizational processes for monitoring and enforcing reliability thresholds. It aligns engineering, operations, and product teams around acceptable operational risk.
Error Budget Governance Board
A cross-functional group that reviews error budget consumption and determines release or remediation actions. It enforces accountability for maintaining reliability standards.
Error Budget Policy
A formal agreement that defines actions when an error budget is consumed or exceeded. It typically governs release velocity, feature rollouts, and reliability improvement initiatives.
Error Budgets
A concept in SRE that defines the maximum allowable error rate for a service within a specific time frame. It helps balance the speed of feature development with the reliability of the service.
Error Tracking
The process of monitoring and logging errors to gain insights into system reliability issues. Effective error tracking helps identify trends, understand root causes, and direct improvements to enhance service stability.
Failure Domain Isolation
Failure domain isolation limits the impact of outages by separating systems, workloads, or infrastructure into independent operational boundaries. This approach reduces cascading failures and improves resilience.
Fault Injection Testing
A testing technique that simulates infrastructure or application failures to evaluate system robustness. It may involve network latency, service crashes, or resource exhaustion. This method verifies that failover and recovery processes function correctly.
Fault Tolerance
The capability of a system to continue operating properly in the event of the failure of some of its components. Fault tolerance involves implementing redundancies and failover mechanisms to ensure uninterrupted service.
Four Golden Signals Extension
An expansion of the traditional golden signals to include additional indicators such as availability zones, dependency health, or cost efficiency. It adapts foundational monitoring concepts to complex distributed systems.
Golden Signals Monitoring
A monitoring approach centered on four key metrics: latency, traffic, errors, and saturation. These signals provide a high-level view of service health and user experience. They are foundational for detecting and diagnosing production issues.
Graceful Degradation
A design principle where systems maintain partial functionality instead of failing completely during disruptions. It improves user experience during outages or overload conditions.
High Availability Architecture
A system design approach that minimizes downtime through redundancy and failover mechanisms. It ensures continuous service operation despite component failures.
Incident Command System
A standardized hierarchical structure used during incidents to streamline communication and decision-making. It helps establish roles and responsibilities, ensuring a coordinated response to service outages.
Incident Command System (ICS)
A structured framework for managing incidents with clearly defined roles and communication paths. It improves coordination and reduces confusion during high-severity outages.
Incident Management Life Cycle
The complete process of managing incidents from detection through resolution, including identification, logging, categorization, prioritization, diagnosis, resolution, and closure. Each stage contributes to improved service reliability.
Incident Management Tool
An incident management tool is a software application that assists teams in tracking, managing, and resolving incidents efficiently. It streamlines the incident response process, ensuring timely communication and resolution.
Incident Review Process
A structured approach to investigating and analyzing incidents after they occur to derive lessons learned and prevent future occurrences. This includes documenting findings and creating actionable follow-ups.
Latency Management
A set of techniques and strategies adopted to minimize the response time of services, ensuring that performance meets user expectations and service level agreements.
Latency SLOs
Latency SLOs are specific service level objectives focused on measuring response times for user requests. They help ensure that services perform within acceptable time frames, directly impacting user experience.
Load Shedding
A defensive technique where a system intentionally drops or rejects excess traffic to maintain stability under high load. It prevents cascading failures and preserves core functionality.
Load Testing
Load testing evaluates how a system performs under high levels of traffic and demand. It helps identify performance bottlenecks and ensures that the system can handle expected workloads without issues.
Mean Time Between Failures (MTBF)
A reliability metric representing the average time between system failures during normal operation. It helps assess long-term system stability and reliability trends.
Monitoring and Alerting
The processes of continuously tracking system performance and health metrics, generating alerts for predefined thresholds to facilitate timely incident response and proactive management of service reliability.
Multi-Region Failover
A resilience strategy that automatically redirects traffic to a secondary geographic region during outages. It enhances availability and disaster recovery posture.
Multi-Window Alerting
Multi-window alerting combines short-term and long-term metric evaluation to improve alert accuracy. It helps detect urgent failures while minimizing unnecessary notifications from transient anomalies.
Network Latency Optimization
Techniques and methodologies aimed at reducing delays in data transmission across networks, critical for improving application performance, user experience, and overall system reliability in distributed environments.
Observability-Driven Development (ODD)
An approach that integrates observability principles into the software development lifecycle, ensuring that systems are designed with monitoring and traceability in mind, resulting in improved reliability and maintainability.
On-call Rotation
A systematic schedule in which members of the SRE team take turns being on-call to respond to incidents or outages, ensuring continuous coverage while managing workload and burnout among team members.
On-Call Rotation Model
A structured schedule assigning engineers responsibility for responding to production alerts. It balances workload distribution and knowledge sharing. Effective models reduce burnout and improve response times.
Operational Excellence Framework
A structured set of best practices aimed at optimizing reliability, efficiency, and scalability. It integrates automation, monitoring, and cultural principles into daily operations.
Operational Load Shedding
A defensive mechanism that intentionally drops or degrades non-critical traffic when systems are under extreme load. It protects core functionality from cascading failures.
Operational Load Testing
Testing systems under simulated production traffic to evaluate performance, scalability, and failure behavior. It validates reliability assumptions before real-world exposure.
Operational Readiness Checklist
A standardized list of criteria ensuring systems are prepared for sustained production operation. It includes monitoring, alerting, documentation, and rollback validation. This checklist reduces overlooked reliability gaps.
Operational Readiness Gate
A predefined checkpoint that must be satisfied before a system progresses to the next lifecycle stage. It enforces reliability and operational compliance standards.
Operational Visibility
The extent to which an organization can observe and understand the state of its technical systems in real-time. High operational visibility allows SRE teams to detect issues proactively and respond to anomalies swiftly.
Performance Baseline
A fixed reference point for measuring the normal operation of a system or service. Understanding baselines is crucial for identifying anomalies and performance degradation.
Performance Tuning
The process of adapting systems and services to achieve optimal performance, which can involve adjusting configurations, fine-tuning databases, or optimizing code.
Postmortem Analysis
The retrospective evaluation carried out after an incident to understand what went wrong, assess the impact, and identify preventive measures. Proper postmortem analysis fosters continuous improvement and prevents future incidents.
Post-Mortem Analysis
A systematic process of reviewing and analyzing incidents after they occur to understand the root causes, identify improvements, and prevent recurrence. It emphasizes transparency and learning.
Postmortem Culture
An organizational practice of conducting blameless incident reviews to identify systemic causes and improvement opportunities. It promotes transparency, accountability, and continuous learning within SRE teams.
Production Readiness Review
A production readiness review evaluates whether a service is prepared for deployment into a live environment. Reviews typically assess monitoring, scalability, rollback procedures, security, and operational ownership.
Production Readiness Review (PRR)
A structured assessment conducted before deploying a new service or feature into production. It evaluates reliability, scalability, monitoring, and operational support readiness.
Prometheus Monitoring
An open-source monitoring system that collects metrics from configured targets at specified intervals, enabling performance tracking and alerting. It's widely used for its powerful querying language and integration capabilities.
Recovery Point Objective (RPO)
The maximum tolerable amount of data loss measured in time during a disruption. RPO informs backup frequency and replication strategies.
Recovery Time Objective (RTO)
The maximum acceptable duration a service can be unavailable after an incident. RTO guides disaster recovery planning and resilience architecture decisions.
Release Engineering
Release engineering manages the build, testing, deployment, and delivery processes for software systems. In SRE environments, it emphasizes automation, consistency, and safe production rollouts.
Reliability Anti-Pattern
A reliability anti-pattern is a design or operational practice that repeatedly introduces instability or operational risk. Identifying anti-patterns helps teams improve architecture and reduce recurring incidents.
Reliability as Code
An approach that codifies reliability policies, monitoring configurations, and resilience patterns into version-controlled artifacts. It enables automated enforcement and consistent reliability standards across environments.
Reliability Benchmarking
Reliability benchmarking compares service stability, recovery performance, and operational efficiency against internal standards or industry baselines. The results guide improvement planning and maturity assessment.
Reliability Budgeting
A planning method that allocates reliability targets across system components and teams. It ensures shared accountability for meeting overall service reliability goals.
Reliability-Driven Development (RDD)
A development methodology that prioritizes reliability requirements alongside functional features. It integrates failure testing and monitoring considerations into the coding phase.
Reliability Engineering
An engineering discipline focused on ensuring systems consistently meet performance and availability expectations. In SRE, it combines software engineering practices with operational expertise to build resilient services.
Reliability Engineering Backlog
A prioritized list of tasks aimed at improving system resilience, scalability, and observability. It includes automation work, technical debt reduction, and incident follow-ups. Managing this backlog ensures continuous reliability enhancement.
Reliability Engineering Lifecycle
A lifecycle model that integrates reliability practices into design, development, deployment, and operations. It ensures reliability considerations are embedded early and continuously validated in production.
Reliability Engineering Metrics
Quantifiable measurements used to assess the reliability of systems, including Mean Time To Recovery (MTTR), Mean Time Between Failures (MTBF), and Service Level Indicators (SLIs). These metrics help teams gauge performance and make informed decisions about reliability improvements.
Reliability Engineering Review
A structured evaluation of system architecture, dependencies, and operational readiness. It assesses risk exposure, redundancy, and failure handling capabilities. These reviews are often conducted before major launches or architectural changes.
Reliability Guardrails
Predefined policies and automated controls that prevent deployments or changes from violating reliability standards. They act as protective boundaries within CI/CD pipelines.
Reliability Regression Testing
Reliability regression testing validates that infrastructure or application changes do not degrade stability or performance. It is commonly integrated into CI/CD pipelines for continuous validation.
Reliability Risk Assessment
A systematic evaluation of potential failure modes and their impact on service continuity. It informs mitigation planning and prioritization of engineering work.
Reliability Risk Register
A documented inventory of known reliability threats, technical debt, and systemic weaknesses. It prioritizes risks based on likelihood and potential impact. This register guides proactive mitigation efforts in SRE programs.
Reliability Runway
The projected duration a system can maintain acceptable reliability under current operational conditions. It helps teams anticipate when reliability investments are needed to prevent degradation.
Reliability Scorecard
A structured reporting tool that aggregates reliability metrics, incidents, and improvement actions. It provides leadership with a consolidated view of service health and risk.
Reliability Target Setting
The process of defining measurable reliability goals based on user expectations and business priorities. It ensures targets are realistic, data-driven, and aligned with system capabilities. Effective target setting balances innovation with operational stability.
Reliability Testing in Production
The practice of validating resilience mechanisms within live environments using controlled experiments. It ensures reliability safeguards function under real conditions.
Resilience Testing
An evaluation of a system's ability to continue operating correctly in the face of adverse conditions or failures. This process involves simulating outages and understanding system recovery behaviors for proactive improvements.
Resilience Testing Framework
A structured toolkit or methodology used to validate a system’s ability to withstand and recover from failures. It integrates fault injection, load testing, and recovery validation.
Resource Contention
Resource contention occurs when multiple processes or services compete for the same resources, leading to performance degradation. Understanding and managing contention is vital for maintaining system reliability and efficiency.
Rollback Strategy
A rollback strategy is a predetermined plan for reverting a system to a previous stable state in case a deployment fails. It is critical for minimizing downtime and maintaining service reliability during updates.
Runbook
A compilation of procedures and operations documented for a specific service or system that guides SRE teams during incidents or routine operations.
Serious Game
A learning exercise designed to simulate incident response scenarios, enhancing team skills and decision-making under pressure. Serious games provide practical experience in a risk-free environment while promoting teamwork.
Service Capacity Buffer
Reserved system capacity maintained above expected load to handle traffic spikes or failures. It reduces the risk of saturation and cascading outages.
Service Dependency Graph
A service dependency graph visualizes the relationships and dependencies between various services in a system. It helps teams understand how failures in one service can affect others, enhancing incident response and troubleshooting.
Service Dependency Injection
A design principle where services are provided or 'injected' into a system to decouple dependencies, improving the maintainability and reliability of applications within a microservices architecture.
Service Level Indicator (SLI)
SLIs are quantifiable metrics that measure the performance and reliability of a service from the end user's perspective. They provide the foundation for defining service level objectives and are crucial for monitoring service health.
Service Maturity Model
A framework used to evaluate the reliability and operational sophistication of services. It guides teams in progressively improving automation, monitoring, and resilience practices.
Service-oriented Architecture (SOA)
An architectural pattern that structures an application as a collection of loosely coupled services, enabling increased flexibility and scalability in development and operations.
Service Ownership Model
A governance framework where specific teams are accountable for the reliability and performance of defined services. Clear ownership accelerates incident response and continuous improvement.
Service Reliability Automation Index
A maturity indicator that measures the percentage of operational tasks automated within a service lifecycle. It evaluates progress in reducing manual intervention. Higher index values correlate with scalable SRE practices.
Service Reliability Hierarchy
A layered model that categorizes reliability requirements from infrastructure to application and user experience levels. It helps prioritize improvements based on impact scope.