PHPackages raccoondepot/error-log - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Logging & Monitoring](/categories/logging) 4. / 5. raccoondepot/error-log ActiveTypo3-cms-extension[Logging & Monitoring](/categories/logging) raccoondepot/error-log ====================== This TYPO3 extension manages errors and exceptions, even before TYPO3 fully loads. It groups and displays errors in the backend, with detailed information and stack traces. Configurable notifications and reports via email and Slack keep you informed, while AI assistance aids in resolving issues. 12.4.8(1y ago)155884[9 issues](https://github.com/raccoondepot/error_log/issues)GPL-2.0-or-laterPHP Since Jun 26Pushed 1y ago2 watchersCompare [ Source](https://github.com/raccoondepot/error_log)[ Packagist](https://packagist.org/packages/raccoondepot/error-log)[ Docs](https://github.com/raccoondepot/error_log/)[ RSS](/packages/raccoondepot-error-log/feed)WikiDiscussions main Synced 1mo ago READMEChangelog (10)Dependencies (5)Versions (17)Used By (0) [![ErrorLog](https://camo.githubusercontent.com/0d5574c0843aeb5ae464096ede3943d150a7a45ed69b8998e9e49b290bd97f11/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f626574612d7631322e342e362d677265656e)](https://github.com/raccoondepot/error_log/tree/12.4.6) [![TYPO3 12](https://camo.githubusercontent.com/08afacc49187e63c796f7d1c4401d0f0563bab574d9c525312b2827acb09a7c5/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f5459504f332d31322d6f72616e67652e737667)](https://get.typo3.org/version/12) ![License](https://camo.githubusercontent.com/c23bc14300582c1ecb9234f2a1c386a5f8d17e4c32cb00ae87a39b3edcec7155/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f6c6963656e73652f5459504f332d446f63756d656e746174696f6e2f746561) [![RD](https://camo.githubusercontent.com/4b07e511f1dd8a10c90b8275a2785566c9719bbf0db80ba833c1a6f5ba7a57a9/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f526163636f6f6e2d4465706f742d353062393961)](https://raccoondepot.com) [![StandWithUkraine](https://raw.githubusercontent.com/vshymanskyy/StandWithUkraine/main/badges/StandWithUkraine.svg)](https://stand-with-ukraine.pp.ua/) TYPO3 Advanced Error Log ======================== [](#typo3-advanced-error-log) [![Stand With Ukraine](https://raw.githubusercontent.com/vshymanskyy/StandWithUkraine/main/banner-direct-team.svg)](https://stand-with-ukraine.pp.ua) Features -------- [](#features) - Handle TYPO3 errors and content object exceptions - Handle the errors occurred before TYPO3 is fully loaded - Display grouped errors in the TYPO3 backend module - Provide detailed information for each error occurrence, including stack traces - Configurable error notifications via email and Slack - Configurable combined error reports via email and Slack - AI assistance for error resolution Requirements ------------ [](#requirements) Basic requirements are the same as for the TYPO3 version it used with, however some adjustments in php.ini might be needed to collect arguments for error stack trace. Starting from `PHP v7.4`, a new ini directive `zend.exception_ignore_args` with default value `On` was added. As result, there are no arguments collected with default PHP setup. It should be changed to `zend.exception_ignore_args = Off`. Installation ------------ [](#installation) You can install Advanced error log with ``` composer require raccoondepot/error-log ``` After the extension is installed, the Upgrade Wizard rewrites the project's LocalConfiguration file with a setup for our exception handlers. Configuration ------------- [](#configuration) Most of the settings are available over *Settings* action in module. It consists of two tabs - `Settings` and `Users`. In the Settings tab there are three sections - `General` - , `Slack` and `OpenAI`, which help you to configure corresponding features. Each section starts with a checkbox which enables the current part of the setup. Users tab shows the list of users who enabled the email notification. [![](https://camo.githubusercontent.com/2a3d1a82df5506eaeba4291233c57b91e43954021413d3b2bc59b05eaa1e87c4/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f302e6a7067)](https://camo.githubusercontent.com/2a3d1a82df5506eaeba4291233c57b91e43954021413d3b2bc59b05eaa1e87c4/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f302e6a7067) ### General [](#general) With the `Enable Error log feature` checkbox you can disable/enable the logging. It writes changes to LocalConfiguration the same way as the Upgrade Wizard does. Field `Number of days before error expires` is responsible for error log database cleanup. It says when we need to remove the outdated records. The default value `0` means that error records are not deleting. ### Slack [](#slack) To use Slack we need to enable it with a corresponding checkbox (`Enable Slack notifications`). To send notifications over Slack, a Slack application should be created first. The process of creating one is described on [Slack tutorial page](https://api.slack.com/tutorials/tracks/actionable-notifications). When the application is ready, you should add its authorization token and a channel ID where the notifications will be sent. Channel ID could be seen on the bottom of the Channel details popup. Fields `Slack authorization token` and `Slack channel ID` should be filled with these values. There's a `Send test message` button to check if the application is configured correctly. Next step is to configure the notifications for error occurrences and reports. This could be done with `Error reports sending` and `Error occurrence notification sending` dropdowns. If configured correctly, Slack notifications will appear as follows:: [![](https://camo.githubusercontent.com/c3eeee29c5d0971c2083883fee69994c409ca87ae3a96be2d91f1947ce208b9a/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f312e6a7067)](https://camo.githubusercontent.com/c3eeee29c5d0971c2083883fee69994c409ca87ae3a96be2d91f1947ce208b9a/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f312e6a7067) ### OpenAI [](#openai) OpenAI API is used to get the suggestions about error cause and resolving. To use OpenAI API, authorization token should be obtained from [OpenAI](https://platform.openai.com/) and entered into the `OpenAI authorization token` field. In the `OpenAI system pre-prompt` field it is possible to adjust the initial instruction to LLM. Dropdown `OpenAI GPT model` gives you a possibility to select which model to use. gpt-3.5-turbo is the cheapest and gpt-4-turbo is the smartest one, but a bit slower and the most expensive. In the bottom of the OpenAI section there's a `Test AI` button to check if everything is configured properly. ### Email notifications [](#email-notifications) There's no configuration for email notifications in extension's module. They are configuring separately for each user (if needed), so these options could be found in either User settings or Backend users module (user editing is also available from *Users* tab of our extension's Settings action). In both User settings and Backend users there's a new tab *Error Notifications* added. Here you can find a configuration, similar to the one used for Slack - `Enable email notifications` checkbox and two dropdowns: `Error reports sending` and `Error occurrence notification sending`. To make it work, the user email field should also be filled in user settings. If everything is configured, users will receive the emails like this: [![](https://camo.githubusercontent.com/0410907938540a5be2950430e40627c625a9c2704835898cabb4546ec0c962c0/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f322e6a7067)](https://camo.githubusercontent.com/0410907938540a5be2950430e40627c625a9c2704835898cabb4546ec0c962c0/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f322e6a7067) ### Scheduler task [](#scheduler-task) Our extension uses a scheduler task *Error log service manager task*. It is used for sending reports, process errors which weren't properly dispatched (those that appeared earlier than TYPO3 was fully loaded) and cleans the database up. It should be enough to execute it once or twice per hour. ### Content object exceptions [](#content-object-exceptions) By default we override the native content object exception handler to write content object errors details into our log, but the rest of its behavior is the same (*Oops, an error occurred* message in the section which couldn't be rendered). If you want to see the error details on the page, you should turn off this handler over typoscript: ``` config.contentObjectExceptionHandler = 0 ``` As result the error details will be displayed on page, but they still will be logged with our extension Main functionality description ------------------------------ [](#main-functionality-description) The main part of our extension is the `Error log` module which is placed in the `System` section of the TYPO3 backend. The main view shows the filtered list of grouped errors: [![](https://camo.githubusercontent.com/8e11f7f7bb208024ca826bada428ded49b5f1b41c8e3f7d2e5e3fd49c83f0e76/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f332e6a7067)](https://camo.githubusercontent.com/8e11f7f7bb208024ca826bada428ded49b5f1b41c8e3f7d2e5e3fd49c83f0e76/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f332e6a7067) You can click on any error group to see the list of all the errors in this group: [![](https://camo.githubusercontent.com/c5984aa26d9059e1dd76c21dbad84511faf32c651ade79f8efef23496178c049/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f342e6a7067)](https://camo.githubusercontent.com/c5984aa26d9059e1dd76c21dbad84511faf32c651ade79f8efef23496178c049/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f342e6a7067) Each individual error in the list could be expanded with detailed information about it. Here you can see a table with details like entry point, browser information, IP, etc. and a full stack trace with arguments: [![](https://camo.githubusercontent.com/b4c3155a984fbb39aef91f321d6db6ed571993aeb407e0755564fac25c160ade/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f352e6a7067)](https://camo.githubusercontent.com/b4c3155a984fbb39aef91f321d6db6ed571993aeb407e0755564fac25c160ade/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f352e6a7067) If OpenAI is configured there will also be a tab `AI Assistant` with a prompt based on error details ready to be executed. It is also possible to modify the prompt if needed. Request from AI will be rendered below the textarea with prompt: [![](https://camo.githubusercontent.com/32bea2ac7d4ee51fdcfa52b08bf5d783c0dfb71e32331d23ae7ffbfbdd52cfba/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f362e6a7067)](https://camo.githubusercontent.com/32bea2ac7d4ee51fdcfa52b08bf5d783c0dfb71e32331d23ae7ffbfbdd52cfba/68747470733a2f2f63702d6465762e726163636f6f6e6465706f742e636f6d2f696d67732f656c5f362e6a7067) Events and features extending ----------------------------- [](#events-and-features-extending) In our extension we dispatching two events: EventDescriptionParametersErrorEventTriggered when either error occurred or when non-dispatched error found during scheduler task execution.$error, $isFirstOccurrenceReportEventHappens when it's time to render a report for user email or Slack.$frequency, $errorsYou can easily add your own listener to any of those events and perform your own actions when it is dispatched. Future plans ------------ [](#future-plans) This extension is a work in progress and we have a lot of ideas to implement in future versions. Here are some of them: - Handle errors from PHP error log file (either directly or with directly uploaded file); - Dynamic configuration for alternative notification sources; - Use retrieval augmented generation (RAG) for giving AI better TYPO3 context. ### Health Score 30 — LowBetter than 64% of packages Maintenance26 Infrequent updates — may be unmaintained Popularity24 Limited adoption so far Community16 Small or concentrated contributor base Maturity48 Maturing project, gaining track record Bus Factor1 Top contributor holds 53.5% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~7 days Total 14 Last Release 592d ago Major Versions 11.5.0 → 12.4.02024-06-28 11.5.1 → 12.4.22024-07-29 11.5.2 → 12.4.32024-08-08 11.5.4 → 12.4.52024-08-09 ### Community Maintainers ![](https://www.gravatar.com/avatar/7a296927ec1bb7eec87a0e45b6bc6fca2aeb280eebe23d40e9e214d5b0b9c1e7?d=identicon)[bobrius](/maintainers/bobrius) ![](https://www.gravatar.com/avatar/a1e9f8cba79c486b0205103d9cdfaaf726be7de0877859a21f9f87f6ec5b27e0?d=identicon)[raccoondepot](/maintainers/raccoondepot) --- Top Contributors [![Voronov](https://avatars.githubusercontent.com/u/3194685?v=4)](https://github.com/Voronov "Voronov (23 commits)")[![bobriusNT](https://avatars.githubusercontent.com/u/18287635?v=4)](https://github.com/bobriusNT "bobriusNT (16 commits)")[![raccoondepot-git](https://avatars.githubusercontent.com/u/173937629?v=4)](https://github.com/raccoondepot-git "raccoondepot-git (2 commits)")[![rosty-matviiv](https://avatars.githubusercontent.com/u/50489886?v=4)](https://github.com/rosty-matviiv "rosty-matviiv (2 commits)") --- Tags TYPO3 CMS ### Embed Badge ![Health badge](/badges/raccoondepot-error-log/health.svg) ``` [![Health](https://phpackages.com/badges/raccoondepot-error-log/health.svg)](https://phpackages.com/packages/raccoondepot-error-log) ``` ### Alternatives [fluidtypo3/vhs This is a collection of ViewHelpers for performing rendering tasks that are not natively provided by TYPO3's Fluid templating engine. 1954.1M48](/packages/fluidtypo3-vhs)[apache-solr-for-typo3/solr Apache Solr for TYPO3 - Apache Solr for TYPO3 is the enterprise search server you were looking for with special features such as Faceted Search or Synonym Support and incredibly fast response times of results within milliseconds. 1473.0M32](/packages/apache-solr-for-typo3-solr)[t3monitor/t3monitoring_client Client extension for the t3monitoring service 31851.3k1](/packages/t3monitor-t3monitoring-client)[derhansen/sf_event_mgt Configurable event management and registration extension based on ExtBase and Fluid 64313.9k6](/packages/derhansen-sf-event-mgt)[pagemachine/typo3-formlog Form log for TYPO3 23225.3k6](/packages/pagemachine-typo3-formlog)[brotkrueml/schema Embedding schema.org vocabulary - API and view helpers for schema.org markup 33584.6k13](/packages/brotkrueml-schema) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)