What is best practice to use Log Analytics Workspace for all production and non production work

Saba Akhtar 20 Reputation points
2024-05-31T09:13:32.3333333+00:00

We are currently in the process of setting up the Log Analytics workspace in the new Tenant. We have a lot of subscriptions ranging from dev, test, cert, stage and production for 3 main projects.

Previosuly we used to have one workspace per project and environment but now we would like to go with one production and one non-production workspace for all subscriptions. Please advise if this is a good approach and how we control data utilised by one project not consuming all GB allocated to that workspace.

e.g
Sub A - DailyCap set at 1GB
Sub B - DailyCap set at 1GB
Sub C - DailyCap set at 1 GB

Log Analytics WorkSpace - Prod - DailyCap set at 3GB.
I am assuming if we set Daily Cap as above it will give isolation to the usage of resources. Please advise.

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
2,921 questions
0 comments No comments
{count} votes

Accepted answer
  1. Deepanshu katara 6,245 Reputation points
    2024-05-31T09:59:13.3833333+00:00

    Hi

    It is indeed a good approach to have separate Log Analytics workspaces for production and non-production environments. This ensures data segregation and easier management.

    To control data utilization by one project not consuming all GB allocated to that workspace, you can set up data retention and archive policies for each workspace. This allows you to manage how much data is stored in each workspace and for how long, helping to control data consumption.

    Additionally, you can use Azure Cost Management + Billing to view charges by workspace and monitor the data volume by Azure resource, resource group, or subscription. This can provide you with a detailed view of data usage and costs associated with each workspace.

    If you need to split billing or perform chargeback, you can consider using separate workspaces for each cost owner. This allows for more granular control over costs and can help ensure that one project does not consume all the allocated GB.

    For more information, you can refer to the following resources:

    Kindly accept answer , if it helps

    Thanks

    Deepanshu

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful