SOLVED

Monitoring Through Log Aanlytics

Brass Contributor

Hi All,

 

I want to monitor all below given resources through Log Analytics.

 

  • Storage account
  • Event Hubs Namespace
  • Load balancers
  • Network interface
  • Public IP address
  • Application Gateway
  • Automation Account
  • Key vault
  • Network security group
  • Azure Database for MySQL server
  • API Management service
  • Azure Databricks Service
  • Recovery Services vault
  • ExpressRoute circuit
  • Virtual network gateway
  • Virtual network
  • Azure Activity
  • Checkpoint Firewall (NVA)
  • VPNs
  • Azure Native backup
  • Azure & on-Prem Active Directory (DHCP, DNS).

 

I have checked and found this could be possible through signal based alert (given by Microsoft metric).

Now concern if I will use this option then i have to follow this same click-click pattern for each and every resource.

 

Is there any way to achieve these task through script or KQL.

 

Thanks in advance for the help :)

2 Replies

@GouravIN 

 

Here are examples to create Log Alerts

 

https://techcommunity.microsoft.com/t5/Azure-Monitor/Azure-Monitor-predefined-Alerts/m-p/786683/high...

 

For Metric alerts 

This article (I've not used it myself) talks about custom metrics (if you haven't found one or two you need and using ARM to build alerts

 

CLI

https://docs.microsoft.com/en-us/powershell/azure/release-notes-azureps?view=azps-1.8.0#azmonitor and https://docs.microsoft.com/en-us/powershell/module/az.monitor/add-azmetricalertrulev2?view=azps-1.8....

 

 

Thanks Clive 

 

best response confirmed by GouravIN (Brass Contributor)
Solution
Be careful with Log Alerts if you're using Azure Diagnostics to collect log data from the different resources as you will run into an issue where the Azure Diagnostics schema will grow to 500 columns and new resource types will not be able to be ingested. Wherever it is available, use the resource specific diagnostics: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-logs-stream-log-store#azure...
1 best response

Accepted Solutions
best response confirmed by GouravIN (Brass Contributor)
Solution
Be careful with Log Alerts if you're using Azure Diagnostics to collect log data from the different resources as you will run into an issue where the Azure Diagnostics schema will grow to 500 columns and new resource types will not be able to be ingested. Wherever it is available, use the resource specific diagnostics: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-logs-stream-log-store#azure...

View solution in original post