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
机器辅助翻译草稿 (Chinese) for "Runbook Incident Timeline": 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.”
机器辅助翻译草稿 (Chinese) for "Cache Cold Start Budget": Cache Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for fast temporary data layer. It uses prewarming, smaller packages, and runtime tuning so teams can keep first requests responsive while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The platform engineering team used Cache Cold Start Budget when the cache missed during peak traffic, so the team could keep first requests responsive before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "TLS Egress Policy": TLS Egress Policy is a networking outbound control that decides where workloads may send traffic for encrypted transport setup. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The network engineering team used TLS Egress Policy when a certificate neared expiration, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
机器辅助翻译草稿 (Chinese) for "Release Artifact Signature": Release Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for versioned delivery of code or content. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The DevOps team used Release Artifact Signature when the release notes were generated, so the team could trust deployed packages before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Infrastructure Release Manifest": Infrastructure Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for cloud resources and platform wiring. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The DevOps team used Infrastructure Release Manifest when a new region was added, so the team could make releases auditable before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Serverless Image Hardening": Serverless Image Hardening is a compute security practice that reduces risk inside packaged runtime images for event-driven function execution. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The platform engineering team used Serverless Image Hardening when the function received a traffic burst, so the team could ship safer workloads before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Observability Config Drift Check": Observability Config Drift Check is a devops consistency check that finds differences between intended and live configuration for logs, metrics, traces, and events. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The DevOps team used Observability Config Drift Check when latency increased after deploy, so the team could avoid surprise environment behavior before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Runbook Runbook Check": 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.”
机器辅助翻译草稿 (Chinese) for "Runbook Rollback Plan": Runbook Rollback Plan is a devops recovery plan that defines how to return to a known good version for documented operational procedure. It uses version pins, database notes, and operator steps so teams can recover quickly from bad changes while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The DevOps team used Runbook Rollback Plan when a responder needed the recovery steps, so the team could recover quickly from bad changes before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Scheduler Runtime Profile": Scheduler Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for placement of work onto resources. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The platform engineering team used Scheduler Runtime Profile when the cluster needed to place a job, so the team could target optimization work before the workload scaled up.”