How does it work?¶
Let's go behind the scenes to give you an idea how the caretaker works: There is a caretaker server on the one hand and several instances on the other.
The instances are the TYPO3 installations you want to observe. The server is a TYPO3 installation offering the monitoring of connected instances. This monitoring process always works in the same way: The caretaker server performs tests (which you define) against the instances. This is realized by sending requests to the instance on an encrypted connection. The instance itself is stupid. It just answers this requests back to the caretaker server. There the caretaker proves the status of the result:
- Ok: everything fine
- Warning: something is not ok
- Failed: The result doesn't comply with the test-specifications.
If configured, it sends Mail-notifications to a caretaker administrator by email, if a test fails.
NOTICE: Even when correctly configured, e-mail notifications and all other notifications will only be issued if the result of a test changes. So if one of your tests starts to fail you will get a notification. But for every subsequent caretaker run you wont be notified unless the result of the test changes to "OK" again.
Each TYPO3 installation you want to monitor, needs to have the extension caretaker_instance installed and activated. For the serversided setup both extensions, caretaker AND caretaker_instance, need to be installed and activated.
@TODO :: Add some notes & Screenshots about the Frontend here
Video: set up a new instance of caretaker
Video: set up a new ping test