@AnuragSingh-MSFT - Thanks for reaching out to us.
It's essential to first ensure that VMInsights is enabled and correctly configured for your VM. This involves verifying that data is being sent to the 'InsightMetrics' table as expected. Additionally, understanding the billing model of VMInsights is crucial. This includes the costs associated with log search alerts generated from data sent to the log analytics workspace and metric alerts based on native metrics. Proper configuration of alerts to ensure they trigger under the correct conditions is also key to avoiding similar issues in the future.
For more detailed information on configuring VMInsights and understanding its billing model, please refer to the following:
https://docs.microsoft.com/en-us/azure/azure-monitor/vm/vminsights-overview
https://docs.microsoft.com/en-us/azure/azure-monitor/logs/manage-cost
Hope this helps. and please feel free to reach out if you have any further questions.
Please don't forget to "Accept as Answer" and click "Yes" if the above response is helpful, so it can be beneficial to the community.