# Status
Since Keitaro is a self-hosted product installed on the client's server, the tracker can monitor technical conditions. It includes information about the installation, assembly version, server version, and other indicators by which you can evaluate the operability of a particular tracker.
Located under Maintenance → Status.
# Installation method
This record shows the way the tracker was installed, as well as the version of the installer. All new trackers that are installed via the terminal by the auto-install command always have the status approved.
Version 2.28.11: This record shows the version of the installer (program) that installed the tracker on the server. Not to be confused with the version of the tracker itself, which is specified in Admin.
The lower the installation version, the more likely your tracker will work on the old configuration. It will not include the latest optimization settings with hardware or various package modules that will help implement all tracker functionality.
You can always check the actual version of the installer in Support and, if necessary, request an update.
# Build version
Build version and release time — information for developers, in case of debugging.
# Clicks
The total amount clicks in the tracker now.
# Conversions
The total amount conversions in the tracker now.
# Size of commands queue
The amount commands that the tracker has not yet processed. When the traffic volumes exceed the recommended specifications for the hardware, the tracker may not have time to process all requests and puts them in a virtual queue, which it processes as resources are freed.
Also, a queue can be formed if the database is locked by a voluminous process, for example, mass data cleansing (statistics).
# Cron timestamp
This shows the time Сron last ran. Cron is responsible for processing commands and runs once a minute. If Cron has not run for a long time, you should see an error in the tracker admin panel (yellow triangle with a notification about a non-working cron). The tracker will not process your traffic in such a situation, and this state is considered entirely inoperative.
# Free disk space
The amount of free disk space on the server.
# Database size
Database size. The database includes all the statistics of the tracker: a list of all created resources and their settings, information about clicks, and conversions, and tracker settings. However, local landing pages are not included in the database, and in case of moving to another server, they are transferred separately.
# Size of /export
This directory contains the reports that have been exported from the tracker.
# Size of /var/logs
This is the size of the directory where the tracker logs are stored (Maintenance — Logs). It has an automatic cleaning function for when the maximum log size is reached. The default value is set in config.ini.php and is 10Mb.
# Using TokuDB
Ability to switch the database (DB) operation to TokuDb mode. All new trackers automatically start the DB operation mode in TokuDb. To switch from old trackers, we recommend moving to a new server using the latest installer version.
# PHP Engine — RoadRunner
The current server the tracker is running on. All new versions of trackers work on RoadRunner (at the time of writing this article).
# FCGI
Keitaro uses fcgi to execute local landing pages.
# CPU
The current load of the server processor. The standard load is considered to be a value of at most 100%.
# CPU Stolen
The amount of time that the virtual server waits for processor resources from the hypervisor. If 0, the server does not freeze, and everything is OK.
# Free memory
The amount of free RAM.
# Size of cache
Cache size. More information can be found in the section Cache storage.
← Logs Troubleshooting →