Debugging

At some point any admin may stumble on the need to see if something has been done, when and by who. Flying Fleet offers a few ways to get some more intel.

Member History

In the member details (Administrator => Members), on the right side, a collapsible section called "Last Actions" allows to quickly check what did a given member did and when. This list doesn't contain the full list of actions nor all the information stored by the software but could offer a quick view to check if somebody did something.

Action Log

"System" => "Action Log" offers a view of the last 5000 actions logged by the system. Keep in mind that the action log is cleaned after 60 days (to reduce the database size).

The action log contains the IP of who triggered the action, the member, the date and the type of action done. Most actions do have additional info.

Notification Pool

Every notification (email or web notification) sent by the system goes through the notification pool ("System" => "Notifications Pool"). The pool can be stopped for a period of time, to catch all notifications as well as browse sent notifications.

If a user doesn't receive an email, yet the system has a copy of the email in the sent notifications, this can mean only 2 things:

• The email sending address is wrongly configured (can be checked using the "System" => "Diagnostic" page) or
• The email has been correctly been sent, but the filtered by some spam filter. Some system simply delete emails and do not even place them in the spam folder.

Diagnostic

The diagnostic page ("System" => "Diagnostic") allows to have a real-time view of the status of the system. Showing the memory / CPU usage in a graph on top. The last errors triggered by the system, slow pages, system information and finally a tool to debug emails.