Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Diagnostics and Monitoring

  1. Add a Counter for the Autoscale Instances to the Monitor

    Pmease add a Metric for the Autoscale to the Monitor-Tab of the Portal

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Scaling of Worker Roles according to Service Bus Message Queues -> Regard Message Status (NOT scale up for scheduled messages)

    Since i would like to auto scale worker roles according to service bus message bus queue lengths it does not make any sense IMHO to scale up regardless of the status the messages actually have. If there are messages scheduled and not likely to become active for a long time it is not possible at the moment to scale according to queue length that actually matters -> Active Messages.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    This is a good idea. Thanks for raising it. We will take a look at this autoscale support.

    Any additional votes?

  3. The (auto) scaling graph has a really wierd timebase. The x-Axis needs to autoscale!

    Like the title says, when starting with autoscaling, the graph looks awful and overwrites itsself if there are several scaling actions. The x-axis needs to autoscale and be configurable (time range). Furthermore, the legend needs to be explained, how does cpu percentage fit into the y-axis of the instance count?

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Improve the Auto Scaling based on queue feature

    1. currently we can only specify a queue and auto scaling based on the queue size regardless of the message type in the queue, for instance, we have deadletter messages and scheduled messages, but it is only the active messages that needs to be considered for auto-scaling, this impacts the cost significantly.

    2. auto-scaling's up scaling only supports fixed numbers, can we support relative numbers? for instance, calculate based on the numbers of messages in the queue

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Fix "no available metric" in the Edit Chart item

    Screenshot:

    http://i.imgur.com/wmTKrRT.png

    No available metric? That's a bit hard to believe. Seems more likely that the service that provides the list of metrics failed.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Enable a "before or after" event to be defined in auto-scaling of Cloud Services

    We domain-join the Virtual Machines associated with our Cloud Service roles. Of course, the process of joining the domain forces a reboot. And, when scaling up, this is fine. However, when scaling-down we want to automatically remove the machines AD Account from the domain. I don't see a way to execute a "before or after" event in Azure auto-scaling. The current prescription is to override the roles OnStop event. However, there is no way to tell if it is a simple reboot or an actual de-allocation.

    We should be able to explicitly define & execute a separate set of code…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    Is this code that you’d want to define inside your role, or, code that you’d want to define in the autoscale setting?

  7. Performance Query Widgets on Dashboard get reset on new load

    The Query-Settings for the Dashboard widgets partly reset on reopening the dashboard. Some have extra plots added, others have less, and even others have a different time range set than before. Exactly which setting is reset is always the same on each widget.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. do not loose the usage overview

    The existing usage overview (6 horizontal bars, with reset timing) is easy to understand and absorb at a quick glance.
    (a) there is nothing like this in the new version.
    (b) if the 'third' panel (website detail) is off screen when the user selects a different website, there is no indication that the new data is available.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Prevent the immediate deallocation of scalled virtual machines when manually starting

    I have a series of Virtual Machines in a cloud instance which switch on or off based on CPU usage.

    Sometimes I want to manually start all virtual machines to apply some configuration changes.

    Unfortunately the auto scaling causes the machines to be immediately switch back off. I have tried setting the "Scale down wait time" to 60 minutes but this setting is ignored if you manually start the machines.

    The only work around at the moment:

    1) Turn off scaling.
    2) Start all virtual machines and apply configurations
    3) Re-configure scaling settings.

    I suggest you should honor the "Scale…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    So to be clear, you’re suggesting that the cooldown period should be based on any scaling action, not just an autoscaling action? This seems like a reasonable change.

  10. Better notifications of services that fail to start at deployement

    Azure gives notifications in the portal is a Cloud Service cannot be reached by the Host or if the deployment fails. It would be nice to have notification if a service fails to start. Note there maybe failed services starts even if the webrole or worker roll starts. For example, the Windows Time service maybe set to auto start, but it failed to start.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add an Alert Rule so that notification can occur as soon as a web service Web Services DIAGNOSTICS CONNECTION STRINGS response fails

    Add an Alert Rule so that notification can occur as soon as a web service Web Services DIAGNOSTICS CONNECTION STRINGS response fails. Currently it only Alerts on Uptime and Response Times which are averaged over a minimum of 15 minutes.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Windows azure diagnostics

    Windows Azure should provide an API to directly read WAD log files generated on Local Storage without having to transfer them on Azure storage

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Being able to read the logs locally without waiting for them to be pushed to storage makes sense — it would potentially reduce lag in getting information. I will pass this feedback to the WAD team.

  13. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Scale page > instances graph is incorrect after using "Specific Dates" feature

    As a test, I used the "Specific Dates" feature yesterday to scale up the # of instances for a web role from 1 -> 10 for just 2 hours. The role scaled back down to 1 instance after that interval. However, today the graph shows the historical # of instances pegged at 10 for the previous 5 days, which is incorrect. See attached image.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Diagnostics and Monitoring

Categories

Feedback and Knowledge Base