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:
- Design a Log Analytics workspace architecture - Design criteria
- Phase 1: Prerequisite planning for Azure server management services - Resource placement examples
Kindly accept answer , if it helps
Thanks
Deepanshu