The new version of the graphics in the dashboard are bad and the usability is terrible. The dynamic y axis forces us to have to look at all the graphs one by one to monitor the applications. Ideally, the Y axis should be fixed at 100% (it can not be dynamic). It was beautiful but it was useless.

When an alert is send (Alert(preview)) I receive an email as defined but the fired alert is not showing in the portal

PSS told me today that the HTTP Queue Length metric on the App Service Plan level actually maps to total current active requests, not an HTTP queue. Apparently this issue also existed at the app service level but was previously resolved. (The App Service Plan is in an ASE if that matters.)

Also, if this were a queue, it's aggregating using a sum at lower time grains where an average would be appropriate.

Please allow the 'Summary' and 'Details' Markdown Tags in Azure Monitor workbooks so that one can insert expanders to make long documents more precise. It is a bug that these tags work in one Microsoft tool eg. Visual Studio Code and not in another ie. Azure workbooks.

we were dealing with missing metrics in extended diagnostics. Based recommendation of page https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/azure-diagnostics-troubleshooting we reinstalled the agent, but it didn't lead to the correction. The Metric was created in Azure portal, but the Storage account table persists empty.

The correction of the issue was:

1) Uninstall the monitoring agent

2) delete the directory

C:\\WindowsAzure\\Logs\\Plugins\\Microsoft.Azure.Diagnostics.IaaSDiagnostics\\1.12.0.0\\WAD0107\\Tables
and redeploy the Diagnostics agent. (1.12.0.0 version may differ, The latest one). If this didn't help, than delete all directory C:\\WindowsAzure\\Logs\\Plugins\\Microsoft.Azure.Diagnostics.IaaSDiagnostics.

3) Install again the monitoring agent.

I would recommend to include the deletion of the directory into the uninstall procedure.

When one Alert is triggers using Dimensions in the Email Information it does not specify the Dimension (object) that generated the issue.
This appears only when the alert is set to resolved.

Is this normal procedure or is this a bug?

Azure Diagnostics agent is currently creating a table named WADDefaultTable for ETW events by default. This would be more aptly named WADETWEventTable to comply with other default table names for other log resources (such as the event log).

The preheader for the Azure Monitor Action Group notification email is incorrect, so when you preview your email it states

'You’ve unsubscribed from an Azure Monitor action group'

When you've actually subscribed to an action group

Frequently while I am trying to monitor CPU usage of a VM it will not update the data for a given minute and this leaves wholes in the data

We've created new Metric Alerts via an ARM template (as documented here: https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-create-metric-alerts-with-templates and https://docs.microsoft.com/en-us/rest/api/monitor/metricalerts/createorupdate)

If we pass multiple resources in the scopes array, we see three unexpected behaviours:
1) The alert only fires for the first resource in the array
2) The Monitor ui on the portal shows no alert definitions, unless you enable the new portal experience.
3) The new portal experience only shows a single resource being monitored

Retrieving the alert definitions from the REST API shows that the multiple resources in the scope have indeed been successfully stored.

When adding an alert rule on a VM, the display for "% Committed Bytes in Use" or "% Free Space" metrics show the units under "Threshold" as "Count", but this should be "%". It also shows in the Condition column when looking at a list of Alerts (for example, "> 80 Count" instead of "> 80 Percent").
This seems to be a bug with Portal display for those two metrics and should be fixed.

Last night during what I assume was an auto-update of the Azure Diagnostics service on a Windows Server 2012 VM in Azure, it stopped our World Wide Web Publishing Service and did not restart it. This resulted in a service disruption.

I've attached the Event Log error.

Why did it need to stop the WWW service?
Is there some way to know in advance if it's going to do this, or control when it happens?

Am unable to change the edit chart metric betweenpast hour/ past week/ custom at times, clicking save does not save all the time

It seems that Azure Monitor REST API for SQL Databases and Storage changed functionality and broke my code 2 days ago. (west europe)

I had a simple REST call that would fetch all 1 minut metrics for a single resource in a single call. New preview api doesn't allow specifying more than a single metric per call which means that my code is now needing to make a call for each metric on each resource. It's probably 10x more REST calls than before.

This worked great with the old API, but 2 days ago it started to return BadOperation.

On portal in path: Home > Diagnostics settings there is no option to manage diagnostics settings for related resources, each time after configuring resource and closing blade portal redirects me to dashboard. Same thing in Monitor service. As a user I would like to configure few services by adding these settings, back to the list, configure another one. For now it is impossible.

I posted in the MSDN forum and finally solved it. Please read the forum notes for full details and fixes too. Let me highlight the bug. When you click on Diagnostics and then Overview you get a screen for configuring the counters. There it gives option None-Basic-Custom. So it turns out what ever you see set there is actually not set that display is wrong. So when you start the monitor it will say not data found because not counter has been set. So you have to actually edit and add it.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/2bf448f5-372c-478d-a55d-8c5bab6af99f/diagnostic-monitoring-does-not-work-on-azure-stack-single-node-deployment?forum=AzureStack

On the startboard, you can't label a chart. Clicking the chart opens a metrics blade, but there is no context or way of figuring out WHAT system those metrics are reporting from. Metrics blades should display the server/service they are reporting on since they are not ALWAYS displayed in the context of that server.