I’m currently facing a challenge in configuring IAM policies to restrict problem visibility in the New Problems App.
We have a user group, ABC, which is assigned the Standard user policy, and is further restricted by a policy boundary that includes:
A specific Management Zone (MZ) rule
A separate Security Context rule
When a user from this ABC group logs in:
They are able to access the New Problems App, but
No problems are visible in the app (nor on any dashboard widgets based on the new Problems view)
Interestingly, as soon as we remove the policy boundary, they are able to view all problems — but this is not acceptable, as we don’t want users to view problems beyond their relevant MZ.
With the traditional Problems App, the same boundary configuration works as expected — problems are scoped correctly to their MZ.
Our challenge is:
The New Problems App does not honor the MZ/Security Context restriction in the same way
Our new dashboards rely on this new Problems view, meaning these restricted users now see nothing
Request: How can we configure IAM policies and boundaries so that:
Users can view problems in the New Problems App and dashboards
But only those problems within their assigned Management Zone or Security Context
Is there a supported way to achieve this today? Or a roadmap plan to support MZ-based scoping in the New Problems App similar to the legacy behavior?
I suggest opening a support ticket, as the current behavior doesn’t align with what’s described in the documentation: IAM policy reference — Dynatrace Docs. Some conditions and operators don’t seem to function as expected.
As a temporary workaround—which may not cover all scenarios—you could try creating a separate policy specifically for event access. Be sure to use the condition within the policy itself, not as a boundary.
You can use the dt.host_group.id with the IN operator. For example:
ALLOW storage:events:read WHERE storage:dt.host_group.id IN (“”)
This might not fully resolve the issue, but it could serve as a helpful interim step.
What I see is that my Problem didn’t have a dt.security_context field filled. I tried to apply the documentation here, but the field still keep empty.
Anyone already fix that ?
I encountered the same problem. Seems like there is no permissions for dt.davis.problems.
If you open developer tools in your browser and query something in the new problems app you can find a request with query: “{ canonicalQuery: 'fetch dt.davis.problems, from:now() - 2h …”
I don’t know how should I set problem fields for security context. I can add only one field that maps something to the security context and I have no idea what to use here to make sure that every event will have security context mapped.
Hello @peter,
I’ve created a ticket to the support. Do you have any update on your side about this issue? Currently the boundaries cannot be used as they won’t work with all Dynatrace apps.
ALLOW storage:events:read WHERE storage:dt.security_context IN ("${bindParam:security-context-ids}");
However it would be much more logic, if the problems generated with one agents generated traces or metrics already had a security context set per default.
Hi @ftmazzone , Can i have this in detailed way. because we are using boundaries restricted with management zone and security context. But unfortunately, users with these permissions are unable to view the latest UI/ Gen3 based environment like data/metrics/logs
We don’t use boundaries but template policies however both should work.
1. Could you check if the field `dt.security_context` is set and visible in the page `Problems` ?
2. Are the logs or metrics with the same `dt.security_context` visible for the users havbing this boundary ?
@ftmazzone , Actually this parameter is available for account admins, environments admis.
In our case we are actually looking to restrict the user with boundaries for latest UI we are using `dt.security_context` as suggested by Dynatrace Vendor similarly for Classic UI we are using management zones. User’s able to view all of the allowed information in Classic UI but, when it comes to latest UI of dynatrace entities and its names along with `dt.security_context` is visible but user’s unable to view the metrics, logs, kuberenetes node names, workload names, etc. But data/metrics/logs related to them is not visible to the user’s.