Anonymous

My feedback

  1. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  2. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  (General Feedback) » Offers  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  3. 604 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    Any status on this?

    Today's advanced web apps such as those using React and Babel/Webpack that depend on running scripts on deploy such as those that transcompile JSX code to plain javascript. Thus there is a period when a new instance is spun up but not ready to accept traffic yet.

    Your LB Probes should at least see if response to / is 200. Even better is a custom URL such as /health or /probe.

    This seems like a showstopper issue for those that want high level of 9's for uptime for someone running even a basic React app!

    In general, this seems like the typical case where Azure is focusing on extra useless bells and whistles like Tinfoil security and new performance testing features I see rather than basic functionality. I can always revert to using third party solutions from Sumo Logic, loader.io, etc, but there is no way for me to change your basic LB behavior!

Feedback and Knowledge Base