How to check if workspace is replicated?

Hoeneveld, T.A. (Tim) 30 Reputation points
2024-09-24T13:35:20.9733333+00:00

Dear support,

We are testing out the workspace-replication feature (https://video2.skills-academy.com/en-us/azure/azure-monitor/logs/workspace-replication) for log analytic workspaces.

When creating a replication workspace and sending the request as mentioned in the wiki, I am not recvieing a response from the API. I am also unable to see any changes in the protal.

How can I valdidate that the change has been made?

Thanks!

This is the respons from a get request:

Before and after doing the failover (POST) request this repsone stays the same.

{
    "properties": {
        "customerId": "0000000",
        "provisioningState": "Succeeded",
        "sku": {
            "name": "pergb2018",
            "lastSkuUpdate": "2024-09-24T11:48:51.1656929Z"
        },
        "retentionInDays": 30,
        "features": {
            "legacy": 0,
            "searchVersion": 1,
            "enableLogAccessUsingOnlyResourcePermissions": true
        },
        "workspaceCapping": {
            "dailyQuotaGb": -1.0,
            "quotaNextResetTime": "2024-09-24T20:00:00Z",
            "dataIngestionStatus": "RespectQuota"
        },
        "publicNetworkAccessForIngestion": "Enabled",
        "publicNetworkAccessForQuery": "Enabled",
        "createdDate": "2024-09-24T11:48:51.1656929Z",
        "modifiedDate": "2024-09-24T12:32:54.3637488Z",
        "replication": {
            "enabled": true,
            "location": "North Europe",
            "provisioningState": "Succeeded",
            "lastModifiedDate": "2024-09-24T12:23:47.9084387Z"
        }
    },
    "location": "westeurope",
    "tags": {},
    "id": "/subscriptions//resourceGroups//providers/Microsoft.OperationalInsights/workspaces/<name>",
    "name": "<name>",
    "type": "Microsoft.OperationalInsights/workspaces",
    "etag": ""
}
Microsoft Sentinel
Microsoft Sentinel
A scalable, cloud-native solution for security information event management and security orchestration automated response. Previously known as Azure Sentinel.
1,129 questions
0 comments No comments
{count} votes

Accepted answer
  1. Pauline Mbabu 330 Reputation points Microsoft Employee
    2024-09-26T12:37:49.3433333+00:00

    Hello @Hoeneveld, T.A. (Tim) ,
    Thank you for your question.

    The secondary workspace serves as a "shadow" workspace solely for resiliency purposes. It is not visible in the Azure portal, and you cannot manage or access it directly.

    Based on the provided JSON, it appears that replication is enabled, and the provisioning state is successful.

    If you are using the Azure Monitor Agent and the Logs Ingestion API, you will utilize data collection rules (DCR). When workspace replication is enabled, Azure Monitor creates a system data collection endpoint (DCE) with a name identical to your workspace ID.

    To replicate data, you need to associate your data collection rules with this system DCE. This ensures that only the specified log streams are replicated, helping control replication costs.

    Here are the steps to associate DCR with the system DCE:

    1. In the Azure portal, select Data collection rules.
    2. Choose a data collection rule that sends data to your primary Log Analytics workspace.
    3. On the Overview page, select Configure DCE and choose the system DCE from the list.

    Note: Data collection rules connected to a workspace’s system DCE can only target that specific workspace and not other destinations.

    Before switching to the secondary workspace during switchover, ensure it contains sufficient logs. It is recommended to wait at least one week after enabling replication to allow for adequate data availability in the secondary region.

    To trigger the switchover, use the POST command, which is a long-running operation that can take some time to complete. A successful call returns a 202-status code.

    If the API is not responding, ensure that your request is correctly formatted and that you have the necessary permissions.

    After the switchover, the secondary workspace should now be active, and the primary workspace should be inactive. You can verify this in the Azure portal under the Log Analytics workspace settings. When you also go to the Workspace Overview Page you should see a banner telling you that you are in Failover and some operations are not supported.

    If this answers your question, please accept the answer to help community members with similar questions.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.