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

[Søren Malling]

Hi Martin,

Thanks for your input.

Our usecase is not isolated to changes in TypoScript, but also in
flexforms, HTML files, css files etc.

But your idea made me think, and I hope you will give some feedback on
this thought as well:

Create a caretaker services, getting rows from the sys_log table on a
TYPO3 instance. On the instance, you can have a log extension, where
you "reserves" your own type for the "type" field in sys_log. In the
caretaker service configuration, your can configure what levels of
sys_log entries you would like to have it return.

Am I still moving at a spot, where caretaker isn't ment to go?

Best regards,

Søren Malling

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



On Mon, Nov 29, 2010 at 7:07 PM, Martin Ficzel <martin.ficzel at gmx.de> wrote:
> Am 29.11.10 15:52, schrieb 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.
>
>
> Hi Søren,
>
> since caretaker does not aggregate and browse logs i would suggest a little
> different approach. Maybe that fits your needs aswell.
>
> Add a test like "Typoscript was not modified in the last 24 hours" that
> fetches the needed informations from the ts and syslog tables and writes the
> apropriate messages. In the result an instance with modified ts would go to
> warning (or error) state for 24 hours.
>
> With this aproach you would have the aggregated changes in the caretaker
> testresult log without modifying the caretaker core-infrastructure. You just
> have to add a new testservice that can rely on the existing
> instance_operations as you intended.
>
> Would that solve your problems?
>
> Regards Martin
>
>
>> 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
>
> _______________________________________________
> TYPO3-project-caretaker mailing list
> TYPO3-project-caretaker at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-caretaker
>