Azure Monitor can be used for centralized monitoring and analysis of log data by using Kusto queries, so Azure Monitor allows you to effectively monitor and visualize Azure resources. Azure Arc also empowers Azure Monitor to expand its capabilities to on-premises and other public clouds. You can monitor every resource across environments, Azure, AWS, GCP, OCI, on-premise and others, with Azure Monitor and Azure Arc, then Azure Monitor minimizes your effort to manage all the resources regardless of location or environments. Refer to Azure Monitor overview article for the detail.
Azure Monitor is a very powerful solution, but customers and partners sometimes have a challenge mapping Azure Monitor features to their functional and non-functional requirements. These series of articles describe how to use various Azure Monitor features in terms of functional and non-functional requirements.
Note: ISVs and partners offer 3rd party monitoring solutions on Azure Marketplace, so you might use the solutions if Azure Monitor might not work well for the requirements.
Here are popular monitoring objectives based on functional and non-functional requirements for monitoring.
Monitor network with SNMP Azure network status can be monitored by configuring "diagnostic setting". Azure Monitor offers great monitoring features to meet most cases, but Azure Monitor doesn't offer snmp agent or snmpwalk agent.
You will have to complete the three configurations below before following these series of articles for Azure Monitor.
1.1. Setup Log Analytics workspace
Azure Monitor uses "metrics" and "logs" for its data. Metric refers to system info for Azure resources, for example CPU usage and memory usage. Log refers to Event Log and syslog. Each Azure resource has settings named as "diagnostic setting" and "activity log", which store logs of the resources on Azure services; for example Log Analytics, Azure Storage, and others. Especially, Log Analytics workspace can be used for analysis and troubleshooting with Kusto query.
1.2. Setup Azure Blob Storage
You can store logs on Azure Blob Storage "diagnostic setting" log and "activity log". Azure Blob Storage can be used to store logs with long term duration in terms of security rules for example regional compliances.
Azure VM is used to take logs. Create Azure VM by following an article here. Open Azure Portal with browser and choose your Log Analytics workspace. Select "Virtual Machine" on left menus. Your fresh VM is not connected to any Log Analytics workspace, thus you need to connect your VM to a Log Analytics workspace. Please note that the VM is required to be running when you enable the VM to connect to a Log Analytics workspace. This operation will install and lunch Log Analytics agent on the VM.
2. Key tips to leverage Azure Monitor for enterprise use cases
Here should be useful tips to configure Azure Monitor for enterprise hybrid network requirements.
2.1. Access Log Analytics workspace with private network
AMPLS(Azure Monitor Private Link Scope) can allow you to have closed network access. Log Analytics workspace is required to setup "Network Isolation - Public Access" as "No", thus users privately access to the workspace. Log Analytics or Azure Monitor agent prefers to Azure DNS records than others, so the agent sends logs with HTTPS to Log Analytics workspace via private IP addresses of the workspace FQDN. https://docs.microsoft.com/en-us/azure/azure-monitor/logs/private-link-configure
2.2. Check connectivity with Log Analytics workspace via proxy servers
omsagent uses https protocol as 443/tcp and access to some FQDN. You need to configure Azure Firewall and NVA to allow omsagent to access the FQDN if your VM needs to use Azure Firewall or NVA for outbound access. Refer to this article for details.
2.4 Retrieve all Log Analytics table
We can check Log Analytics tables on Azure Portal, but Azure Portal would show with only metadata and no logging data. We can retrieve all tables having logging data by using search operator with a wildcard. The result contains a $table column that represents the table in which record was found, thus the distinct operator is used to create a list of unique tables.
| distinct $table
Now, we can start these series articles for Azure Monitor. In next post, we will dive deep to "Compute" monitoring objective.
add link for Storage/Disk monitoring
add "2.4 Retrieve all Log Analytics table" section