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 "Incident Trace Link": 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.”
機械支援の翻訳下書き (Japanese) for "DNS Path Trace": DNS Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for name resolution and delegation. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used DNS Path Trace when a resolver returned stale data, so the team could debug connectivity issues before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) for "Runbook Artifact Signature": Runbook Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for documented operational procedure. 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 Runbook Artifact Signature when a responder needed the recovery steps, so the team could trust deployed packages before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Incident Infra Plan": Incident Infra Plan is a devops change preview that shows expected infrastructure changes before apply for response to service degradation. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Incident Infra Plan when on-call received a high-severity page, so the team could review platform changes safely before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Incident Artifact Signature": Incident Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for response to service degradation. 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 Incident Artifact Signature when on-call received a high-severity page, so the team could trust deployed packages before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Container Backpressure Control": Container Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for packaged application runtime. It uses queues, retry budgets, and admission control so teams can avoid overload cascades while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Container Backpressure Control when the image started on a new node, so the team could avoid overload cascades before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "DNS Anycast Endpoint": DNS Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for name resolution and delegation. It uses regional announcements, health checks, and traffic steering so teams can serve users from nearby healthy sites while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used DNS Anycast Endpoint when a resolver returned stale data, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "GPU Autoscaling Policy": GPU Autoscaling Policy is a compute control loop that changes capacity based on demand signals for accelerated compute for parallel workloads. 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 GPU Autoscaling Policy when the training job requested more memory, so the team could match resources to load before the workload scaled up.”