Keitaro Best Practices #8: Status tab

Friends, we are in a hurry to present you with the final article of Keitaro Best Practices, in which we will analyze the functionality of the Status tab. Let’s go through each record and determine what indicators indicate the tracker’s regular operation and which ones signal possible malfunctions.

For what task is the Status tab used?

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.

What information can I find on the Status tab?

Let’s see what the Status tab tells us and what it gives us:

Installation method — Approved (v2.28.11)

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 — patch- (2021-09-30-14:12:01)

Build version and release time — information for developers, in case of debugging.

Clicks — 14,810

The total number of clicks in the tracker at the moment.

Conversions — 75

The total number of conversions in the tracker at the moment.

Size of commands queue — 0

The number of 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).

If your queue of commands builds up and does not unload even after stopping traffic to the tracker, you should immediately contact Support for help through the chat function on or the Telegram bot @keitarobot.

Cron timestamp— 12 October 2021, 12:14

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 — 21.63 Gb/37.43 Gb

21.63GB out of 37.43GB of your disk on the server is free.

Database size — 13.04 Mb

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 — 0 Bytes

This directory contains the reports that have been exported from the tracker.

Size of /var/logs — 2.20 Mb

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.

Cache storage — files (recommended)

Physical storage of cache data in files. When you click the Refresh cache button, the files are deleted, and new ones are created. The cache stores everything you see in the interface: information about campaigns, streams, domains, offers, landing pages, etc.

Using TokuDB: Yes

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.

We do not recommend changing this setting without consulting the Support team! You can contact us through the chat function on or through the Telegram bot Telegram bot.

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

Client-server protocol of interaction between a web server and an application. It is installed by default on all new installations.

CPU — 2.01%

The current load of the server processor. The standard load is considered to be a value of no more than 100%.

CPU — 2.1GHz, cores 2, Intel Xeon Processor (Skylake, IBRS)

Your server hardware data.

CPU Stolen — 0

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 — 3.17 Gb

The amount of free RAM.

Size of cache — 5.68 Mb

Cache size. More information can be found in the section Cache storage — files.

This is all the information that the Status tab provides. When using it on a daily basis, it is worth monitoring free disk space and the command queue from time to time. At the first suspicion of a tracker malfunction, you should restart RoadRunner and reset the cache. If this does not help, immediately contact Support for assistance using the chat function on or through the Telegram bot.

Keitaro Team

Team to deliver fresh and quality content!

View all posts by Keitaro Team →