You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Microsoft Teams Integration |@datadog/datadog-api-client-microsoft-teams-integration |[README.md](../../services/microsoft-teams-integration/README.md)|
**Note: This endpoint is in public beta. If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).**
6
+
7
+
A Restriction Query is a logs query that restricts which logs the `logs_read_data` permission grants read access to.
8
+
For users whose roles have Restriction Queries, any log query they make only returns those log events that also match
9
+
one of their Restriction Queries. This is true whether the user queries log events from any log-related feature, including
10
+
the log explorer, Live Tail, re-hydration, or a dashboard widget.
11
+
12
+
Restriction Queries currently only support use of the following components of log events:
13
+
14
+
- Reserved attributes
15
+
- The log message
16
+
- Tags
17
+
18
+
To restrict read access on log data, add a team tag to log events to indicate which teams own them, and then scope Restriction Queries to the relevant values of the team tag. Tags can be applied to log events in many ways, and a log event can have multiple tags with the same key (like team) and different values. This means the same log event can be visible to roles whose restriction queries are scoped to different team values.
19
+
20
+
See [How to Set Up RBAC for Logs](https://docs.datadoghq.com/logs/guide/logs-rbac/?tab=api#restrict-access-to-logs) for details on how to add restriction queries.
0 commit comments