[TYPO3-caretaker] Syslog on each installation to be fetched into caretaker server

[Søren Malling]

Hi,

I have the following proposal for a caretaker service:

On each TYPO3 installation, a admin user got the possibility to add a
note (syslog) if they change something. Example:

Developer A logs in, and changes a TypoScript setting in extension
xyz. Write a note in a log module and logs out.
Next day, extension xyz stopped working and Developer B wonders why.
He logs in to the central caretaker installation and find the syslog
for that specific installation.
Here he can see that Developer A wrote the following note "Changed
option A to 3 instead of 2"
That just saved Developer B from logging in to the backend, finding
the Log module and reading through a lot of log entries.

We are planning such caretaker service at work, but would like some
help/knowledge on the following:

By looking at tx_caretakerinstance_BackendUserTestService I've found a
way to get data out of existing tables on a remote destination.

It includes the RemoteTestServiceBase class from caretaker_instance,
will it be safe/okay/correct to depend my own service on that specific
class?

What about tables for the syslog entries on each installation, should
they be in the same extension installed on the caretaker server? (the
one providing the service) Or will it be a separate extension?

Hope to hear some best advice on this topic.

Thanks in advance!

Regards,

Søren Malling

TYPO3 Brugergruppe Danmark: www.typo3danmark.dk
Twitter: twitter.com/sorenmalling