zabbix历史数据相关表研究

history和trends相关表

history和trends都是存储历史数据的地方。一般是通过监控项(item)配置里、匹配更新监控项(item)和设置HouseKeeper tasks来设置保留数据的时长。

Housekeeper 会定期删除过期的数据。如果不是特别有意义,建议你把保留时间设置短一些, 如果想看以前的数 据图怎么办?这里趋势数据就派上用场了,一般只要小时平均即可这样话趋势据保留久一点即可,趋势数据的计算源数据来自history表。如果将history设置为0那么就只会获取item的值然后用于触发器,不会存历史数据到数据库。

监控项前端配置:

  • history相关表

    MariaDB [rtm]> show tables like 'history%';
    +--------------------------+
    | Tables_in_rtm (history%) |
    +--------------------------+
    | history |
    | history_log |
    | history_str |
    | history_text |
    | history_uint |
    +--------------------------+
    • history

      history 表存放信息类型为浮点数的监控项历史数据,类型在配置监控项是指定

      itemid: 监控项唯一标识id

      clock: 时间戳整数部分

      value: 监控项的值

      ns: 纳秒数

      MariaDB [rtm]> desc history;
      +--------+---------------------+------+-----+---------+-------+
      | Field | Type | Null | Key | Default | Extra |
      +--------+---------------------+------+-----+---------+-------+
      | itemid | bigint(20) unsigned | NO | MUL | NULL | |
      | clock | int(11) | NO | | 0 | |
      | value | double(16,4) | NO | | 0.0000 | |
      | ns | int(11) | NO | | 0 | |
      +--------+---------------------+------+-----+---------+-------+ MariaDB [rtm]> select * from history limit 10;
      +-----------+------------+---------+----+
      | itemid | clock | value | ns |
      +-----------+------------+---------+----+
      | 300161484 | 1545404400 | 1.9616 | 0 |
      | 300161484 | 1545379200 | 2.3494 | 0 |
      | 300161484 | 1545382800 | 2.7355 | 0 |
      | 300161484 | 1545386400 | 3.3068 | 0 |
      | 300161484 | 1545390000 | 3.2508 | 0 |
      | 300161484 | 1545393600 | 4.2648 | 0 |
      | 300161484 | 1545397200 | 4.0263 | 0 |
      | 300161484 | 1545400800 | 2.7983 | 0 |
      | 300161485 | 1545404400 | 16.8910 | 0 |
      | 300161485 | 1545379200 | 20.5173 | 0 |
      +-----------+------------+---------+----+
    • history_log

      history_log 表存放信息类型为日志的监控项历史数据,类型在配置监控项是指定

      MariaDB [rtm]> desc history_log;
      +------------+---------------------+------+-----+---------+-------+
      | Field | Type | Null | Key | Default | Extra |
      +------------+---------------------+------+-----+---------+-------+
      | id | bigint(20) unsigned | NO | PRI | NULL | |
      | itemid | bigint(20) unsigned | NO | MUL | NULL | |
      | clock | int(11) | NO | | 0 | |
      | timestamp | int(11) | NO | | 0 | |
      | source | varchar(64) | NO | | | |
      | severity | int(11) | NO | | 0 | |
      | value | text | NO | | NULL | |
      | logeventid | int(11) | NO | | 0 | |
      | ns | int(11) | NO | | 0 | |
      +------------+---------------------+------+-----+---------+-------+
    • history_str

      history_str 表存放信息类型为字符的监控项历史数据,类型在配置监控项是指定

      MariaDB [rtm]> desc history_str;
      +--------+---------------------+------+-----+---------+-------+
      | Field | Type | Null | Key | Default | Extra |
      +--------+---------------------+------+-----+---------+-------+
      | itemid | bigint(20) unsigned | NO | MUL | NULL | |
      | clock | int(11) | NO | | 0 | |
      | value | varchar(255) | NO | | | |
      | ns | int(11) | NO | | 0 | |
      +--------+---------------------+------+-----+---------+-------+ MariaDB [rtm]> select * from history_str limit 2\G;
      *************************** 1. row ***************************
      itemid: 23307
      clock: 1545384507
      value: localhost.localdomain
      ns: 410719216
      *************************** 2. row ***************************
      itemid: 23312
      clock: 1545384512
      value: Linux localhost.localdomain 3.10.0-862.el7.x86_64 #1 SMP Fri Apr 20 16:44:24 UTC 2018 x86_64
      ns: 411996428
    • history_text

      history_text 表存放信息类型为文本的监控项历史数据,类型在配置监控项是指定

      MariaDB [rtm]> desc history_text;
      +--------+---------------------+------+-----+---------+-------+
      | Field | Type | Null | Key | Default | Extra |
      +--------+---------------------+------+-----+---------+-------+
      | id | bigint(20) unsigned | NO | PRI | NULL | |
      | itemid | bigint(20) unsigned | NO | MUL | NULL | |
      | clock | int(11) | NO | | 0 | |
      | value | text | NO | | NULL | |
      | ns | int(11) | NO | | 0 | |
      +--------+---------------------+------+-----+---------+-------+ MariaDB [rtm]> select * from history_text limit 10;
      +---------+--------+------------+---------------------+-----------+
      | id | itemid | clock | value | ns |
      +---------+--------+------------+---------------------+-----------+
      | 1937748 | 30436 | 1545381354 | 10/11/2017 14:28:06 | 892072527 |
      | 1937749 | 28311 | 1545381364 | N/A | 146021861 |
      | 1937750 | 27186 | 1545381374 | N/A | 934199968 |
      | 1937751 | 26936 | 1545381376 | N/A | 146546842 |
      | 1937752 | 28936 | 1545381378 | N/A | 189324808 |
      | 1937753 | 24686 | 1545381380 | N/A | 89381118 |
      | 1937754 | 25061 | 1545381383 | N/A | 484549259 |
      | 1937755 | 28061 | 1545381385 | N/A | 699330874 |
      | 1937756 | 27061 | 1545381389 | N/A | 559602805 |
      | 1937757 | 30686 | 1545381391 | N/A | 303467948 |
      +---------+--------+------------+---------------------+-----------+
    • history_uint

      history_unit 表存放信息类型为数字(无正负)的监控项历史数据,类型在配置监控项是指定

      MariaDB [rtm]> desc history_uint;
      +--------+---------------------+------+-----+---------+-------+
      | Field | Type | Null | Key | Default | Extra |
      +--------+---------------------+------+-----+---------+-------+
      | itemid | bigint(20) unsigned | NO | MUL | NULL | |
      | clock | int(11) | NO | | 0 | |
      | value | bigint(20) unsigned | NO | | 0 | |
      | ns | int(11) | NO | | 0 | |
      +--------+---------------------+------+-----+---------+-------+ MariaDB [rtm]> select * from history_uint limit 10;
      +-----------+------------+-------+----+
      | itemid | clock | value | ns |
      +-----------+------------+-------+----+
      | 100029541 | 1545404700 | 4311 | 0 |
      | 100029541 | 1545405000 | 4276 | 0 |
      | 100029541 | 1545405300 | 4242 | 0 |
      | 100029541 | 1545405600 | 4207 | 0 |
      | 100029541 | 1545405900 | 4172 | 0 |
      | 100029541 | 1545406200 | 4137 | 0 |
      | 100029541 | 1545406500 | 4102 | 0 |
      | 100029541 | 1545406800 | 4067 | 0 |
      | 100029541 | 1545407100 | 4032 | 0 |
      | 100029541 | 1545407400 | 3997 | 0 |
      +-----------+------------+-------+----+
  • trends相关表

    MariaDB [rtm]> show tables like 'trends%';
    +-------------------------+
    | Tables_in_rtm (trends%) |
    +-------------------------+
    | trends |
    | trends_uint |
    +-------------------------+
    • trends

      itemid: 监控项唯一标识id

      clock: 时间戳整数部分

      num: 该小时内用了多少数据用于计算平均值、最小值、最大值

      value_min: 趋势时间内最小值(趋势数据时间间隔为一小时)

      value_avg: 趋势时间内平均值(趋势数据时间间隔为一小时)

      value_max: 趋势时间内最大值(趋势数据时间间隔为一小时)

      MariaDB [rtm]> desc trends;
      +-----------+---------------------+------+-----+---------+-------+
      | Field | Type | Null | Key | Default | Extra |
      +-----------+---------------------+------+-----+---------+-------+
      | itemid | bigint(20) unsigned | NO | PRI | NULL | |
      | clock | int(11) | NO | PRI | 0 | |
      | num | int(11) | NO | | 0 | |
      | value_min | double(16,4) | NO | | 0.0000 | |
      | value_avg | double(16,4) | NO | | 0.0000 | |
      | value_max | double(16,4) | NO | | 0.0000 | |
      +-----------+---------------------+------+-----+---------+-------+ MariaDB [rtm]> select * from trends limit 10;
      +--------+------------+-----+-----------+-----------+-----------+
      | itemid | clock | num | value_min | value_avg | value_max |
      +--------+------------+-----+-----------+-----------+-----------+
      | 23252 | 1538211600 | 60 | 0.0000 | 0.0006 | 0.0169 |
      | 23252 | 1538215200 | 60 | 0.0000 | 0.0008 | 0.0169 |
      | 23252 | 1538218800 | 60 | 0.0000 | 0.0008 | 0.0169 |
      | 23252 | 1538222400 | 60 | 0.0000 | 0.0003 | 0.0169 |
      | 23252 | 1538226000 | 60 | 0.0000 | 0.0008 | 0.0169 |
      | 23252 | 1538229600 | 60 | 0.0000 | 0.0017 | 0.0508 |
      | 23252 | 1538233200 | 60 | 0.0000 | 0.0011 | 0.0169 |
      | 23252 | 1538236800 | 60 | 0.0000 | 0.0014 | 0.0169 |
      | 23252 | 1538240400 | 60 | 0.0000 | 0.0008 | 0.0169 |
      | 23252 | 1538244000 | 60 | 0.0000 | 0.0003 | 0.0169 |
      +--------+------------+-----+-----------+-----------+-----------+
    • trends_unit

      MariaDB [rtm]> desc trends_uint;
      +-----------+---------------------+------+-----+---------+-------+
      | Field | Type | Null | Key | Default | Extra |
      +-----------+---------------------+------+-----+---------+-------+
      | itemid | bigint(20) unsigned | NO | PRI | NULL | |
      | clock | int(11) | NO | PRI | 0 | |
      | num | int(11) | NO | | 0 | |
      | value_min | bigint(20) unsigned | NO | | 0 | |
      | value_avg | bigint(20) unsigned | NO | | 0 | |
      | value_max | bigint(20) unsigned | NO | | 0 | |
      +-----------+---------------------+------+-----+---------+-------+ MariaDB [rtm]> select * from trends_uint limit 10;
      +--------+------------+-----+-----------+-----------+-----------+
      | itemid | clock | num | value_min | value_avg | value_max |
      +--------+------------+-----+-----------+-----------+-----------+
      | 23271 | 1538211600 | 6 | 0 | 0 | 0 |
      | 23271 | 1538215200 | 6 | 0 | 0 | 0 |
      | 23271 | 1538218800 | 6 | 0 | 0 | 0 |
      | 23271 | 1538222400 | 6 | 0 | 0 | 0 |
      | 23271 | 1538226000 | 6 | 0 | 0 | 0 |
      | 23271 | 1538229600 | 6 | 0 | 0 | 0 |
      | 23271 | 1538233200 | 6 | 0 | 0 | 0 |
      | 23271 | 1538236800 | 6 | 0 | 0 | 0 |
      | 23271 | 1538240400 | 6 | 0 | 0 | 0 |
      | 23271 | 1538244000 | 6 | 0 | 0 | 0 |
      +--------+------------+-----+-----------+-----------+-----------+

zabbix历史数据相关表研究的更多相关文章

  1. C#实现 OPC历史数据存取研究

    来源:http://blog.csdn.net/gjack/article/details/5641794 C#实现 OPC历史数据存取研究 (原文)Research of Accessing the ...

  2. Zabbix 历史数据存储到 Elasticsearch

    Zabbix 历史数据存储到 Elasticsearch Zabbix 3.4.6 版本开始支持历史数据存储到 Elasticsearch, 早就想测试这个功能,最近有个需求需保存 zabbix 的历 ...

  3. 清理 zabbix 历史数据, 缩减 mysql 空间

    zabbix 由于历史数据过大, 因此导致磁盘空间暴涨,  下面是结局方法步骤 1. 停止 ZABBIX SERER 操作 [root@gd02-qa-plxt2-nodomain-web-95 ~] ...

  4. Zabbix历史数据清理

    特别提醒: a.文中测试的Zabbix版本为 3.0.3 . b.清理数据属于高危操作,请在测试环境中验证后再执行线上操作!!! 1.统计数据库中每个表所占的空间: mysql> SELECT ...

  5. zabbix历史数据全部清楚

    #这种方法会出现 监控项不可用的情况 1.停掉zabbix_server 2.重重名表 RENAME TABLE history to history_20180117; RENAME TABLE h ...

  6. zabbix监控历史数据清理

    2018/12/24 14:00:57  zabbix监控运行一段时间以后,会留下大量的历史监控数据,zabbix数据库一直在增大:可能会造成系统性能下降,查看历史数据室查询速度缓慢. zabbix里 ...

  7. zabbix的历史数据存储到elasticsearch中

    基本配置项 https://www.jianshu.com/p/bffca8128e8f 官方说这个实验性的功能支持es的版本是5.0.x - > 6.1.x,如果使用早期或更高版本的Elast ...

  8. zabbix报警逻辑初探

    zabbix报警逻辑初探 首先贴出一张网上找的一张关于zabbix报警相关表结构及表关联逻辑图: actions表 actions表对应前端配置是动作(actions) action由conditio ...

  9. zabbix通过jmx监控tomcat

    Zabbix版本: Zabbix 3.0.2 一.服务端配置 1.安装jdk(版本1.7.0_79) 安装与配置比较简单,过程省略.执行java -version命令,出现类似界面表示成功.   2. ...

随机推荐

  1. AKA “Project” Milestone

    Homework 6 (60 points)Due Thursday, April 25th at 11:59pm (via blackboard) AKA “Project” Milestone # ...

  2. 监听器 Listener

    监听器:监听某个对象状态的变化 被监听的对象:request.session.servletContext 监听对象的创建和销毁/对象属性的变化 ServletContext HttpSession ...

  3. 10、jeecg 默认为空的字段值是如何被填充的?

    1.前言 用过 jeecg 的小伙伴,在 jeecg 实体中常见下面几个字段: /**创建人名称*/ private java.lang.String createName; /**创建人登录名称*/ ...

  4. Linux系统(四)LVS集群负载均衡NAT模式

    序言 提到LVS,就从章文嵩博士开始吧,反正也不知道如何下笔来写这一篇.章大博士,读博时候创建这个lvs软件项目,但是他提倡开源精神,在用户的建议和反馈中,这个花了他两周时间开发的开源软件不断得到改建 ...

  5. 创建vs离线安装程序(不联网安装vs)

    https://blog.csdn.net/u013064585/article/details/80996933

  6. CentOS系统/tmp目录里面的文件默认保留多久

    一.CentOS系统/tmp目录里面的文件默认保留多久 CentOS6默认保留30天,CentOS7默认保留10天 一.CentOS7系统/tmp目录里面的文件默认保留多久 CentOS7默认保留10 ...

  7. Centos7 HyperLedger Fabric 1.4 生产环境部署

    Kafka生产环境部署案例采用三个排序(orderer)服务.四个kafka.三个zookeeper和四个节点(peer)组成,共准备八台服务器,每台服务器对应的服务如下所示: kafka案例网络拓扑 ...

  8. MySQL建表 TIMESTAMP 类型字段问题

    Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT ...

  9. Notification web 桌面消息推送

    var NotificationHandler = { isNotificationSupported: 'Notification' in window, isPermissionGranted: ...

  10. 图表管理账单的NABCD

    首先,我们团队的项目目标是记账本.就我个人理解,记账本中心功能有两项,第一,记录:第二,显示.而本篇博客主要描述用各种不同的图表来显示的NABCD. 首先是N(need),用户的需求就是我们的动力!利 ...