Monitoring and Logging best practices
!Friendica Support Hi! Now that I have both a NAT ingress router and a pfsense reverse proxy in front of my Friendica instance and the whole thing in a DMZ separate from my work, I feel confident that I could allow other users onto my instance. But before I can do that, I need to be sure that I can support the system when problems occur without having to spend too much time. What interests me in this connection is if there are any good monitoring practices and solutions - scripts or web views or the like - that would alert me about any abnormal conditions such as errors in the log files, sharp traffic increases, overload siutations and the like. Also a todo list of things to check manually once in a while maybe. Oh and automated backup of the configuration (including user accounts and their contributions) of course! I want to be a responsible admin
.

Friendica Support reshared this.
Michael 🇺🇦
in reply to Tobias Ernst • • •We have got an endpoint that can be called by external monitoring services like Zabbix. There you have a lot of data, like the number of unprocessed tasks, worker jobs per minute, date of the last cron execution and a lot more. With some rules you should be able to react early, when the system would had a hiccup.
See here: friendica.tf-translate.net/hel…
Tobias Ernst likes this.