/t3monitoring

Monitoring service of TYPO3 extensions

Primary LanguagePHPGNU General Public License v2.0GPL-2.0

TYPO3 CMS Extension "t3monitoring"

https://travis-ci.org/georgringer/t3monitoring.svg?branch=master

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 8 LTS (monitoring works also for 6.2 installations)
  • The host must have access to every client to be able to fetch the data

Important: This extension is still beta and things might change!

Pricing This extension is completly 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 (mail@ringer.it) or slack for questions and to receive an invoice!

Screenshots

Overview

Overview including most important information

Search result

Search result

Single view of a client

Client

List of all used extensions

Extensions

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. You can find this extension on github (https://github.com/georgringer/t3monitoring_client) or later in the TER.

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 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

To be able to deliver proper results, this extensions requires information about all core versions and all extensions. This information is provided by typo3.org.

To import the data, use the command line:

./typo3/cli_dispatch.phpsh extbase 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:

  • ./typo3/cli_dispatch.phpsh extbase monitoring:importCore to fetch latest core versions
  • ./typo3/cli_dispatch.phpsh extbase monitoring:importExtensions to fetch the extensions
  • ./typo3/cli_dispatch.phpsh extbase monitoring:importClients to fetch the client data