 Zabbix 6.2 ManualSNMPv2-MIB::snmpTrapOID.0 = IF-MIB::linkUp.0 The item value in Zabbix will be: 2022-08-05 10:54:432022-08-05 10:54:41 20220805.105441 UDP: [127.0.0.1]:44262->[127.0.0.1]:162 DISMAN-EVENT-MIB::sysUpTimeInstance Event date: 2018.01.02 Event age: 5m Event acknowledgment: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: host connection and power state", "enabled": true, "key": "alarm-1.host-2013", "time": "2022-06-27T05:27:38.759976Z", "overall_status": "red", "acknowledged": false }, { "name": "Host memory usage",0 码力 | 1689 页 | 22.82 MB | 1 年前3 Zabbix 6.2 ManualSNMPv2-MIB::snmpTrapOID.0 = IF-MIB::linkUp.0 The item value in Zabbix will be: 2022-08-05 10:54:432022-08-05 10:54:41 20220805.105441 UDP: [127.0.0.1]:44262->[127.0.0.1]:162 DISMAN-EVENT-MIB::sysUpTimeInstance Event date: 2018.01.02 Event age: 5m Event acknowledgment: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: host connection and power state", "enabled": true, "key": "alarm-1.host-2013", "time": "2022-06-27T05:27:38.759976Z", "overall_status": "red", "acknowledged": false }, { "name": "Host memory usage",0 码力 | 1689 页 | 22.82 MB | 1 年前3
 Zabbix 6.4 ManualSNMPv2-MIB::snmpTrapOID.0 = IF-MIB::linkUp.0 The item value in Zabbix will be: 260 2022-08-05 10:22:352022-08-05 10:22:33 20220805.102233 UDP: [127.0.0.1]:35736->[127.0.0.1]:162 DISMAN-EVENT-MIB::sysUpTimeInstance Event date: 2018.01.02 Event age: 5m Event acknowledgment: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: host connection and power state", "enabled": true, "key": "alarm-1.host-2013", "time": "2022-06-27T05:27:38.759976Z", "overall_status": "red", "acknowledged": false }, { "name": "Host memory usage",0 码力 | 1885 页 | 29.12 MB | 1 年前3 Zabbix 6.4 ManualSNMPv2-MIB::snmpTrapOID.0 = IF-MIB::linkUp.0 The item value in Zabbix will be: 260 2022-08-05 10:22:352022-08-05 10:22:33 20220805.102233 UDP: [127.0.0.1]:35736->[127.0.0.1]:162 DISMAN-EVENT-MIB::sysUpTimeInstance Event date: 2018.01.02 Event age: 5m Event acknowledgment: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: host connection and power state", "enabled": true, "key": "alarm-1.host-2013", "time": "2022-06-27T05:27:38.759976Z", "overall_status": "red", "acknowledged": false }, { "name": "Host memory usage",0 码力 | 1885 页 | 29.12 MB | 1 年前3
 Zabbix 7.0 ManualEvent date: 2018.01.02 Event age: 5m Event acknowledgment: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: host connection and power state", "enabled": true, "key": "alarm-1.host-2013", "time": "2022-06-27T05:27:38.759976Z", "overall_status": "red", "acknowledged": false }, { "name": "Host memory usage", "Default alarm to monitor host memory usage", "enabled": true, "key": "alarm-4.host-1004", "time": "2022-05-16T13:32:42.47863Z", "overall_status": "yellow", "acknowledged": false }, { // other alarms } ]0 码力 | 1949 页 | 31.91 MB | 1 年前3 Zabbix 7.0 ManualEvent date: 2018.01.02 Event age: 5m Event acknowledgment: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: host connection and power state", "enabled": true, "key": "alarm-1.host-2013", "time": "2022-06-27T05:27:38.759976Z", "overall_status": "red", "acknowledged": false }, { "name": "Host memory usage", "Default alarm to monitor host memory usage", "enabled": true, "key": "alarm-4.host-1004", "time": "2022-05-16T13:32:42.47863Z", "overall_status": "yellow", "acknowledged": false }, { // other alarms } ]0 码力 | 1949 页 | 31.91 MB | 1 年前3
 Zabbix 5.4 中文手册匹配服务器的时间。例如,如果一个监控项的时间戳 是 “10:30:50”,zabbix_sender 机器上的当前时间是 “10:40:03”,Zabbix server 主机的时间是”10:40:05”,那么该监控项的值将以 “10:30:52” 的时间戳存储在数据库中。 类似地,如果一个值首先发送到 Zabbix proxy,然后再将其发送到 Zabbix server,那么时间戳将首先会被调整以匹配 Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status:0 码力 | 2339 页 | 19.57 MB | 1 年前3 Zabbix 5.4 中文手册匹配服务器的时间。例如,如果一个监控项的时间戳 是 “10:30:50”,zabbix_sender 机器上的当前时间是 “10:40:03”,Zabbix server 主机的时间是”10:40:05”,那么该监控项的值将以 “10:30:52” 的时间戳存储在数据库中。 类似地,如果一个值首先发送到 Zabbix proxy,然后再将其发送到 Zabbix server,那么时间戳将首先会被调整以匹配 Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status:0 码力 | 2339 页 | 19.57 MB | 1 年前3
 Zabbix 6.0 ManualSNMPv2-MIB::snmpTrapOID.0 = IF-MIB::linkUp.0 The item value in Zabbix will be: 2022-08-05 10:22:352022-08-05 10:22:33 20220805.102233 UDP: [127.0.0.1]:35736->[127.0.0.1]:162 DISMAN-EVENT-MIB::sysUpTimeInstance Event date: 2018.01.02 Event age: 5m Event acknowledgment: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: entity as well). Export format Export format in YAML: zabbix_export: version: '6.0' date: '2023-05-03T11:24:04Z' groups: - uuid: dc579cd7a1a34222933f24f52a68bcd8 name: 'Linux servers' hosts: - host:0 码力 | 1681 页 | 23.19 MB | 1 年前3 Zabbix 6.0 ManualSNMPv2-MIB::snmpTrapOID.0 = IF-MIB::linkUp.0 The item value in Zabbix will be: 2022-08-05 10:22:352022-08-05 10:22:33 20220805.102233 UDP: [127.0.0.1]:35736->[127.0.0.1]:162 DISMAN-EVENT-MIB::sysUpTimeInstance Event date: 2018.01.02 Event age: 5m Event acknowledgment: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: entity as well). Export format Export format in YAML: zabbix_export: version: '6.0' date: '2023-05-03T11:24:04Z' groups: - uuid: dc579cd7a1a34222933f24f52a68bcd8 name: 'Linux servers' hosts: - host:0 码力 | 1681 页 | 23.19 MB | 1 年前3
 Zabbix 3.4 Manualon zabbix_sender’s machine is ”10:40:03”, and the current time on Zabbix server’s machine is ”10:40:05”, then the item’s value will be stored in the database with a timestamp of ”10:30:52”. Similarly 2014.01.02 374 Event age: 5m Event acknowledgement: Yes Event acknowledgement history: 2014.01.02 13:05:51 "John Smith (Admin)" -acknowledged- Recovery: Event ID: 21896 Event value: 0 Event status: OK Zabbix 3.4 Manualon zabbix_sender’s machine is ”10:40:03”, and the current time on Zabbix server’s machine is ”10:40:05”, then the item’s value will be stored in the database with a timestamp of ”10:30:52”. Similarly 2014.01.02 374 Event age: 5m Event acknowledgement: Yes Event acknowledgement history: 2014.01.02 13:05:51 "John Smith (Admin)" -acknowledged- Recovery: Event ID: 21896 Event value: 0 Event status: OK- 3.4 472- 2016-10-05T08:16:20Z - Server_(64) - 1 - iVBOR 0 码力 | 1136 页 | 15.03 MB | 1 年前3
 Zabbix 4.4 中文手册匹配服务器的时间。例如,如果一个监控项的时间戳 是 “10:30:50”,zabbix_sender 机器上的当前时间是 “10:40:03”,Zabbix server 主机的时间是”10:40:05”,那么该监控项的值将以 “10:30:52” 的时间戳存储在数据库中。 类似地,如果一个值首先发送到 Zabbix proxy,然后再将其发送到 Zabbix server,那么时间戳将首先会被调整以匹配 Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" 716 Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event0 码力 | 1850 页 | 13.52 MB | 1 年前3 Zabbix 4.4 中文手册匹配服务器的时间。例如,如果一个监控项的时间戳 是 “10:30:50”,zabbix_sender 机器上的当前时间是 “10:40:03”,Zabbix server 主机的时间是”10:40:05”,那么该监控项的值将以 “10:30:52” 的时间戳存储在数据库中。 类似地,如果一个值首先发送到 Zabbix proxy,然后再将其发送到 Zabbix server,那么时间戳将首先会被调整以匹配 Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" 716 Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event0 码力 | 1850 页 | 13.52 MB | 1 年前3
 Zabbix 5.2 Manual匹配服务器的时间。例如,如果一个监控项的时间戳 是 “10:30:50”,zabbix_sender 机器上的当前时间是 “10:40:03”,Zabbix server 主机的时间是”10:40:05”,那么该监控项的值将以 “10:30:52” 的时间戳存储在数据库中。 类似地,如果一个值首先发送到 Zabbix proxy,然后再将其发送到 Zabbix server,那么时间戳将首先会被调整以匹配 Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status:0 码力 | 1725 页 | 11.53 MB | 1 年前3 Zabbix 5.2 Manual匹配服务器的时间。例如,如果一个监控项的时间戳 是 “10:30:50”,zabbix_sender 机器上的当前时间是 “10:40:03”,Zabbix server 主机的时间是”10:40:05”,那么该监控项的值将以 “10:30:52” 的时间戳存储在数据库中。 类似地,如果一个值首先发送到 Zabbix proxy,然后再将其发送到 Zabbix server,那么时间戳将首先会被调整以匹配 Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status: Event date: 2018.01.02 Event age: 5m Event acknowledgement: Yes Event update history: 2018.01.02 13:05:51 "John Smith (Admin)" Actions: acknowledged. Recovery: Event ID: 21896 Event value: 0 Event status:0 码力 | 1725 页 | 11.53 MB | 1 年前3
 Zabbix 2.4 Manualon zabbix_sender’s machine is ”10:40:03”, and the current time on Zabbix server’s machine is ”10:40:05”, then the item’s value will be stored in the database with a timestamp of ”10:30:52”. Similarly date: 2014.01.02 Event age: 5m Event acknowledgement: Yes Event acknowledgement history: 2014.01.02 13:05:51 "John Smith (Admin)" -acknowledged- Recovery: Event ID: 21896 263 Event value: 0 Event status:0 码力 | 910 页 | 10.81 MB | 1 年前3 Zabbix 2.4 Manualon zabbix_sender’s machine is ”10:40:03”, and the current time on Zabbix server’s machine is ”10:40:05”, then the item’s value will be stored in the database with a timestamp of ”10:30:52”. Similarly date: 2014.01.02 Event age: 5m Event acknowledgement: Yes Event acknowledgement history: 2014.01.02 13:05:51 "John Smith (Admin)" -acknowledged- Recovery: Event ID: 21896 263 Event value: 0 Event status:0 码力 | 910 页 | 10.81 MB | 1 年前3
 Zabbix 2.2 Manualon Zabbix sender’s machine is ”10:40:03”, and the current time on Zabbix server’s machine is ”10:40:05”, then the item’s value will be stored in the database with a timestamp of ”10:30:52”. Similarly, date: 2014.01.02 Event age: 5m Event acknowledgement: Yes Event acknowledgement history: 2014.01.02 13:05:51 "John Smith (Admin)" -acknowledged- Recovery: 270 Event ID: 21896 Event value: 0 Event status:0 码力 | 918 页 | 11.28 MB | 1 年前3 Zabbix 2.2 Manualon Zabbix sender’s machine is ”10:40:03”, and the current time on Zabbix server’s machine is ”10:40:05”, then the item’s value will be stored in the database with a timestamp of ”10:30:52”. Similarly, date: 2014.01.02 Event age: 5m Event acknowledgement: Yes Event acknowledgement history: 2014.01.02 13:05:51 "John Smith (Admin)" -acknowledged- Recovery: 270 Event ID: 21896 Event value: 0 Event status:0 码力 | 918 页 | 11.28 MB | 1 年前3
共 25 条
- 1
- 2
- 3













