You can control access to the SLOs in your environment by setting write and/or read permissions to users or user groups at the environment or management-zone level. For details on how to set permissions, see Role-based permissions.
Permission checks are based only on the global entity selector.
At the environment level, a user with View environment permission can view any SLO. To manage group permissions, you can create policies.
Example policy: ALLOW settings:objects:read, settings:schemas:read WHERE settings:schemaId = "builtin:monitoring.slo";
On a management-zone level, a user with View environment permission can read all global SLOs and all SLOs belonging to the respective management zone.
Currently, a policy can't be assigned on the management-zone level.
At the environment level, a user with Change monitoring settings permissions can create and update any SLO, including global SLOs without management zones specified. To manage group permissions, you can create policies.
Example policy: ALLOW settings:objects:read, settings:schemas:read, settings:objects:write WHERE settings:schemaId = "builtin:monitoring.slo";
.
On a management-zone level, a user with Change monitoring settings permissions can create and update any SLO for the respective management zone, but can't create or update global SLOs.
The SLO evaluation takes into account both your selected management zone and the management zone from the entity selector.
At the environment level
On a management-zone level
Starting with Dynatrace version 1.233+, you can also set a custom management zone for a specific tile, similar to the timeframe. In this case, the global management zone filter isn't relevant for the respective tile.