In my previous post I had discussed about Azure Monitor | Data Collection Rules.
https://hiyusuf.blogspot.com/2021/12/azure-monitor-data-collection-rules.html
In this article we will discuss with one of the use case scenario on implementing Data Collection rule.
Current Scenario:
This Workspace consist of Logs / counters of VM's , VM scale sets.
Requirement: Now, this enterprise have a centralize team who wants to centrally monitor / needs to view / keep an eye on performance counters for each VM's in each subscriptions from all regions.
Proposed Scenario:
New proposed scenario will be as followed to achieve given requirements:
- Create a new Log Analytics Workspace per Region (As workspace are region specific).
- Go to Azure Monitor | Data Connection Rule | Create New Rule (For each subscription level)
- Basic - Select the subscription to manage deployed resources and costs. Use resource groups like folders to organize and manage all of your resources.
- Resources - Pick a set of machines to collect data from. The Azure Monitor Agent will be automatically installed on these machines.(This will also enable System Assigned Managed Identity on these machines, in addition to existing User Assigned Identities (if any).)
- Collect & Deliver - Configure which data sources to collect, and where to send the data to.
- Data Source type - Select which data source type and the data to collect for your resource(s).
- Destination - Select the destination(s) for where the data will be delivered. ( Destination Type depends on what type of data source selected) example, if data source is selected as windows event logs -- destination type will only show Azure monitor logs & if data source is selected as performance counters -- destination type will show Azure monitor metrics & Azure monitor logs.
- Select the destination workspace (in one case the centralize workspace).
- Review & Create.
No comments:
Post a Comment