Monitor and Log Tools

System Monitor

Currently, IoTDB provides users to use Java’s JConsole tool to monitor system status or use IoTDB’s open API to check data status.

System Status Monitoring

After starting JConsole tool and connecting to IoTDB server, you will have a basic look at IoTDB system status(CPU Occupation, in-memory information, etc.). See official documentation for more informations.

JMX MBean Monitoring

By using JConsole tool and connecting with JMX you can see some system statistics and parameters. This section describes how to use the JConsole Mbean tab to monitor the number of files opened by the IoTDB service process, the size of the data file, and so on. Once connected to JMX, you can find the MBean named org.apache.iotdb.service through the MBeans tab, as shown in the following Figure.

There are several attributes under Monitor, including the numbers of files opened in different folders, the data file size statistics and the values of some system parameters. By double-clicking the value corresponding to an attribute it can also display a line chart of that attribute. In particular, all the opened file count statistics are currently only supported on MacOS and most Linux distro except CentOS. For the OS not supported these statistics will return -2. See the following section for specific introduction of the Monitor attributes.

MBean Monitor Attributes List

• DataSizeInByte

• FileNodeNum

• OverflowCacheSize

• BufferWriteCacheSize

• BaseDirectory

• WriteAheadLogStatus

• TotalOpenFileNum

• DeltaOpenFileNum

• WalOpenFileNum

• MetadataOpenFileNum

• DigestOpenFileNum

• SocketOpenFileNum

• MergePeriodInSecond

• ClosePeriodInSecond

Data Status Monitoring

This module is the statistical monitoring method provided by IoTDB for users to store data information. We will record the statistical data in the system and store it in the database. The current 0.9.3 version of IoTDB provides statistics for writing data.

The user can choose to enable or disable the data statistics monitoring function (set the enable_stat_monitor item in the configuration file, see Engine Layer for details).

Writing Data Monitor

The current statistics of writing data by the system can be divided into two major modules: Global Writing Data Statistics and Storage Group Writing Data Statistics. Global Writing Data Statistics records the point number written by the user and the number of requests. Storage Group Writing Data Statistics records data of a certain storage group.

The system defaults to collect data every 5 seconds, and writes the statistics to the IoTDB and stores them in a system-specified locate. (If you need to change the statistic frequency, you can set The back_loop_period_in_second entry in the configuration file, see Section Engine Layer for details). After the system is refreshed or restarted, IoTDB does not recover the statistics, and the statistics data will restart from zero.

In order to avoid the excessive use of statistical information, we add a mechanism to periodically clear invalid data for statistical information. The system will delete invalid data at regular intervals. The user can set the trigger frequency (stat_monitor_retain_interval_in_second, default is 600s, see section Engine Layer for details) to set the frequency of deleting data. By setting the valid data duration (stat_monitor_detect_freq_in_second entry, the default is 600s, see section Engine Layer for details) to set the time period of valid data, that is, the data within the time of the clear operation trigger time is stat_monitor_detect_freq_in_second is valid data. In order to ensure the stability of the system, it is not allowed to delete the statistics frequently. Therefore, if the configuration parameter time is less than the default value (600s), the system will abort the configuration parameter and uses the default parameter.

It’s convenient for you to use select clause to get the writing data statistics the same as other timeseires.

Here are the writing data statistics:

• TOTAL_POINTS (GLOABAL)

• TOTAL_REQ_SUCCESS (GLOABAL)

• TOTAL_REQ_FAIL (GLOABAL)

• TOTAL_POINTS_FAIL (GLOABAL)

• TOTAL_POINTS_SUCCESS (GLOABAL)

• TOTAL_REQ_SUCCESS (STORAGE GROUP)

• TOTAL_REQ_FAIL (STORAGE GROUP)

• TOTAL_POINTS_SUCCESS (STORAGE GROUP)

• TOTAL_POINTS_FAIL (STORAGE GROUP)

Note:

should be replaced by real storage group name, and the ‘.’ in storage group need to be replaced by ‘_‘. For example, the storage group name is ‘root.a.b’, when using in the statistics, it will change to ‘root_a_b’

Example

Here we give some example of using writing data statistics.

If you want to know the global successful writing points number, you can use select clause to query it’s value. The query statement is like this:

select TOTAL_POINTS_SUCCESS from root.stats.write.global

If you want to know the successfule writing points number of root.ln (storage group), here is the query statement:

select TOTAL_POINTS_SUCCESS from root.stats.write.root_ln

If you want to know the current timeseries point in the system, you can use MAX_VALUE function to query. Here is the query statement:

select MAX_VALUE(TOTAL_POINTS_SUCCESS) from root.stats.write.root_ln

File Size Monitor

Sometimes we are concerned about how the data file size of IoTDB is changing, maybe to help calculate how much disk space is left or the data ingestion speed. The File Size Monitor provides several statistics to show how different types of file-sizes change.

The file size monitor defaults to collect file size data every 5 seconds using the same shared parameter back_loop_period_in_second,

Unlike Writing Data Monitor, currently File Size Monitor will not delete statistic data at regular intervals.

You can also use select clause to get the file size statistics like other time series.

Here are the file size statistics:

• DATA

• SETTLED

• OVERFLOW

• WAL

• INFO

• SCHEMA

Performance Monitor

Introduction

In order to grasp the performance of iotdb, we add this module to count the time-consumption of each operation. This module can compute the statistics of the avg time-consuming of each operation and the proportion of each operation whose time consumption falls into a time range. The output is in log_measure.log file. An output example is below.

Configuration parameter

location：conf/iotdb-engine.properties

**Table -parameter and description**

JMX MBean

Connect to jconsole with port 31999，and choose ‘MBean’in menu bar. Expand the sidebar and choose ‘org.apache.iotdb.db.cost.statistic’. You can Find：

Attribute

1. EnableStat：Whether the statistics are enabled or not, if it is true, the module records the time-consuming of each operation and prints the results; It is non-editable but can be changed by the function below.

2. DisplayIntervalInMs：The interval between print results. The changes will not take effect instantly. To make the changes effective, you should call startContinuousStatistics() or startOneTimeStatistics().

3. OperationSwitch：It’s a map to indicate whether the statistics of one kind of operation should be computed, the key is operation name and the value is true means the statistics of the operation are enabled, otherwise disabled. This parameter cannot be changed directly, it’s changed by operation ‘changeOperationSwitch()’.

Operation

1. startContinuousStatistics： Start the statistics and output at interval of ‘DisplayIntervalInMs’.
2. startOneTimeStatistics：Start the statistics and output in delay of ‘DisplayIntervalInMs’.
3. stopStatistic：Stop the statistics.
4. clearStatisticalState(): clear current stat result, reset statistical result.
5. changeOperationSwitch(String operationName, Boolean operationState):set whether to monitor a kind of operation. The param ‘operationName’ is the name of operation, defined in attribute operationSwitch. The param operationState is whether to enable the statistics or not. If the state is switched successfully, the function will return true, else return false.

Adding Custom Monitoring Items for contributors of IOTDB

Add Operation

Add an enumeration in org.apache.iotdb.db.cost.statistic.Operation.

Add Timing Code in Monitoring Area

Add timing code in the monitoring start area:

long t0 = System. currentTimeMillis();

Add timing code in the monitoring stop area:

Measurement.INSTANCE.addOperationLatency(Operation, t0);

Cache Hit Ratio Statistics

Overview

To improve query performance, IOTDB caches ChunkMetaData and TsFileMetaData. Users can view the cache hit ratio through debug level log and MXBean, and adjust the memory occupied by the cache according to the cache hit ratio and system memory. The method of using MXBean to view cache hit ratio is as follows:

1. Connect to jconsole with port 31999 and select ‘MBean’ in the menu item above.
2. Expand the sidebar and select ‘org.apache.iotdb.db.service’. You will get the results shown in the following figure:

## System log

IoTDB allows users to configure IoTDB system logs (such as log output level) by modifying the log configuration file. The default location of the system log configuration file is in $IOTDB_HOME/conf folder.

The default log configuration file is named logback.xml. The user can modify the configuration of the system running log by adding or changing the xml tree node parameters. It should be noted that the configuration of the system log using the log configuration file does not take effect immediately after the modification, instead, it will take effect after restarting the system. The usage of logback.xml is just as usual.

At the same time, in order to facilitate the debugging of the system by the developers and DBAs, we provide several JMX interfaces to dynamically modify the log configuration, and configure the Log module of the system in real time without restarting the system.

Dynamic System Log Configuration

Connect JMX

Here we use JConsole to connect with JMX.

Start the JConsole, establish a new JMX connection with the IoTDB Server (you can select the local process or input the IP and PORT for remote connection, the default operation port of the IoTDB JMX service is 31999). Fig 4.1 shows the connection GUI of JConsole.

After connected, click MBean and find ch.qos.logback.classic.default.ch.qos.logback.classic.jmx.JMXConfigurator(As shown in fig 4.2).

In the JMXConfigurator Window, there are 6 operations provided for you, as shown in fig 4.3. You can use there interfaces to perform operation.

Interface Instruction

• reloadDefaultConfiguration

This method is to reload the default logback configuration file. The user can modify the default configuration file first, and then call this method to reload the modified configuration file into the system to take effect.

• reloadByFileName

This method loads a logback configuration file with the specified path and name, and then makes it take effect. This method accepts a parameter of type String named p1, which is the path to the configuration file that needs to be specified for loading.

• getLoggerEffectiveLevel

This method is to obtain the current log level of the specified Logger. This method accepts a String type parameter named p1, which is the name of the specified Logger. This method returns the log level currently in effect for the specified Logger.

• getLoggerLevel

This method is to obtain the log level of the specified Logger. This method accepts a String type parameter named p1, which is the name of the specified Logger. This method returns the log level of the specified Logger. It should be noted that the difference between this method and the getLoggerEffectiveLevel method is that the method returns the log level that the specified Logger is set in the configuration file. If the user does not set the log level for the Logger. , then return empty. According to Logger’s log-level inheritance mechanism, f a Logger’s level is not explicitly set, it will inherit the log level settings from its nearest ancestor. At this point, calling the getLoggerEffectiveLevel method will return the log level in which the Logger is in effect; calling getLoggerLevel will return null.