Logging and Monitoring

[cultpony]

Is your feature request related to a problem? Please describe.

At the moment, administration is after-the-fact and sort of blind, sifting through logfiles. We should establish a central solution to ingest and analyze logs from webservers and applications running on the philo deployment.

Describe the solution you'd like

• Nginx Weblog Analytics (e.g. GoAccess, this also helps in monitoring how the site is used, what user agents are popular and what users are causing undue load)
• Philo Log Ingest/Storage (Store Logs from Philo for X days, in case we need analysis of past events)
• Error/Incident System (Stack Traces ought to be stored along with context for analysis so we can fix bugs)
• Performance Monitoring (over all components, including docker, possibly InfluxDB or Postgres for storage)

I would advice against the ELK stack, it's heavy and would require 3-node setups to run cleanly.