Best practice to monitor an application

[Skins]

I have an application which consists of (all running on one server as a test)

The app running as an exe
webserver
php
mysql

I'd like to build a dashboard and monitor the application so i can eventually push this out on a bigger scale - i'd like to monitor ..
(I have installed UF on box)

all key running services :

webserver, application, mysql - and trigger an alert if any of these fall over (service stopped).

I can monitor the apache, mysql, php logs etc - (although not sure how i can simulate some errors as theres not much in the logs currently)

Anything else i should add to my dashboard ? - ah env stats - cpu, mem, disk space anything else ?

gratzi.

[felipecerda]

Hi,

You should also monitor the operation of your application. You'd want to send logs of the backed interactions when the users are flowing through your application.
Say users have to go through different steps when using the application, it'd be a good practice to measure the effectiveness of each of those steps, as well as the volume of users, so you can detect breaks in the usual behavior of the application.

Good luck