Bugs, corrupt data or performance issues on web applications are often recognized far too late. In the worst case they are reported by the customer, so they probably have already done some serious damage - frustrated the user, made them lose trust or even corrupted their data. Finding these bugs or recognizing them early gets especially hard, if your application makes heavy use of background processes, daemons or cronjobs. They might even throw exceptions that are buried somewhere in the logs, and no one will ever be aware of them, until someone has a look into the log files. I want to show a way out of this misery and provide different solutions in form of practical examples. These will include different levels of monitoring - from simple text logs on the servers up to a fully monitored application including hardware monitoring, extensive metrics, indexed and searchable logs of the whole environment, performance analysis and alerts if something odd happens. I'll show different examples and give ideas when such a fully monitored solution is a good idea, or when a "light monitoring" is applicable. Plus d'informations sur cette conférence : https://afup.org/talks/2048-monitoring-applications-evolve-from-text-logs-to-extensive-automatic-monitoring Cette vidéo vous a plu ? Adhérez à l'AFUP pour soutenir son activité : https://afup.org/pages/site/?route=vie-associative/56/devenir-membre Nous cherchons des sponsors et des conférenciers pour le prochain événement AFUP : https://event.afup.org/ Captation & montage : http://www.dfusion.fr/