PHPackages t3monitor/t3monitoring - 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. t3monitor/t3monitoring ActiveTypo3-cms-extension[Logging & Monitoring](/categories/logging) t3monitor/t3monitoring ====================== T3monitoring service 3.1.0(5mo ago)5415.5k↓47.7%35[2 issues](https://github.com/georgringer/t3monitoring/issues)[7 PRs](https://github.com/georgringer/t3monitoring/pulls)1GPL-2.0-or-laterPHPPHP ^8.2 Since Mar 20Pushed 5mo ago8 watchersCompare [ Source](https://github.com/georgringer/t3monitoring)[ Packagist](https://packagist.org/packages/t3monitor/t3monitoring)[ Fund](https://paypal.me/GeorgRinger/10)[ Fund](https://www.amazon.de/hz/wishlist/ls/8F573K08TSDG)[ RSS](/packages/t3monitor-t3monitoring/feed)WikiDiscussions master Synced 1mo ago READMEChangelog (4)Dependencies (6)Versions (12)Used By (1) TYPO3 CMS Extension "t3monitoring" ================================== [](#typo3-cms-extension-t3monitoring) This extensions provides the possibility to monitor all of your TYPO3 installations and shows you - used TYPO3 version and if it is up to date - available TYPO3 extensions and if those are installed, insecure or if there are bugfix, minor or major updates - additional information like PHP & Mysql versions. **Requirements** - At least TYPO3 CMS 12 LTS (monitoring works also for 6.2 installations) - The host must have access to every client to be able to fetch the data **Pricing** This extension is completely free to use! However maintaining an extension takes an enormous amount of time. Therefore I am using a concept which is based on your trust! If you use this extension to monitor your clients, please consider to pay (once): - € 150 for less than 20 clients - € 350 for less than 100 clients - € 500 for more than 100 clients Please contact me via email () or slack for questions and to receive an invoice! Screenshots ----------- [](#screenshots) **Overview** [![Overview including most important information](Documentation/images/t3monitoring_index.png)](Documentation/images/t3monitoring_index.png) **Search result** [![Search result](Documentation/images/t3monitoring-search.png)](Documentation/images/t3monitoring-search.png) **Single view of a client** [![Client](Documentation/images/t3monitoring-client.png)](Documentation/images/t3monitoring-client.png) **List of all used extensions** [![Extensions](Documentation/images/t3monitoring-extensions.png)](Documentation/images/t3monitoring-extensions.png) ### How to start [](#how-to-start) Before you can actually monitor any installation, you need to install the extension *t3monitoring\_client* on every installation (called "client"). This extension provides the data which will be fetched by the master installation. Install this extension via [:composer:`t3monitor/t3monitoring\_client`](#id1) or from [:t3ext:`t3monitoring\_client`](#id3). Important Please secure the installation as much as possible, as it contains data of all your clients. Restrict access by running it in your intranet only, or at least use a *Basic HTTP Authentication*. #### Create the clients [](#create-the-clients) Create a record "**Client**" on any sys folder and fill out at least the following required fields: - Title - Domain. Include `http://` or `https://`. - Secret: This is the same secret as defined in the configuration of *t3monitoring\_client* in the client installation. Please don't reuse any secrets twice. - (Optional) BasicAuth username and password: (if your client is secured via HTTP Basic Auth) - (Optional) Host Header: (if you want to monitor a client which can't be resolved via public DNS services) ( - (Optional) Ignore Certificate Errors: Ignores certificate errors (mostly necessary if you use the previous field "Host Header" in conjunction with Let's Encrypt) - (Optional) Force IP Resolve: IPv4 or IPv6 Create an optional record "**SLA**" to group your clients. Examples could be: - VIP: Do all updates ASAP - First ask: Before doing any updates, ask client for proper time schedule #### Import the data [](#import-the-data) To be able to deliver proper results, this extensions requires information about all core versions and all extensions. This information is provided by . To import the data, use the command line: ``` vendor/bin/typo3 monitoring:importAll ``` You can add this call also as task in the scheduler extension. Especially the import of extensions can take a while, therefore you can use different calls for all required imports: - `vendor/bin/typo3 monitoring:importCore` to fetch latest core versions - `vendor/bin/typo3 monitoring:importExtensions` to fetch the extensions - `vendor/bin/typo3 monitoring:importClients` to fetch the client data ### Notifications [](#notifications) t3monitoring contains various notifications. #### Failed to fetch client info [](#failed-to-fetch-client-info) This notification sends an email, if a clients information (provided by the extension "t3monitoring\_client") cannot be accessed/fetched. You may configure the email recipient in the "Extension Configuration" of the t3monitoring extension using the setting "records.emailForFailedClient". The notification is send by the Symfony Console Command **"monitoring:importClients"** and consists of a single email which contains a list of all failing clients. The frequency of the notification email depends on your scheduled task for importing the clients. The "Extension Configuration" also contains a option "records.emailAllowedAmountOfFailures". This value provides the ability to only send the notification email, if a client fails multiple times in a row. #### Client report [](#client-report) Another possible notification is the "Client report". It is represented by the Symfony Console Command **"reporting:client"**. It generates an email for each client and uses the clients email property ("email") as recipient address. If there is no email set, its not possible to send a notification. If t3monitoring identifies security problems, an outdated core or additional error messages the notification is sent. If the client does not break with these regulations, no email is sent. The frequency is again defined by the according scheduled task. #### Admin report [](#admin-report) Last but not least, the "Admin report" (Symfony Console Command: **reporting:admin**) generates a single email with all problematic clients and sends it. The recipients email address needs to be configured as argument of the Symfony Console Command (respective the scheduled task). The frequency of the sent notification is also defined by the occurrence of the scheduled task. ### Health Score 59 — FairBetter than 99% of packages Maintenance70 Regular maintenance activity Popularity40 Moderate usage in the ecosystem Community31 Small or concentrated contributor base Maturity82 Battle-tested with a long release history Bus Factor1 Top contributor holds 55.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 ~354 days Recently: every ~207 days Total 11 Last Release 170d ago Major Versions 0.0.3 → 1.0.02016-05-19 1.0.1 → 2.0.02018-01-11 2.0.1 → 3.0.x-dev2023-08-23 ### Community Maintainers ![](https://www.gravatar.com/avatar/1d08c176686c8914d32c70d4af388887d738930fdfdf07c7ca9c841ad10ed683?d=identicon)[georgringer](/maintainers/georgringer) --- Top Contributors [![georgringer](https://avatars.githubusercontent.com/u/1905663?v=4)](https://github.com/georgringer "georgringer (151 commits)")[![liayn](https://avatars.githubusercontent.com/u/222377?v=4)](https://github.com/liayn "liayn (29 commits)")[![josefglatz](https://avatars.githubusercontent.com/u/2861556?v=4)](https://github.com/josefglatz "josefglatz (17 commits)")[![wouter90](https://avatars.githubusercontent.com/u/1637330?v=4)](https://github.com/wouter90 "wouter90 (9 commits)")[![davidjakob](https://avatars.githubusercontent.com/u/4965254?v=4)](https://github.com/davidjakob "davidjakob (8 commits)")[![andyhirsch](https://avatars.githubusercontent.com/u/14921186?v=4)](https://github.com/andyhirsch "andyhirsch (7 commits)")[![koehnlein](https://avatars.githubusercontent.com/u/16088567?v=4)](https://github.com/koehnlein "koehnlein (6 commits)")[![NeoBlack](https://avatars.githubusercontent.com/u/1128085?v=4)](https://github.com/NeoBlack "NeoBlack (5 commits)")[![frans-beech-it](https://avatars.githubusercontent.com/u/4436635?v=4)](https://github.com/frans-beech-it "frans-beech-it (4 commits)")[![DanielRuf](https://avatars.githubusercontent.com/u/827205?v=4)](https://github.com/DanielRuf "DanielRuf (4 commits)")[![peterkraume](https://avatars.githubusercontent.com/u/4234704?v=4)](https://github.com/peterkraume "peterkraume (4 commits)")[![christophlehmann](https://avatars.githubusercontent.com/u/4953689?v=4)](https://github.com/christophlehmann "christophlehmann (3 commits)")[![tim-asdfsd](https://avatars.githubusercontent.com/u/31507184?v=4)](https://github.com/tim-asdfsd "tim-asdfsd (3 commits)")[![mueller-sebastian](https://avatars.githubusercontent.com/u/20316366?v=4)](https://github.com/mueller-sebastian "mueller-sebastian (2 commits)")[![jacobsenj](https://avatars.githubusercontent.com/u/399303?v=4)](https://github.com/jacobsenj "jacobsenj (2 commits)")[![nlehmkuhl](https://avatars.githubusercontent.com/u/17159560?v=4)](https://github.com/nlehmkuhl "nlehmkuhl (2 commits)")[![schugabe](https://avatars.githubusercontent.com/u/138686?v=4)](https://github.com/schugabe "schugabe (2 commits)")[![tbsschmdt](https://avatars.githubusercontent.com/u/79580110?v=4)](https://github.com/tbsschmdt "tbsschmdt (2 commits)")[![jonnsn](https://avatars.githubusercontent.com/u/575971?v=4)](https://github.com/jonnsn "jonnsn (1 commits)")[![hoermannklaus](https://avatars.githubusercontent.com/u/5311695?v=4)](https://github.com/hoermannklaus "hoermannklaus (1 commits)") --- Tags monitoringt3monitoringtypo3-cms-extensiontypo3-extension ### Embed Badge ![Health badge](/badges/t3monitor-t3monitoring/health.svg) ``` [![Health](https://phpackages.com/badges/t3monitor-t3monitoring/health.svg)](https://phpackages.com/packages/t3monitor-t3monitoring) ``` ### Alternatives [aimeos/aimeos-typo3 Professional, full-featured and high performance TYPO3 e-commerce extension for online shops and complex B2B projects 1.5k91.2k4](/packages/aimeos-aimeos-typo3)[fluidtypo3/vhs This is a collection of ViewHelpers for performing rendering tasks that are not natively provided by TYPO3's Fluid templating engine. 1954.1M49](/packages/fluidtypo3-vhs)[pagemachine/typo3-formlog Form log for TYPO3 23225.3k6](/packages/pagemachine-typo3-formlog)[typo3/testing-framework The TYPO3 testing framework provides base classes for unit, functional and acceptance testing. 675.0M775](/packages/typo3-testing-framework)[t3monitor/t3monitoring_client Client extension for the t3monitoring service 31851.3k1](/packages/t3monitor-t3monitoring-client)[netresearch/rte-ckeditor-image Image support in CKEditor for the TYPO3 ecosystem - by Netresearch 63991.3k4](/packages/netresearch-rte-ckeditor-image) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)