Skip to content

Commit f97f1f9

Browse files
authored
Merge pull request #197480 from MicrosoftDocs/main
Merge master to live Sunday at 4 PM
2 parents 8ad3db2 + 01375fe commit f97f1f9

37 files changed

+386
-120
lines changed

articles/active-directory/fundamentals/custom-security-attributes-overview.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: fundamentals
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 03/28/2022
11+
ms.date: 05/09/2022
1212
ms.collection: M365-identity-device-management
1313
---
1414

@@ -149,8 +149,9 @@ Here are some of the limits and constraints for custom security attributes.
149149
> | Predefined values per attribute definition | 100 | |
150150
> | Attribute value length | 64 | Unicode characters |
151151
> | Attribute values assigned per object | 50 | Values can be distributed across single and multi-valued attributes.<br/>Example: 5 attributes with 10 values each or 50 attributes with 1 value each |
152-
> | Characters not allowed for:<br/>Attribute set name<br/>Attribute name | ``<space> ` ~ ! @ # $ % ^ & * ( ) _ - + = { [ } ] \| \ : ; " ' < , > . ? /`` | Attribute set name and attribute name cannot start with a number |
153-
> | Characters not allowed for:<br/>Attribute values | `# % & * + \ : " / < > ?` | |
152+
> | Special characters **not** allowed for:<br/>Attribute set name<br/>Attribute name | ``<space> ` ~ ! @ # $ % ^ & * ( ) _ - + = { [ } ] \| \ : ; " ' < , > . ? /`` | Attribute set name and attribute name cannot start with a number |
153+
> | Special characters allowed for attribute values | All special characters | |
154+
> | Special characters allowed for attribute values when used with blob index tags | `<space> + - . : = _ /` | If you plan to use [attribute values with blob index tags](../../role-based-access-control/conditions-custom-security-attributes.md), these are the only special characters allowed for blob index tags. For more information, see [Setting blob index tags](../../storage/blobs/storage-manage-find-blobs.md#setting-blob-index-tags). |
154155
155156
## Custom security attribute roles
156157

articles/active-directory/governance/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -134,6 +134,8 @@
134134

135135
- name: Groups and apps
136136
items:
137+
- name: Prepare for an app access review
138+
href: access-reviews-application-preparation.md
137139
- name: Create an access review
138140
href: create-access-review.md
139141
- name: Review access

articles/active-directory/governance/access-reviews-application-preparation.md

Lines changed: 149 additions & 0 deletions
Large diffs are not rendered by default.

articles/active-directory/governance/create-access-review.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,8 @@ This article describes how to create one or more access reviews for group member
3737

3838
For more information, see [License requirements](access-reviews-overview.md#license-requirements).
3939

40+
If you are reviewing access to an application, then before creating the review, see the article on how to [prepare for an access review of users' access to an application](access-reviews-application-preparation.md) to ensure the application is integrated with Azure AD.
41+
4042
## Create a single-stage access review
4143

4244
### Scope

articles/active-directory/governance/deploy-access-reviews.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -319,7 +319,9 @@ To create access reviews for an application, set the **User assignment required?
319319

320320
![Screenshot that shows planning app assignments.](./media/deploy-access-review/6-plan-applications-assignment-required.png)
321321

322-
Then [assign the users and groups](../manage-apps/assign-user-or-group-access-portal.md) that you want to have access.
322+
Then [assign the users and groups](../manage-apps/assign-user-or-group-access-portal.md) whose access you want to have reviewed.
323+
324+
Read more about how to [prepare for an access review of users' access to an application](access-reviews-application-preparation.md).
323325

324326
### Reviewers for an application
325327

articles/active-directory/governance/manage-user-access-with-access-reviews.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@ With Azure Active Directory (Azure AD), you can easily ensure that users have ap
3030

3131
For more information, see [License requirements](access-reviews-overview.md#license-requirements).
3232

33+
If you are reviewing access to an application, then before creating the review, see the article on how to [prepare for an access review of users' access to an application](access-reviews-application-preparation.md) to ensure the application is integrated with Azure AD.
34+
3335
## Create and perform an access review
3436

3537
You can have one or more users as reviewers in an access review.
@@ -38,7 +40,7 @@ You can have one or more users as reviewers in an access review.
3840

3941
2. Decide whether to have each user review their own access or to have one or more users review everyone's access.
4042

41-
3. In one of the following roles: a global administrator, user administrator, or (Preview) a M365 or AAD Security Group owner of the group to be reviewed, go to the [Identity Governance page](https://portal.azure.com/#blade/Microsoft_AAD_ERM/DashboardBlade/).
43+
3. In one of the following roles: a global administrator, user administrator, or (Preview) an owner of a Microsoft 365 group or Azure AD security group to be reviewed, go to the [Identity Governance page](https://portal.azure.com/#blade/Microsoft_AAD_ERM/DashboardBlade/).
4244

4345
4. Create the access review. For more information, see [Create an access review of groups or applications](create-access-review.md).
4446

Loading

articles/active-directory/managed-identities-azure-resources/managed-identities-status.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,7 @@ The following Azure services support managed identities for Azure resources:
6161
| Azure Resource Mover | [Move resources across regions (from resource group)](../../resource-mover/move-region-within-resource-group.md)
6262
| Azure Site Recovery | [Replicate machines with private endpoints](../../site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints.md#enable-the-managed-identity-for-the-vault) |
6363
| Azure Search | [Set up an indexer connection to a data source using a managed identity](../../search/search-howto-managed-identities-data-sources.md) |
64+
| Azure Service Bus | [Authenticate a managed identity with Azure Active Directory to access Azure Service Bus resources](../../service-bus-messaging/service-bus-managed-service-identity.md) |
6465
| Azure Service Fabric | [Using Managed identities for Azure with Service Fabric](../../service-fabric/concepts-managed-identity.md) |
6566
| Azure SignalR Service | [Managed identities for Azure SignalR Service](../../azure-signalr/howto-use-managed-identity.md) |
6667
| Azure Spring Cloud | [How to enable system-assigned managed identity for Azure Spring Cloud application](../../spring-cloud/how-to-enable-system-assigned-managed-identity.md) |

articles/cosmos-db/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1152,6 +1152,8 @@
11521152
href: cassandra/lwt-cassandra-api.md
11531153
- name: Cassandra API extensions overview
11541154
href: cassandra/cassandra-driver-extensions.md
1155+
- name: Monitor and debug with insights in Cassandra API
1156+
href: cassandra/cassandra-monitor-insights.md
11551157
- name: Reference
11561158
items:
11571159
- name: REST resource provider
Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
---
2+
title: Monitor and debug with insights in Azure Cosmos DB Cassandra API
3+
description: Learn how to debug and monitor your Azure Cosmos DB Cassandra API account using insights
4+
author: iriaosara
5+
ms.author: iriaosara
6+
ms.service: cosmos-db
7+
ms.subservice: cosmosdb-cassandra
8+
ms.topic: how-to
9+
ms.date: 05/02/2022
10+
ms.custom: template-how-to
11+
---
12+
13+
# Monitor and debug with insights in Azure Cosmos DB Cassandra API
14+
[!INCLUDE[appliesto-cassandra-api](../includes/appliesto-cassandra-api.md)]
15+
16+
Azure Cosmos DB helps provide insights into your application’s performance using the Azure Monitor API. Azure Monitor for Azure Cosmos DB provides metrics view to monitor your Cassandra API Account and create dashboards.
17+
18+
This article walks through some common use cases and how best to use Azure Cosmos DB insights to analyze and debug your Cassandra API account.
19+
> [!NOTE]
20+
> The Azure Cosmos DB metrics are collected by default, this feature does not require you to enable or configure anything.
21+
22+
23+
## Availability
24+
The availability shows the percentage of successful requests over the total requests per hour. Monitor service availability for a specified Cassandra API account.
25+
26+
:::image type="content" source="./media/cassandra-monitor-insights/service-availability-min.png" alt-text=" Screenshot for service availability for an Azure Cosmos DB Cassandra API account.":::
27+
28+
29+
## Latency
30+
These charts below show the read and write latency observed by your Cassandra API account in the region where your account is operating. You can visualize latency across regions for a geo-replicated account. This metric doesn't represent the end-to-end request latency. Use diagnostic log for cases where you experience high latency for query operations.
31+
32+
The server side latency (Avg) by region also displays a sudden latency spike on the server. It can help a customer differentiate between a client side latency spike and a server-side latency spike.
33+
34+
:::image type="content" source="./media/cassandra-monitor-insights/avg-server-side-latency-by-region.png" alt-text="Diagram showing the average server side latency by region.":::
35+
36+
Also view server-side latency by different operations in a specific keyspace.
37+
38+
:::image type="content" source="./media/cassandra-monitor-insights/avg-ss-latency-keyspace-operation.png" alt-text="Screenshot showing the average server side latency for a specific keyspace based on operation.":::
39+
40+
41+
:::image type="content" source="./media/cassandra-monitor-insights/avg-ss-latency-region-keyspace.png" alt-text="Screenshot showing the average server side latency by region and keyspace.":::
42+
43+
44+
Is your application experiencing any throttling? The chart below shows the total number of requests failed with a 429-response code.
45+
Exceeding provisioned throughput could be one of the reasons. Enable [Server Side Retry](./prevent-rate-limiting-errors.md) when your application experiences high throttling due to higher consumption of request units than what is allocated.
46+
47+
:::image type="content" source="./media/cassandra-monitor-insights/throttled-requests.png" alt-text="Screenshot of graph showing throttled request with a defined time frame.":::
48+
49+
50+
51+
## System and management operations
52+
The system view helps show metadata requests count by primary partition. It also helps identify throttled requests. The management operation shows the account activities such as creation, deletion, key, network and replication settings. Request volume per status code over a time period.
53+
54+
:::image type="content" source="./media/cassandra-monitor-insights/metadata-requests-status-code.png" alt-text="Screenshot showing request status code based on metadata.":::
55+
56+
- Metric chart for account diagnostic, network and replication settings over a specified period and filtered based on a Keyspace.
57+
58+
:::image type="content" source="./media/cassandra-monitor-insights/diagnostic-network-replication.png" alt-text="Screenshot of diagnostic network replication for a Cassandra API account.":::
59+
60+
61+
- Metric chart to view account key rotation.
62+
63+
You can view changes to primary or secondary password for your Cassandra API account.
64+
65+
:::image type="content" source="./media/cassandra-monitor-insights/cosmos-db-account-key.png" alt-text="Screenshot showing Cosmos DB rotation key for a Cassandra API account.":::
66+
67+
68+
## Storage
69+
Storage distribution for raw and index storage. Also a count of documents in the Cassandra API account.
70+
71+
:::image type="content" source="./media/cassandra-monitor-insights/data-index-usage.png" alt-text="Diagram showing the document count within a Cassandra API account.":::
72+
73+
Maximum request units consumption for an account over a defined time period.
74+
75+
:::image type="content" source="./media/cassandra-monitor-insights/normalized-ru-consumption.png" alt-text="Diagram showing the maximum request unit consumption.":::
76+
77+
78+
## Throughput and requests
79+
The Total Request Units metric displays the requests unit usage based on operation types.
80+
81+
These operations can be analyzed within a given time interval, defined keyspace or table.
82+
83+
:::image type="content" source="./media/cassandra-monitor-insights/total-cassandra-requests.png" alt-text="Screenshot image of a graph showing the total Cassandra requests for an account.":::
84+
85+
:::image type="content" source="./media/cassandra-monitor-insights/total-request-units.png" alt-text="Screenshot image of a graph showing the total request units for a Cassandra account.":::
86+
87+
The Normalized RU Consumption metric is a metric between 0% to 100% that is used to help measure the utilization of provisioned throughput on a database or container. The metric can also be used to view the utilization of individual partition key ranges on a database or container. One of the main factors of a scalable application is having a good cardinality of partition keys.
88+
The chart below shows if your application’s high RU consumption is because of hot partition.
89+
90+
:::image type="content" source="./media/cassandra-monitor-insights/normalized-ru-pk-rangeid.png" alt-text="Screenshot showing normalized request unit consumption by partition key range ID.":::
91+
92+
The chart below shows a breakdown of requests by different status code. Understand the meaning of the different codes for your [Cassandra API codes](./error-codes-solution.md).
93+
94+
:::image type="content" source="./media/cassandra-monitor-insights/total-request-by-status-code.png" alt-text="Screenshot image of a graph showing the total request by status code for a cassandra api account.":::
95+
96+
97+
## Next steps
98+
- [Monitor and debug with insights in Azure Cosmos DB](../use-metrics.md)
99+
- [Create alerts for Azure Cosmos DB using Azure Monitor](../create-alerts.md)

0 commit comments

Comments
 (0)