Lets say you run a simple web app, everything is going fine and number of clients are always going up. You know you will need a new server soon - but not quite sure when. Of course you wouldn't want to hear complaint from a customer saying "Your app is soooo slow.. I'm switching to your competitor", before you decide its time to upgrade to a new server or install a new slave. So my question is, what factors and metrics to monitor and keep eye on as a sysadmin? I know this is a wide-topic but I'm looking for top factors/metrics to monitor limited to a simple PHP/MySQL web app.
Tell me more
×
Server Fault is a question and answer site for
professional system and network administrators. It's 100% free, no registration required.
|
|
closed as not a real question by womble, Chris S♦ May 2 '12 at 12:25
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, see the FAQ.
|
Clearly, the response time. You can run any monitoring tool like nagios and graph this value. When the response time exceeds the acceptable range, you need to start optimizing your servers. When no more optimization can be done, you can start adding more resources and even more machines. |
|||
|
First of all make a range of what is normal, tresshold (slower but still ok) and Red zone (too slow). Define this for yourself. Start to run tests to see what your response time is during peek times/normal times/slow times. Once you reach your tresshold it's time to invest in a new machine. Also when you keep track of this in with some nice statistic schemes for a longer period of time you might notice a growth curve and you can start predicting when you will need a new machine. |
|||
|
|
