Skip to main content

Matomo Cluster Overview

Server setup diagram​

Proxy​

hostname: matomo.tf.analys.cloud CPU: 4 RAM: 2gb Disk: 20gb IPv4/IPv6: 159.253.30.109 / 2a02:750:7:3305::729 Domain: matomo.tf.analys.cloud LetsEncrypt: true

Instead of using the glesys provided loadbalancer we use a ngin-based proxy instead.

The resoning behind this are:

  • The Glesys provided service does not support LetsEncrypt certificates.
  • The GleSYS provided service does not support monitoring.
  • Overall this gives us more control over the loadbalancer and makes it possible do deploy custom configurations to our customers.

Frontend servers​

CPU: 4 RAM: 2gb Disk: 20gb IPs: 159.253.30.91, 159.253.30.140, 159.253.30.245

For Trafikförvaltningen we currently have 3 "frontend" servers. f1.tf.analys.cloud, f2.tf.analys.cloud and f3.tf.analys.cloud.

Small frontend server that handles the traffic. The frontend servers are using Nginx and PHP-FPM.

Matomo Admin Server​

CPU: 16 RAM: 16GB Disk: 20 GB IP: 159.253.30.202 Hostname: webbanalys.tf.analys.cloud Domainname: webbanalys.tf.analys.cloud

Used for the Matomo web interface and to run the archive schedulers

Ansible command to provision​

 ansible-playbook server-matomo-app.yml -e env=tf-matomo-app -u <USERNAME>

Database Server​

CPU: 16 RAM: 16GB Disk: 250 GB IP: 159.253.27.246 Hostname: database.tf.analys.cloud

MariaDSB server.

Ansible command to provision​

 ansible-playbook server-matomo-database.yml -e env=tf-matomo-database -u <USERNAME>

Other​

SSH Config example to paste into ~/.ssh/config​

Host tf-app tf-f1 tf-f2 tf-f3 tf-db tf-redis
  User <your-username>

Host tf-app
  HostName 159.253.30.202
  ControlMaster auto
  ControlPath ~/.ssh/ansible-%r@%h:%p
  ControlPersist 5m

Host tf-f1
  HostName 159.253.30.91

Host tf-f2
  HostName 159.253.30.140

Host tf-f3
  HostName 159.253.30.245

Host tf-db
  HostName 159.253.27.246

Host tf-redis
  HostName 159.253.31.106

Changelog​

  • 2022-05-09 – Enviroment started and customer has been granted access to service