How can we improve Azure Diagnostics and Monitoring?

Show memory and network metrics as percentages

Since each VM / Cloud Service has 3 major metrics: CPU, Memory , Network - diagnostics should collect this metrics by default (logging level minimal).

Because there are allot of instance types absolute values of Network and Memory counters are not informative and % should be used.
It is more informative to know that instance is using 90% of memory than to have a value of 600 MB. Same is for the network channel load. For example my service is network intensive and now it is really hard to understand when network channel load comes to it's limit and service scale is required.

Once this 2 metrics will be implemented they should be put to auto-scale. I strongly believe that combined with service bus queue they will cover all possible case of auto-scale.

62 votes
Vote
Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
You have left! (?) (thinking…)
Стас Султанов shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
under review  ·  Azure portal team responded  · 

This is very good feedback. Today we have separate datasources for what your quotas are (e.g. network, memory), and the metrics that we emit. Ideally, we could bring those two points together to give you a percentage of those metrics.

Also, once these are exposed, they will automatically be available for autoscale — already today you can use any exposed metric for scaling.

2 comments

Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base