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
機械支援の翻訳下書き (Japanese) for "Virtual Machine Runtime Profile": Virtual Machine Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for isolated guest compute. 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 Virtual Machine Runtime Profile when the VM migrated hosts, so the team could target optimization work before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Secret Build Gate": Secret Build Gate is a devops quality gate that blocks promotion when required checks fail for credential and sensitive configuration. It uses tests, lint, security scans, and policy rules so teams can prevent broken releases while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Secret Build Gate when a token rotated, so the team could prevent broken releases before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "CPU Workload Priority": CPU Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for general-purpose processor scheduling. 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 CPU Workload Priority when the service hit a compute ceiling, so the team could protect critical paths before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Scheduler Autoscaling Policy": Scheduler Autoscaling Policy is a compute control loop that changes capacity based on demand signals for placement of work onto resources. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Scheduler Autoscaling Policy when the cluster needed to place a job, so the team could match resources to load before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "GPU Resource Quota": GPU Resource Quota is a compute limit that sets how much compute a workload may consume for accelerated compute for parallel workloads. It uses policy, reservations, and usage tracking so teams can protect shared capacity while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used GPU Resource Quota when the training job requested more memory, so the team could protect shared capacity before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Observability Secret Rotation": Observability Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for logs, metrics, traces, and events. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Observability Secret Rotation when latency increased after deploy, so the team could reduce credential exposure before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Runbook Approval Step": 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.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) for "TLS Ingress Rule": TLS Ingress Rule is a networking boundary rule that controls how external traffic enters a service for encrypted transport setup. It uses hostnames, paths, protocols, and policy checks so teams can keep entry points predictable while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used TLS Ingress Rule when a certificate neared expiration, so the team could keep entry points predictable before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Observability Rollback Plan": Observability Rollback Plan is a devops recovery plan that defines how to return to a known good version for logs, metrics, traces, and events. 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 Observability Rollback Plan when latency increased after deploy, so the team could recover quickly from bad changes before the deployment window opened.”