Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
2,337 definitions
Incident Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for response to service degradation. It uses trace IDs, span metadata, and release identifiers so teams can debug production changes faster while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Incident Trace Link when on-call received a high-severity page, so the team could debug production changes faster before the deployment window opened.”
BGP Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for interdomain routing. It uses health signals, priorities, and cooldown windows so teams can recover from outages predictably while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used BGP Failover Policy when a route advertisement changed, so the team could recover from outages predictably before traffic crossed a service boundary.”
Incident Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for response to service degradation. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Incident Incident Timeline when on-call received a high-severity page, so the team could learn from outages without guesswork before the deployment window opened.”
Serverless Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for event-driven function execution. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Serverless Cache Invalidation when the function received a traffic burst, so the team could serve current results before the workload scaled up.”
Runbook Runbook Check is a devops operational test that confirms that documented procedures still work for documented operational procedure. It uses dry runs, screenshots, and command validation so teams can keep response playbooks current while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Runbook Runbook Check when a responder needed the recovery steps, so the team could keep response playbooks current before the deployment window opened.”
Serverless Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for event-driven function execution. It uses priority classes, preemption rules, and fairness limits so teams can protect critical paths while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Serverless Workload Priority when the function received a traffic burst, so the team could protect critical paths before the workload scaled up.”
Secret Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for credential and sensitive configuration. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Secret Incident Timeline when a token rotated, so the team could learn from outages without guesswork before the deployment window opened.”
Cache Capacity Forecast is a compute planning model that estimates future resource needs for fast temporary data layer. It uses traffic history, growth assumptions, and utilization trends so teams can avoid surprise shortages while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Cache Capacity Forecast when the cache missed during peak traffic, so the team could avoid surprise shortages before the workload scaled up.”
Runbook Approval Step is a devops workflow control that requires review before a sensitive change proceeds for documented operational procedure. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Runbook Approval Step when a responder needed the recovery steps, so the team could keep high-risk automation accountable before the deployment window opened.”
Runbook Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for documented operational procedure. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Runbook Incident Timeline when a responder needed the recovery steps, so the team could learn from outages without guesswork before the deployment window opened.”