Zabbix優化之必殺技-表分區

時間2014-05-06

作者 itnihao

郵箱 [email protected]

博客 http://www.itnihao.com

如需引用，請註明以上信息，謝謝合作

前言，使用zabbix最大的瓶頸在於數據庫,維護好zabbix的數據存儲，告警，即能夠很好的應用zabbix去構建監控系統。本文所講的正是數據存儲部分。本文所針對的用戶，需要對zabbix有一定概念，對MySQL熟悉，掌握存儲過程的書寫，對zabbix數據庫字段熟悉

本部分內容來自本人的新書，作爲對新書分表章節的部分補充，書名叫《zabbix監控系統》，將於2014-06與讀者面市。書的章節目錄已經放在github上面

https://github.com/itnihao/zabbix-book/blob/master/README.md

Zabbix中歷史數據的

zabbix對數據將數據存於數據庫，其主要將歷史數據存於history和trends的2個表中，如下

1）歷史數據的表

2）警告日誌數據的表

History表結構

mysql> show create table history\G;
*************************** 1. row ***************************
       Table: history
Create Table: CREATE TABLE `history` (
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `value` double(16,4) NOT NULL DEFAULT '0.0000',
  `ns` int(11) NOT NULL DEFAULT '0',
  KEY `history_1` (`itemid`,`clock`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
mysql> show create table history_str\G;
       Table: history_str
Create Table: CREATE TABLE `history_str` (
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `value` varchar(255) NOT NULL DEFAULT '',
  `ns` int(11) NOT NULL DEFAULT '0',
  KEY `history_str_1` (`itemid`,`clock`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
mysql> show create table history_str_sync \G;
*************************** 1. row ***************************
       Table: history_str_sync
Create Table: CREATE TABLE `history_str_sync` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `nodeid` int(11) NOT NULL,
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `value` varchar(255) NOT NULL DEFAULT '',
  `ns` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  KEY `history_str_sync_1` (`nodeid`,`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
mysql> show create table history_sync \G;
*************************** 1. row ***************************
       Table: history_sync
Create Table: CREATE TABLE `history_sync` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `nodeid` int(11) NOT NULL,
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `value` double(16,4) NOT NULL DEFAULT '0.0000',
  `ns` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  KEY `history_sync_1` (`nodeid`,`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
mysql> show create table history_text \G;
*************************** 1. row ***************************
       Table: history_text
Create Table: CREATE TABLE `history_text` (
  `id` bigint(20) unsigned NOT NULL,
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `value` text NOT NULL,
  `ns` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  UNIQUE KEY `history_text_2` (`itemid`,`id`),
  KEY `history_text_1` (`itemid`,`clock`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
mysql> show create table history_log\G;
*************************** 1. row ***************************
       Table: history_log
Create Table: CREATE TABLE `history_log` (
  `id` bigint(20) unsigned NOT NULL,
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `timestamp` int(11) NOT NULL DEFAULT '0',
  `source` varchar(64) NOT NULL DEFAULT '',
  `severity` int(11) NOT NULL DEFAULT '0',
  `value` text NOT NULL,
  `logeventid` int(11) NOT NULL DEFAULT '0',
  `ns` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  UNIQUE KEY `history_log_2` (`itemid`,`id`),
  KEY `history_log_1` (`itemid`,`clock`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
mysql> show create table history_uint \G;
*************************** 1. row ***************************
       Table: history_uint
Create Table: CREATE TABLE `history_uint` (
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `value` bigint(20) unsigned NOT NULL DEFAULT '0',
  `ns` int(11) NOT NULL DEFAULT '0',
  KEY `history_uint_1` (`itemid`,`clock`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
mysql> show create table history_uint_sync\G;
*************************** 1. row ***************************
       Table: history_uint_sync
Create Table: CREATE TABLE `history_uint_sync` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `nodeid` int(11) NOT NULL,
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `value` bigint(20) unsigned NOT NULL DEFAULT '0',
  `ns` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  KEY `history_uint_sync_1` (`nodeid`,`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

trends表結構

mysql> show create table trends\G;
*************************** 1. row ***************************
       Table: trends
Create Table: CREATE TABLE `trends` (
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `num` int(11) NOT NULL DEFAULT '0',
  `value_min` double(16,4) NOT NULL DEFAULT '0.0000',
  `value_avg` double(16,4) NOT NULL DEFAULT '0.0000',
  `value_max` double(16,4) NOT NULL DEFAULT '0.0000',
  PRIMARY KEY (`itemid`,`clock`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
mysql> show create table trends_uint\G;
*************************** 1. row ***************************
       Table: trends_uint
Create Table: CREATE TABLE `trends_uint` (
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `num` int(11) NOT NULL DEFAULT '0',
  `value_min` bigint(20) unsigned NOT NULL DEFAULT '0',
  `value_avg` bigint(20) unsigned NOT NULL DEFAULT '0',
  `value_max` bigint(20) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`itemid`,`clock`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

housekeeper表結構

mysql> show create table housekeeper\G;
*************************** 1. row ***************************
       Table: housekeeper
Create Table: CREATE TABLE `housekeeper` (
  `housekeeperid` bigint(20) unsigned NOT NULL,
  `tablename` varchar(64) NOT NULL DEFAULT '',
  `field` varchar(64) NOT NULL DEFAULT '',
  `value` bigint(20) unsigned NOT NULL,
  PRIMARY KEY (`housekeeperid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

儘管將housekeeper功能已經關閉，但zabbix-server和WEB前端仍然會記錄數據到housekeeper表，這裏爲了防止寫入數據，將其表的引擎設置爲BLACKHOLE，使其不可寫。

mysql>  ALTER TABLE housekeeper ENGINE = BLACKHOLE;

mysql> show create table housekeeper\G;
*************************** 1. row ***************************
       Table: housekeeper
Create Table: CREATE TABLE `housekeeper` (
  `housekeeperid` bigint(20) unsigned NOT NULL,
  `tablename` varchar(64) NOT NULL DEFAULT '',
  `field` varchar(64) NOT NULL DEFAULT '',
  `value` bigint(20) unsigned NOT NULL,
  PRIMARY KEY (`housekeeperid`)
) ENGINE=BLACKHOLE DEFAULT CHARSET=utf8

查看索引

mysql> show index from history\G;

如下表所示

改變history_text表結構

mysql> show create table history_text\G;

*************************** 1. row ***************************

Table: history_text

Create Table: CREATE TABLE `history_text` (

`id` bigint(20) unsigned NOT NULL,

`itemid` bigint(20) unsigned NOT NULL,

`clock` int(11) NOT NULL DEFAULT '0',

`value` text NOT NULL,

`ns` int(11) NOT NULL DEFAULT '0',

PRIMARY KEY (`id`),

UNIQUE KEY `history_text_2` (`itemid`,`id`),

KEY `history_text_1` (`itemid`,`clock`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8

mysql> Alter table history_text drop primary key, add index (id), drop index history_text_2, add index history_text_2 (itemid, id);

mysql> show create table history_text\G;

*************************** 1. row ***************************

Table: history_text

Create Table: CREATE TABLE `history_text` (

`id` bigint(20) unsigned NOT NULL,

`itemid` bigint(20) unsigned NOT NULL,

`clock` int(11) NOT NULL DEFAULT '0',

`value` text NOT NULL,

`ns` int(11) NOT NULL DEFAULT '0',

KEY `history_text_1` (`itemid`,`clock`),

KEY `id` (`id`), #原來的PRIMARY KEY

KEY `history_text_2` (`itemid`,`id`) #原來的UNIQUE KEY

) ENGINE=InnoDB DEFAULT CHARSET=utf8

改變history_log表結構

mysql> show create table history_log\G;

*************************** 1. row ***************************

Table: history_log

Create Table: CREATE TABLE `history_log` (

`id` bigint(20) unsigned NOT NULL,

`itemid` bigint(20) unsigned NOT NULL,

`clock` int(11) NOT NULL DEFAULT '0',

`timestamp` int(11) NOT NULL DEFAULT '0',

`source` varchar(64) NOT NULL DEFAULT '',

`severity` int(11) NOT NULL DEFAULT '0',

`value` text NOT NULL,

`logeventid` int(11) NOT NULL DEFAULT '0',

`ns` int(11) NOT NULL DEFAULT '0',

PRIMARY KEY (`id`),

UNIQUE KEY `history_log_2` (`itemid`,`id`),

KEY `history_log_1` (`itemid`,`clock`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8

mysql> Alter table history_log drop primary key, add index (id), drop index history_log_2, add index history_log_2 (itemid, id);

mysql> show create table history_log\G;

*************************** 1. row ***************************

Table: history_log

Create Table: CREATE TABLE `history_log` (

`id` bigint(20) unsigned NOT NULL,

`itemid` bigint(20) unsigned NOT NULL,

`clock` int(11) NOT NULL DEFAULT '0',

`timestamp` int(11) NOT NULL DEFAULT '0',

`source` varchar(64) NOT NULL DEFAULT '',

`severity` int(11) NOT NULL DEFAULT '0',

`value` text NOT NULL,

`logeventid` int(11) NOT NULL DEFAULT '0',

`ns` int(11) NOT NULL DEFAULT '0',

KEY `history_log_1` (`itemid`,`clock`),

KEY `id` (`id`), #原來的PRIMARY KEY

KEY `history_log_2` (`itemid`,`id`) #原來的UNIQUE KEY

) ENGINE=InnoDB DEFAULT CHARSET=utf8

表分區的過程

防盜鏈，來自博客 http://www.itnihao.com

創建存儲過程

分區創建的存儲過程

DELIMITER $$

CREATEPROCEDURE`partition_create`(SCHEMANAME VARCHAR(64), TABLENAME VARCHAR(64), PARTITIONNAME VARCHAR(64), CLOCK INT)

BEGIN

SCHEMANAME = The DB schema in which to make changes

TABLENAME = The table with partitions to potentially delete

PARTITIONNAME = The name of the partition to create

Verify that the partition does not already exist

DECLARE RETROWS INT;

SELECTCOUNT(1)INTO RETROWS

FROM information_schema.partitions

WHERE table_schema = SCHEMANAME ANDTABLE_NAME= TABLENAME AND partition_name = PARTITIONNAME;

IF RETROWS =0THEN

1. Print a message indicating that a partition was created

2. Create the SQL to create the partition

3. Execute the SQL from #2.

SELECT CONCAT("partition_create(", SCHEMANAME,",", TABLENAME,",", PARTITIONNAME,",", CLOCK,")")AS msg;

SET @SQL= CONCAT('ALTER TABLE ', SCHEMANAME,'.', TABLENAME,' ADD PARTITION (PARTITION ', PARTITIONNAME,' VALUES LESS THAN (', CLOCK,'));');

PREPARE STMT FROM @SQL;

EXECUTE STMT;

DEALLOCATE PREPARE STMT;

ENDIF;

END$$

DELIMITER ;

分區刪除的存儲過程

DELIMITER $$

CREATEPROCEDURE`partition_drop`(SCHEMANAME VARCHAR(64), TABLENAME VARCHAR(64), DELETE_BELOW_PARTITION_DATE BIGINT)

BEGIN

SCHEMANAME = The DB schema in which to make changes

TABLENAME = The table with partitions to potentially delete

DELETE_BELOW_PARTITION_DATE = Delete any partitions with names that are dates older than this one (yyyy-mm-dd)

DECLARE done INTDEFAULTFALSE;

DECLARE drop_part_name VARCHAR(16);

Get a list of all the partitions that are older than the date

in DELETE_BELOW_PARTITION_DATE. All partitions are prefixed with

a "p", so use SUBSTRING TO get rid of that character.

DECLARE myCursor CURSOR FOR

SELECT partition_name

FROM information_schema.partitions

WHERE table_schema = SCHEMANAME ANDTABLE_NAME= TABLENAME ANDCAST(SUBSTRING(partition_name FROM2)ASUNSIGNED)< DELETE_BELOW_PARTITION_DATE;

DECLARE CONTINUE HANDLER FORNOT FOUND SET done =TRUE;

Create the basics for when we need to drop the partition. Also, create

@drop_partitions to hold a comma-delimited list of all partitions that

should be deleted.

SET @alter_header = CONCAT("ALTER TABLE ", SCHEMANAME,".", TABLENAME," DROP PARTITION ");

SET @drop_partitions ="";

Start looping through all the partitions that are too old.

OPEN myCursor;

read_loop: LOOP

FETCH myCursor INTO drop_part_name;

IF done THEN

LEAVE read_loop;

ENDIF;

SET @drop_partitions =IF(@drop_partitions ="", drop_part_name, CONCAT(@drop_partitions,",", drop_part_name));

END LOOP;

IF @drop_partitions !=""THEN

1. Build the SQL to drop all the necessary partitions.

2. Run the SQL to drop the partitions.

3. Print out the table partitions that were deleted.

SET @full_sql = CONCAT(@alter_header, @drop_partitions,";");

PREPARE STMT FROM @full_sql;

EXECUTE STMT;

DEALLOCATE PREPARE STMT;

SELECT CONCAT(SCHEMANAME,".", TABLENAME)AS`table`, @drop_partitions AS`partitions_deleted`;

ELSE

No partitions are being deleted, so print out "N/A" (Not

applicable) to indicatethat no changes were made.

SELECT CONCAT(SCHEMANAME,".", TABLENAME)AS`table`,"N/A"AS`partitions_deleted`;

ENDIF;

END$$

DELIMITER ;

分區維護的存儲過程

DELIMITER $$

CREATEPROCEDURE`partition_maintenance`(SCHEMA_NAME VARCHAR(32),TABLE_NAMEVARCHAR(32), KEEP_DATA_DAYS INT, HOURLY_INTERVAL INT, CREATE_NEXT_INTERVALS INT)

BEGIN

DECLARE OLDER_THAN_PARTITION_DATE VARCHAR(16);

DECLARE PARTITION_NAME VARCHAR(16);

DECLARE LESS_THAN_TIMESTAMP INT;

DECLARE CUR_TIME INT;

CALL partition_verify(SCHEMA_NAME,TABLE_NAME, HOURLY_INTERVAL);

SET CUR_TIME = UNIX_TIMESTAMP(DATE_FORMAT(NOW(),'%Y-%m-%d 00:00:00'));

IFDATE(NOW())='2014-04-01'THEN

SET CUR_TIME = UNIX_TIMESTAMP(DATE_FORMAT(DATE_ADD(NOW(),INTERVAL1DAY),'%Y-%m-%d 00:00:00'));

ENDIF;

SET @__interval =1;

create_loop: LOOP

IF @__interval > CREATE_NEXT_INTERVALS THEN

LEAVE create_loop;

ENDIF;

SET LESS_THAN_TIMESTAMP = CUR_TIME +(HOURLY_INTERVAL * @__interval *3600);

SET PARTITION_NAME = FROM_UNIXTIME(CUR_TIME + HOURLY_INTERVAL *(@__interval -1)*3600,'p%Y%m%d%H00');

CALL partition_create(SCHEMA_NAME,TABLE_NAME, PARTITION_NAME, LESS_THAN_TIMESTAMP);

SET @__interval=@__interval+1;

END LOOP;

SET OLDER_THAN_PARTITION_DATE=DATE_FORMAT(DATE_SUB(NOW(),INTERVAL KEEP_DATA_DAYS DAY),'%Y%m%d0000');

CALL partition_drop(SCHEMA_NAME,TABLE_NAME, OLDER_THAN_PARTITION_DATE);

END$$

DELIMITER ;

分區校驗的存儲過程

DELIMITER $$

CREATEPROCEDURE`partition_verify`(SCHEMANAME VARCHAR(64), TABLENAME VARCHAR(64), HOURLYINTERVAL INT(11))

BEGIN

DECLARE PARTITION_NAME VARCHAR(16);

DECLARE RETROWS INT(11);

DECLARE FUTURE_TIMESTAMP TIMESTAMP;

/** Check if any partitions exist for the given SCHEMANAME.TABLENAME. */

SELECTCOUNT(1)INTO RETROWS

FROM information_schema.partitions

WHERE table_schema = SCHEMANAME ANDTABLE_NAME= TABLENAME AND partition_name ISNULL;

/* * If partitions do not exist, go ahead and partition the table*/

IF RETROWS =1THEN

* Take the current date at 00:00:00 and add HOURLYINTERVAL to it. This is the timestamp below which we will store values.

* We begin partitioning based on the beginning of a day. This is because we don't want to generate a random partition

* that won't necessarily fall in line with the desired partition naming (ie: if the hour interval is 24 hours, we could

* end up creating a partition now named "p201403270600" when all other partitions will be like "p201403280000").

SET FUTURE_TIMESTAMP = TIMESTAMPADD(HOUR, HOURLYINTERVAL, CONCAT(CURDATE()," ",'00:00:00'));

SET PARTITION_NAME = DATE_FORMAT(CURDATE(),'p%Y%m%d%H00');

-- Create the partitioning query

SET @__PARTITION_SQL = CONCAT("ALTER TABLE ", SCHEMANAME,".", TABLENAME," PARTITION BY RANGE(`clock`)");

SET @__PARTITION_SQL = CONCAT(@__PARTITION_SQL,"(PARTITION ", PARTITION_NAME," VALUES LESS THAN (", UNIX_TIMESTAMP(FUTURE_TIMESTAMP),"));");

-- Run the partitioning query

PREPARE STMT FROM @__PARTITION_SQL;

EXECUTE STMT;

DEALLOCATE PREPARE STMT;

ENDIF;

END$$

DELIMITER ;

使用存儲過程

mysql>CALL partition_maintenance('<zabbix_db_name>','<table_name>',<days_to_keep_data>,<hourly_interval>,<num_future_intervals_to_create>)

例如，zabbix.history保存28天，表區間的時間爲24小時，預留14天的區間。

mysql> CALL partition_maintenance('zabbix', 'history', 28, 24, 14);
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405070000,1399478400) |
+-----------------------------------------------------------+
1 row in set (18.75 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405080000,1399564800) |
+-----------------------------------------------------------+
1 row in set (19.08 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405090000,1399651200) |
+-----------------------------------------------------------+
1 row in set (19.16 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405100000,1399737600) |
+-----------------------------------------------------------+
1 row in set (19.27 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405110000,1399824000) |
+-----------------------------------------------------------+
1 row in set (19.42 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405120000,1399910400) |
+-----------------------------------------------------------+
1 row in set (19.52 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405130000,1399996800) |
+-----------------------------------------------------------+
1 row in set (19.63 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405140000,1400083200) |
+-----------------------------------------------------------+
1 row in set (19.89 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405150000,1400169600) |
+-----------------------------------------------------------+
1 row in set (20.00 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405160000,1400256000) |
+-----------------------------------------------------------+
1 row in set (20.07 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405170000,1400342400) |
+-----------------------------------------------------------+
1 row in set (20.13 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405180000,1400428800) |
+-----------------------------------------------------------+
1 row in set (20.20 sec)
+-----------------------------------------------------------+
| msg                                                       |
+-----------------------------------------------------------+
| partition_create(zabbix,history,p201405190000,1400515200) |
+-----------------------------------------------------------+
1 row in set (20.31 sec)
+----------------+--------------------+
| table          | partitions_deleted |
+----------------+--------------------+
| zabbix.history | N/A                |
+----------------+--------------------+
1 row in set (20.42 sec)
Query OK, 0 rows affected (20.42 sec)

創建存儲過程

DELIMITER $$
CREATE PROCEDURE `partition_maintenance_all`(SCHEMA_NAME VARCHAR(32))
BEGIN
       CALL partition_maintenance(SCHEMA_NAME, 'history', 28, 24, 14);
       CALL partition_maintenance(SCHEMA_NAME, 'history_log', 28, 24, 14);
       CALL partition_maintenance(SCHEMA_NAME, 'history_str', 28, 24, 14);
       CALL partition_maintenance(SCHEMA_NAME, 'history_text', 28, 24, 14);
       CALL partition_maintenance(SCHEMA_NAME, 'history_uint', 28, 24, 14);
       CALL partition_maintenance(SCHEMA_NAME, 'trends', 730, 24, 14);
       CALL partition_maintenance(SCHEMA_NAME, 'trends_uint', 730, 24, 14);
END$$
DELIMITER ;

調用存儲過程

mysql> CALL partition_maintenance_all('zabbix');
+----------------+--------------------+
| table          | partitions_deleted |
+----------------+--------------------+
| zabbix.history | N/A                |
+----------------+--------------------+
1 row in set (0.01 sec)
....
....
....
+--------------------+--------------------+
| table              | partitions_deleted |
+--------------------+--------------------+
| zabbix.trends_uint | N/A                |
+--------------------+--------------------+
1 row in set (22.41 sec)
Query OK, 0 rows affected, 1 warning (22.41 sec)
mysql>

查看錶結構

mysql> show create table history\G;
*************************** 1. row ***************************
       Table: history
Create Table: CREATE TABLE `history` (
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT '0',
  `value` double(16,4) NOT NULL DEFAULT '0.0000',
  `ns` int(11) NOT NULL DEFAULT '0',
  KEY `history_1` (`itemid`,`clock`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
/*!50100 PARTITION BY RANGE (`clock`)
(PARTITION p201405060000 VALUES LESS THAN (1399392000) ENGINE = InnoDB,
 PARTITION p201405070000 VALUES LESS THAN (1399478400) ENGINE = InnoDB,
 PARTITION p201405080000 VALUES LESS THAN (1399564800) ENGINE = InnoDB,
 PARTITION p201405090000 VALUES LESS THAN (1399651200) ENGINE = InnoDB,
 PARTITION p201405100000 VALUES LESS THAN (1399737600) ENGINE = InnoDB,
 PARTITION p201405110000 VALUES LESS THAN (1399824000) ENGINE = InnoDB,
 PARTITION p201405120000 VALUES LESS THAN (1399910400) ENGINE = InnoDB,
 PARTITION p201405130000 VALUES LESS THAN (1399996800) ENGINE = InnoDB,
 PARTITION p201405140000 VALUES LESS THAN (1400083200) ENGINE = InnoDB,
 PARTITION p201405150000 VALUES LESS THAN (1400169600) ENGINE = InnoDB,
 PARTITION p201405160000 VALUES LESS THAN (1400256000) ENGINE = InnoDB,
 PARTITION p201405170000 VALUES LESS THAN (1400342400) ENGINE = InnoDB,
 PARTITION p201405180000 VALUES LESS THAN (1400428800) ENGINE = InnoDB,
 PARTITION p201405190000 VALUES LESS THAN (1400515200) ENGINE = InnoDB) */

添加定時任務

1 1 * * *   mysql  -uzabbix -pzabbix zabbix -e "CALL partition_maintenance_all('zabbix')"

參考文檔

本文參考https://www.zabbix.org/wiki/Docs/howto/mysql_partition寫成。

Zabbix優化之必殺技-表分區

本部分內容來自本人的新書，作爲對新書分表章節的部分補充，書名叫《zabbix監控系統》，將於2014-06與讀者面市。書的章節目錄已經放在github上面

https://github.com/itnihao/zabbix-book/blob/master/README.md

Zabbix中歷史數據的

zabbix對數據將數據存於數據庫，其主要將歷史數據存於history和trends的2個表中，如下

1）歷史數據的表

2）警告日誌數據的表

History表結構

trends表結構

housekeeper表結構

查看索引

改變history_text表結構

改變history_log表結構

表分區的過程

創建存儲過程

使用存儲過程

創建存儲過程

調用存儲過程

查看錶結構

AI 畫圖真刺激，手把手教你如何用 ComfyUI 來畫出刺激的圖

公司剛入職了一名 Java 中級開發，短短 4 行代碼居然湊齊了 3 個 bug！我哭了~~

數據展示動態（跑分）顯示

公衆號5月C#/.NET熱文一覽

git 下載大陸鏡像地址

grafana-zabbix安裝簡明教程

Zabbix企業級分佈式監控系統第2版即將出版

Zabbix監控可視化

當CMDB遇上Zabbix,工程師的幸福感提升?

搞定微信告警

https://yachay.unat.edu.pe/blog/index.php?comment_area=format_blog&comment_component=blog&comment_co

linux以太網驅動總結