So now we have our website and our blog running.
But we've promoted that across the internet and it's become
more popular, and suddenly we're seeing really big spikes and traffic.
So, how do we go ahead and have Azure automatically
scale up our instances of both our website and our blog?
So the first thing I want to show. Is the Monitor tab.
You'll see under here we have our CPU Time, Data In, Data Out and Requests.
If I hit Add Metrics, one of the really tell-tale signs
that your website's under a lot of stress is 404 errors.
You begin to start really timing out on everything.
So, we're going to go ahead and add that.
And let's just go ahead and pretend that this
number is just being blown out of the water.
And we want the ability to go head and start to deal with that, so
we need to come under configure and we need to make sure that our application
logging is turned on.
So if I go head and turn this on and my
web server logging and we save that, when I go ahead
back to our FDP client you'll notice that I'm going to
have logs that are going to be written to the root.
So if we come over here And we move up
(SOUND)
to log files.
All of those log files will start being dumped
down here, so you're going to be able to get
all sorts of information from both IIS and the
website, or if you are using word press and mySQL.
You're going to see everything get written there.
Now, we've got the log files running.
We've got all of the metrics set up for our monitoring And we've
decided that we need to go ahead and grow this website, or this blog.
So we've got a couple
options here.
The first option is I can come under here and I can increase the instances directly.
So you'll see maybe I want 2 instances.
In the free tier, you're noticing I'm locked to that
instance, but if I move to the shared tier I
can go ahead and move this up, you can see I can move this all the way up to 6.
Instances.
And so if I was to say, put me into
a shared model, and this happens to be what I'm running
my own blog in, with 2 instances and hit save, you'll notice that the blog is
going to be affected, and we're changing a mode, so this might affect our bill.
Currently we're in the free tier, when I move to
the new tier I have the possibility of being charged.
We're going to go ahead and say yes.
And you can look at your bill at any time.
So, previously in this course, we went to the top right and you
saw the bill, which is where we started out with.
If I go ahead and I say view my bill now
and I enter my password, we're going to use our free trial.
And you'll notice everything right here.
So, my website is going to start to show here.
You're going to see how far across we've been and you
can see right now, my monthly credit, I haven't used anything.
So don't be afraid when you're moving from free to shared in your trial account.
It's really easy to go ahead and check out the bigger capabilities.
And then you can see how close you are
to running out of your max on your credits there.
Let's go ahead and move back to the portal, and we're
going to click on websites, we're going to go back to our blog.
And, we also have something new, that's under preview currently.
Preview means there's no guaranteed SLA, like there is with
general availability.
But it is available for production websites
today if you want to check it out.
If I click on standard, what you're going to see happen here, is I
have the ability to turn this on for my blog or by university.
Now, I'm going to go ahead and keep select all running.
And I can go down to autoscale, and I could set the CPU.
So, I could say.
For the CPU,
if I"m running between 70-85% CPU power
consistently, then I want you, you can see we've got small, medium, and large.
So, I've got small, medium and large.
I currently have one instance running.
I could do this.
And what you'll notice here is this is
going to set the minimum and maximum number of machines.
So you are not going to move past these limits.
Azure is going to scale down as well as up.
So, if that CPU target drops below 70, for example, may
be it's during the night or it's the off peak hours.
It'll actually shut down these additional instances for me.
And then it will spin them up, up to a maximum of
6, when it starts to see the CPU between that target CPU.
This is an incredibly powerful
feature and I think this is a feature for web sites,
in particular, that's going to save you a lot of money over time.
I know in my own blog, there are periods where there are
simply no requests hitting that blog, and then there are other periods where
there are a ton of requests hitting that But you have that
skill and that capability to set
everything directly here in the azure portal.