Skip to content

Commit 42242e8

Browse files
authored
Merge pull request #262348 from rcdun/rathishr2712
new BCDR article
2 parents 4acd511 + 3042922 commit 42242e8

File tree

5 files changed

+98
-8
lines changed

5 files changed

+98
-8
lines changed

articles/operator-insights/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@
1717
items:
1818
- name: Managed identity
1919
href: managed-identity.md
20+
- name: Business continuity disaster recovery
21+
href: business-continuity-disaster-recovery.md
2022
- name: Data quality and data monitoring
2123
href: concept-data-quality-monitoring.md
2224
- name: Data types
@@ -36,6 +38,8 @@
3638
href: dashboards-use.md
3739
- name: Query data in the Azure Operator Insights Data Product
3840
href: data-query.md
41+
- name: Manage permissions to the consumption URL
42+
href: consumption-plane-configure-permissions.md
3943
- name: Deploy Ingestion Agents for MCC protobuf EDRs
4044
items:
4145
- name: Create and configure MCC EDR Ingestion Agents
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
title: Business Continuity and Disaster recovery (BCDR) for Azure Operator Insights
3+
description: This article helps you understand BCDR concepts Azure Operator Insights.
4+
author: rcdun
5+
ms.author: rdunstan
6+
ms.reviewer: duncanarcher
7+
ms.service: operator-insights
8+
ms.topic: concept-article
9+
ms.date: 11/27/2023
10+
---
11+
12+
# Business continuity and disaster recovery
13+
14+
Disasters can be hardware failures, natural disasters, or software failures. The process of preparing for and recovering from a disaster is called disaster recovery (DR). This article discusses recommended practices to achieve business continuity and disaster recovery (BCDR) for Azure Operator Insights.
15+
16+
BCDR strategies include availability zone redundancy and user-managed recovery.
17+
18+
## Control plane
19+
20+
The Azure Operator Insights control plane is resilient both to software errors and failure of an Availability Zone. The ability to create and manage Data Products isn't affected by these failure modes.
21+
22+
The control plane isn't regionally redundant. During an outage in an Azure region, you can't create new Data Products in that region or access/manage existing ones. Once the region recovers from the outage, you can access and manage existing Data Products again.
23+
24+
## Data plane
25+
26+
Data Products are resilient to software or hardware failures. For example, if a software bug causes the service to crash, or a hardware failure causes the compute resources for enrichment queries to be lost, service automatically recovers. The only impact is a slight delay in newly ingested data becoming available in the Data Product's storage endpoint and in the KQL consumption URL.
27+
28+
### Zone redundancy
29+
30+
Data Products don't support zone redundancy. When an availability zone fails, the Data Product's ingestion, blob/DFS and KQL/SQL APIs are all unavailable, and dashboards don't work. Transformation of already-ingested data is paused. No previously ingested data is lost. Processing resumes when the availability zone recovers.
31+
32+
What happens to data that was generated during the availability zone outage depends on the behavior of the ingestion agent:
33+
34+
* If the ingestion agent buffers data and resends it when the availability zone recovers, data isn't lost. Azure Operator Insights might take some time to work through its transformation backlog.
35+
* Otherwise, data is lost.
36+
37+
### Disaster recovery
38+
39+
Azure Operator Insights has no innate region redundancy. Regional outages affect Data Products in the same way as [availability zone failures](#zone-redundancy). We have recommendations and features to support customers that want to be able to handle failure of an entire Azure region.
40+
41+
#### User-managed redundancy
42+
43+
For maximal redundancy, you can deploy Data Products in an active-active mode. Deploy a second Data Product in a backup Azure region of your choice, and configure your ingestion agents to fork data to both Data Products simultaneously. The backup data product is unaffected by the failure of the primary region. During a regional outage, look at dashboards that use the backup Data Product as the data source. This architecture doubles the cost of the solution.
44+
45+
Alternatively, you could use an active-passive mode. Deploy a second Data Product in a backup Azure region, and configure your ingestion agents to send to the primary Data Product. During a regional outage, reconfigure your ingestion agents to send data to the backup Data Product during a region outage. This architecture gives full access to data created during the outage (starting from the time where you reconfigure the ingestion agents), but during the outage you don't have access to data ingested before that time. This architecture requires a small infrastructure charge for the second Data Product, but no additional data processing charges.
Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
title: Manage permissions for Azure Operator Insights consumption plane
3+
description: This article helps you configure consumption URI permissions for Azure Operator Insights.
4+
author: rcdun
5+
ms.author: rdunstan
6+
ms.reviewer: duncanarcher
7+
ms.service: operator-insights
8+
ms.topic: how-to
9+
ms.date: 1/06/2024
10+
---
11+
12+
# Manage permissions to the consumption URL
13+
14+
Azure Operator Insights enables you to control access to the consumption URL of each Data Product based on email addresses or distribution lists. Use the following steps to configure read-only access to the consumption URL.
15+
16+
Azure Operator Insights currently supports a single role that gives Read access to all tables and columns on the consumption URL.
17+
18+
## Add user access
19+
20+
1. Sign in to the [Azure portal](https://portal.azure.com).
21+
1. Go to your Azure Operator Insights Data Product resource.
22+
1. In the left-hand menu under **Security**, select **Permissions**.
23+
1. Select **Add Reader** to add a new user.
24+
1. Type in the user's email address or distribution list and select **Add Reader(s)**.
25+
1. Wait for about 30 seconds, then refresh the page to view your changes.
26+
27+
## Remove user access
28+
29+
1. Sign in to the [Azure portal](https://portal.azure.com).
30+
1. Go to your Azure Operator Insights Data Product resource.
31+
1. In the left-hand menu under **Security**, select **Permissions**.
32+
1. Select the **Delete** symbol next to the user who you want to remove.
33+
> [!NOTE]
34+
> There is no confirmation dialog box, so be careful when deleting users.
35+
1. Wait for about 30 seconds, then refresh the page to view your changes.

articles/operator-insights/data-query.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: operator-insights
88
ms.topic: how-to
99
ms.date: 10/22/2023
1010

11-
#CustomerIntent: As a consumer of the Data Product, I want to query data that has been collected so that I can visualise the data and gain customised insights.
11+
#CustomerIntent: As a consumer of the Data Product, I want to query data that has been collected so that I can visualize the data and gain customized insights.
1212
---
1313

1414
# Query data in the Data Product
@@ -19,14 +19,16 @@ The Azure Operator Insights Data Product stores enriched and processed data, whi
1919

2020
## Prerequisites
2121

22-
A deployed Data Product, see [Create an Azure Operator Insights Data Product](data-product-create.md).
22+
- A deployed Data Product: see [Create an Azure Operator Insights Data Product](data-product-create.md).
23+
- The `Reader` role for the data for this Data Product, because access to the data is controlled by role-based access control (RBAC).
24+
- To check your access, sign in to the [Azure portal](https://portal.azure.com), go to the Data Product resource and open the **Permissions** pane. You must have the `Reader` role.
25+
- If you don't have this role, ask an owner of the resource to give you `Reader` permissions by following [Manage permissions to the consumption URL](consumption-plane-configure-permissions.md).
2326

24-
## Get access to the ADX cluster
27+
## Add the consumption URL in Azure Data Explorer
2528

26-
Access to the data is controlled by role-based access control (RBAC).
27-
28-
1. In the Azure portal, select the Data Product resource and open the Permissions pane. You must have the `Reader` role. If you do not, contact an owner of the resource to grant you `Reader` permissions.
29-
1. In the Overview pane, copy the Consumption URL.
29+
1. Sign in to the [Azure portal](https://portal.azure.com).
30+
1. Go to your Azure Operator Insights Data Product resource.
31+
1. In the **Overview** pane, copy the Consumption URL.
3032
1. Open the [Azure Data Explorer web UI](https://dataexplorer.azure.com/) and select **Add** > **Connection**.
3133
1. Paste your Consumption URL in the connection box and select **Add**.
3234

articles/operator-insights/index.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,14 +31,18 @@ landingContent:
3131
links:
3232
- text: Managed identity
3333
url: managed-identity.md
34+
- text: Business continuity and disaster recovery
35+
url: business-continuity-disaster-recovery.md
3436
- text: Data quality and data monitoring
3537
url: concept-data-quality-monitoring.md
3638
- text: Data types
3739
url: concept-data-types.md
3840
- text: Data visualization
3941
url: concept-data-visualization.md
40-
- text: MCC Data Product
42+
- text: Quality of Experience - Affirmed MCC Data Product
4143
url: concept-mcc-data-product.md
44+
- text: Monitoring - Affirmed MCC Data Product
45+
url: concept-monitoring-mcc-data-product.md
4246

4347
# Card
4448
- title: Get started with Azure Operator Insights

0 commit comments

Comments
 (0)