이 페이지는 아직 한국어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우
언제든지 연락주시기 바랍니다.Join the Preview!
Deployment Gates are in Preview. If you’re interested in this feature, complete the form to request access.
Request AccessDeployment Gates have two main components:
- A Gate is defined for a service and environment (and optionally an identifier), and evaluates one or more rules to decide whether a deployment should proceed.
- A Rule is a type of evaluation performed as part of a gate, such as checking the status of a set of monitors or running APM Faulty Deployment Detection analysis on the deployed version.
Gate evaluations are asynchronous — the API returns immediately with an evaluation ID, and the result resolves to pass or fail over time as the rules run.
Deployment Gate evaluation modes
Deployment Gates support two evaluation modes: Just-In-Time (JIT) and preconfigured.
| JIT (default) | Preconfigured |
|---|
| Where rules live | Inline in your deployment configuration or CI step | Persisted in Datadog (UI, API, or Terraform) |
| Setup in Datadog | None | Create a gate and rules ahead of time |
| Best for | Rules-as-code, per-deployment flexibility, teams that own their own gate configuration | Shared rules across services, central management, non-CI editing |
| How to evaluate | Send rules in the evaluation request | Reference the gate by service, environment, and optionally identifier |
You can use different modes across different gates if needed.
If you’re unsure where to start, use JIT. It requires no setup in Datadog and lets you iterate on rules directly in your deployment configuration.
Further reading
