Closed giohappy closed 6 years ago
As an app, it can be enabled by default, but there's also monitoring configuration part, which should be processed in ui by user.
Alternatively, there's autoconfigure code which should populate configuration based on settings (it's not very well tested though, just basic case), which should populate hosts and services. I can add MONITORING_AUTOCONFIGURE
flag to settings, which will enable autoconf on deployment (when no host/service is defined), or just hardcode autoconfigure in geonode-generic.
I would be in favour of autonfiguring it.
Monitoring requires collector script to be run each minute. This can be done by cron task, or we can add it to uwsgi scheduler: http://uwsgi-docs.readthedocs.io/en/latest/Cron.html
I would use a dedicated container for scheduled tasks (cron). It could be used both for monitoring and for scheduled backups. Don't you think?
monitoring models setup defined in https://github.com/geosolutions-it/geonode-generic/commit/a95e94082c9e7
There was a misconfiguration causing no data were collected, i've added proper host name generation in settings for this.
GeoNode monitoring must be enabled by default. It's a key element for the typical user, who wants to have reports on numners of users, data downloads, etc.
see #11 for scheduling implementation