Download the PHP package yesjoar/t3monitoring-client-extended without Composer
On this page you can find all versions of the php package yesjoar/t3monitoring-client-extended. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download yesjoar/t3monitoring-client-extended
More information about yesjoar/t3monitoring-client-extended
Files in yesjoar/t3monitoring-client-extended
Package t3monitoring-client-extended
Short Description Monitoring: scheduler and log insights - Adds scheduler, system log and log file insights to the t3monitoring_client endpoint
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package t3monitoring-client-extended
t3monitoring_client_extended
Adds scheduler, system log and log file insights to the endpoint of t3monitoring_client, so your monitoring shows right away when something goes wrong inside a TYPO3 installation:
- Scheduler – did the scheduler run recently? Which tasks failed, are overdue or stuck?
- System log – errors of
sys_login the last hours, grouped by message, and the number of failed backend logins. - Log files – errors written to
var/log/typo3_*.log(e.g. uncaught frontend exceptions that never show up insys_log). - Composer – the version constraints of the root
composer.json, so a monitoring server can tell whether an available update only needscomposer updateor a changed constraint (composer require).
| Extension key | t3monitoring_client_extended |
| Composer name | yesjoar/t3monitoring-client-extended |
| TYPO3 | 12.4, 13.4, 14 |
| PHP | 8.2 – 8.5 |
| Requires | t3monitor/t3monitoring_client 11 |
Installation
There is nothing else to set up: the extension registers its providers in t3monitoring_client. The next request
to ?eID=t3monitoring&secret=… contains the additional data.
What the endpoint delivers
The result is delivered twice, so it is useful for the t3monitoring server as well as for other monitoring servers:
- Messages in
extra(warning/danger), the groups the t3monitoring server imports and shows for a client, e.g.Scheduler - 2 failed task(s)orLog files - 14 error(s) in the last 24 hours. They work without any change of the server. - Structured data in
extendedfor monitoring servers that want to evaluate it:
composer is plain data without messages: package names (with a vendor) and their constraints. It is only
evaluated by monitoring servers that know the available versions; available is false without Composer mode.
All times are Unix timestamps. scheduler.lastRunStatus rates the last run by the configured thresholds:
ok, warning, error, never (tasks are enabled, but the scheduler never ran) or unused (no enabled tasks). version is increased on incompatible changes of the format. If a provider
fails, the endpoint keeps working: the error is reported in extended.errors.<provider> and as a warning in extra.
Configuration
Admin Tools → Settings → Extension Configuration → t3monitoring_client_extended
| Setting | Default | Description |
|---|---|---|
scheduler.enabled |
1 | Report the scheduler |
scheduler.lastRunWarningMinutes |
60 | Warning if the scheduler did not run for this long |
scheduler.lastRunErrorMinutes |
360 | Error if the scheduler did not run for this long |
scheduler.overdueMinutes |
60 | An enabled task is overdue if its planned execution is older |
scheduler.stuckMinutes |
240 | A task is stuck if it is marked as running for longer |
sysLog.enabled |
1 | Report errors of sys_log |
sysLog.periodHours |
24 | Period that is evaluated |
sysLog.maxGroups |
10 | Number of different errors that are reported |
sysLog.failedLoginsWarning |
50 | Warning from this number of failed backend logins (0 = off) |
logFiles.enabled |
1 | Report errors of the log files |
logFiles.periodHours |
24 | Period that is evaluated |
logFiles.maxGroups |
10 | Number of different errors that are reported |
logFiles.minimumLevel |
error | Minimum PSR-3 level (warning … emergency) |
logFiles.maxBytesPerFile |
1048576 | Only the end of each log file is read |
composer.enabled |
1 | Report the version constraints of composer.json |
ignoredMessages |
Comma separated text fragments; matching entries are skipped |
Privacy and security
The data leaves the installation, so it is reduced on purpose:
- No user names, IP addresses or record data of
sys_logare read; only the message of an entry. - Query strings of URLs (which may contain secrets), email and IP addresses are removed from all messages.
- Messages are limited to 300 characters; equal messages are grouped.
- Scheduler tasks are never unserialized, so no code of task classes is executed.
- Of
composer.jsononly package names and version constraints are read – no repositories or credentials.
Every provider can be disabled, also in config/system/additional.php:
The endpoint itself is protected by t3monitoring_client (secret and allowed IPs).
Development
The checks run in Docker with the images of the TYPO3 core testing:
Release
The extension is distributed via Packagist only.
- Set the version in
ext_emconf.phpand incomposer.json(extra.typo3/cms.version), updateCHANGELOG.md. - Create and push a tag with the version, e.g.
git tag -a 1.0.0 -m "First stable release" && git push --tags. Packagist picks up the tag through its GitHub hook.
License
GPL-2.0-or-later. Developed by Kai Seliger.
All versions of t3monitoring-client-extended with dependencies
t3monitor/t3monitoring_client Version ^11.0
typo3/cms-core Version ^12.4 || ^13.4 || ^14.0