How can we improve Azure Diagnostics and Monitoring?

Add CPU and Memory usage metrics per instance

We use New Relic to monitor our cloud services. Sometimes we see an instance going above 80% CPU, which would possibly be solved by rebooting the instance, but it's imposible to identify which of the instances is in trouble in the portal (Azure portal uses _N to name the instances, New Relic uses an ID).

80 votes
Vote
Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
You have left! (?) (thinking…)
Guillermo Bellmann shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

5 comments

Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    is there any way we could automate this....specially like a report i know its off base...can any one suggest...

  • Irfan Metin commented  ·   ·  Flag as inappropriate

    Not sure this is what you mean, but in the Azure Management portal for Cloud Services, on the configuration screen set monitoring from Minimal to Verbose. This adds some new options to the Monitoring screen.
    On the Monitoring screen click [Add Metrics]; You can now switch on monitoring per CPU & Memory per instance.
    Still no link to your New Relic ID, but at least the metrics are now visible within Azure.

  • Ray Sülzer commented  ·   ·  Flag as inappropriate

    Memory usage would be HUGELY helpful. Memory leaks would be easier to spot and mitigate.

Feedback and Knowledge Base