- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`Datadog is removing support for the is_read_only
attribute in the Dashboards API’s. For customers who manage Dashboards with the API directly, Datadog recommends that you transition to restricted_roles
or Restriction Policies.
Migrate off of is_read_only
to restricted_roles
or consider participating in Preview for Restriction Policies.
restricted_roles
The restricted_roles
parameter allows Dashboard owners to assign specific permissions to users with roles.
Migrating to restricted_roles
can be done independently. For more information, see the Dashboard API documentation.
Restriction Policies for Dashboards defines the access control rules for a resource. It maps a set of relations (editor and viewer) to a set of allowed principals (roles, teams, or users).
If you’re managing Dashboards through Terraform:
is_read_only
and restricted_role
from your Dashboard Terraform resources.terraform apply
.For an example of a Terraform resources, see the guide on How to use Terraform to restrict the editing of a dashboard.