('17810','{21059}=2','Morningstar TriStar MPPT 600V: Status: Device has "rs232SerialToMeterBridge" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','4d8f0244f8d047bc8730ffc2f02a976d',''),
('17811','{21060}=2','Morningstar TriStar MPPT 600V: Status: Device has "rtsDisconnected" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','6c125b8f681b47a99f7535292bd0507c',''),
('17812','{21061}=2','Morningstar TriStar MPPT 600V: Status: Device has "rtsShorted" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','abad398631f34dac8094e4bcd14e3613',''),
('17813','{21062}=2','Morningstar TriStar MPPT 600V: Status: Device has "slave" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','6824d221feb042da860248a4b418105c',''),
('17814','{21063}=2','Morningstar TriStar MPPT 600V: Status: Device has "softwareFault" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','56adf438e90f410497246b27b6da49f4',''),
('17815','({32310}>0 and {32310}<10m) or ({32310}=0 and {32311}<10m)','Morningstar TriStar MPPT 600V: Status: Device has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Morningstar TriStar MPPT 600V: Status: Device has been restarted (uptime < 10m)','5393dee9b39d438a8c1553a0be0fb0f2',''),
('17816','{21065}=1','Morningstar TriStar MPPT 600V: Status: Failed to fetch data','','0','2','Zabbix has not received data for items for the last 5 minutes.',NULL,'0','0','0','','0','','1','','0','Morningstar TriStar MPPT 600V: Status: Failed to fetch data (or no data for 5m)','c4f0ea9e18884bc0b546933871017098',''),
('17817','{21066}>{$BATTERY.TEMP.MAX.CRIT}','Morningstar TriStar MPPT 600V: Temperature: Critically high battery temperature','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar MPPT 600V: Temperature: Critically high battery temperature (over {$BATTERY.TEMP.MAX.CRIT}C for 5m)','bc117de353304889980c7836603abb0d',''),
('17818','{21067}<{$BATTERY.TEMP.MIN.CRIT}','Morningstar TriStar MPPT 600V: Temperature: Critically low battery temperature','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar MPPT 600V: Temperature: Critically low battery temperature (below {$BATTERY.TEMP.MIN.WARN}C for 5m)','25a8f16d632940c3a2c994a9f2a76851',''),
('17819','{21068}>{$BATTERY.TEMP.MAX.WARN}','Morningstar TriStar MPPT 600V: Temperature: High battery temperature','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar MPPT 600V: Temperature: High battery temperature (over {$BATTERY.TEMP.MAX.WARN}C for 5m)','db1152c815c84d208be0db3dac63acb4',''),
('17820','{21069}<{$BATTERY.TEMP.MIN.WARN}','Morningstar TriStar MPPT 600V: Temperature: Low battery temperature','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar MPPT 600V: Temperature: Low battery temperature (below {$BATTERY.TEMP.MIN.WARN}C for 5m)','9c331fb9a30b4867a3e16acd7e9f8983',''),
('17825','{21074}={$CHARGE.STATE.CRIT}','Morningstar TriStar MPPT: Battery: Device charge in critical state','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','6c6371d2476246789d23404e068e5179',''),
('17826','{21075}={$CHARGE.STATE.WARN}','Morningstar TriStar MPPT: Battery: Device charge in warning state','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','65bdeac02fed4febae857f571319bf37',''),
('17827','{21076}=2','Morningstar TriStar MPPT: Status: Device has "batterySense" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','b073c972bb64463aaee85c6129fad319',''),
('17828','{21077}=2','Morningstar TriStar MPPT: Status: Device has "batterySenseDisconnected" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','80a2d0a457024c22b39f0fcd45992e1e',''),
('17829','{21078}=2','Morningstar TriStar MPPT: Status: Device has "controllerWasReset" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','bac1cc54818245f9baa8dc07ddc0f850',''),
('17830','{21079}=2','Morningstar TriStar MPPT: Status: Device has "currentLimit" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','86c2dfb7b0984eaab02f47c58337f468',''),
('17831','{21080}=2','Morningstar TriStar MPPT: Status: Device has "currentOffset" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','dd000390277a4e848a3236501817addf',''),
('17832','{21081}=2','Morningstar TriStar MPPT: Status: Device has "heatsinkTempSensorOpen" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','650ecb9c06464937a3f797e73a3d756d',''),
('17833','{21082}=2','Morningstar TriStar MPPT: Status: Device has "heatsinkTempSensorShorted" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','5999a4b6c49a4dabb6350d826b01e646',''),
('17834','{21083}=2','Morningstar TriStar MPPT: Status: Device has "highArrayVCurrentLimit" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','7331337c7ffb4933bca3982614657912',''),
('17835','{21084}=2','Morningstar TriStar MPPT: Status: Device has "highTemperatureCurrentLimit" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','82a2e0adba7444c6945666fcb9430808',''),
('17836','{21085}=2','Morningstar TriStar MPPT: Status: Device has "highVoltageDisconnect" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','b1f6d22d205e449a811da905e679800f',''),
('17837','{21086}=2','Morningstar TriStar MPPT: Status: Device has "maxAdcValueReached" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','e3ce50b9b696486f945ee5a4c1a7a753',''),
('17838','{21087}=2','Morningstar TriStar MPPT: Status: Device has "mosfetSOpen" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','1536cf07556b4cddb62186030a4321ca',''),
('17839','{21088}=2','Morningstar TriStar MPPT: Status: Device has "p12VoltageReferenceOff" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','136621f032544ea8af5e86a14ec03cb6',''),
('17840','{21089}=2','Morningstar TriStar MPPT: Status: Device has "rtsDisconnected" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','62ecaaf59a984b2999d13540c5220470',''),
('17841','{21090}=2','Morningstar TriStar MPPT: Status: Device has "rtsMiswire" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','12037d207b3f413198594877cc7a3862',''),
('17842','{21091}=2','Morningstar TriStar MPPT: Status: Device has "rtsShorted" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','330f9dfe6ea34b17bcf4cac2c908d78c',''),
('17843','{21092}=2','Morningstar TriStar MPPT: Status: Device has "systemMiswire" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','fba13770ff67433489ec95d62b65d4b5',''),
('17844','{21093}=2','Morningstar TriStar MPPT: Status: Device has "uncalibrated" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','de6208b4474f4743ad99444fd7eb135d',''),
('17845','{21094}=2','Morningstar TriStar MPPT: Status: Device has "arrayHvd" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','2a1b5a65311144d69c03255336f9f15f',''),
('17846','{21095}=2','Morningstar TriStar MPPT: Status: Device has "batteryHvd" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','f837f0839967493bb0e38b21000f5e9a',''),
('17847','{21096}=2','Morningstar TriStar MPPT: Status: Device has "customSettingsEdit" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','05b70b4be5554dd5ac2c65af04d79986',''),
('17848','{21097}=2','Morningstar TriStar MPPT: Status: Device has "dipSwitchChange" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','24ecb8842ea84a82b4d05a4e85150c55',''),
('17849','{21098}=2','Morningstar TriStar MPPT: Status: Device has "eepromRetryLimit" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','008d82bc793b49afa6cd37d038c837fe',''),
('17850','{21099}=2','Morningstar TriStar MPPT: Status: Device has "fetShort" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','71dbbf441c234dcfbf014fc043bf5d3a',''),
('17851','{21100}=2','Morningstar TriStar MPPT: Status: Device has "overcurrent" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','c100ec68ddaf40e6964ba2598141daa7',''),
('17852','{21101}=2','Morningstar TriStar MPPT: Status: Device has "rtsDisconnected" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','435df7ebe3e047ffada64dcf7e69148a',''),
('17853','{21102}=2','Morningstar TriStar MPPT: Status: Device has "rtsShorted" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','88443c84eaa0415db976e7a5d6c1dec4',''),
('17854','{21103}=2','Morningstar TriStar MPPT: Status: Device has "slaveControlTimeout" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','b19111ec08094dbca30a804011b02ed2',''),
('17855','{21104}=2','Morningstar TriStar MPPT: Status: Device has "softwareFault" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','0d90cab800ad4bbcbf880c157a7a9dae',''),
('17856','({32312}>0 and {32312}<10m) or ({32312}=0 and {32313}<10m)','Morningstar TriStar MPPT: Status: Device has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Morningstar TriStar MPPT: Status: Device has been restarted (uptime < 10m)','aab5be196ac64dc69883c3109fcd094f',''),
('17857','{21106}=1','Morningstar TriStar MPPT: Status: Failed to fetch data','','0','2','Zabbix has not received data for items for the last 5 minutes.',NULL,'0','0','0','','0','','1','','0','Morningstar TriStar MPPT: Status: Failed to fetch data (or no data for 5m)','db9317cb9a6645d2bd8f4760f7579c17',''),
('17858','{21107}>{$BATTERY.TEMP.MAX.CRIT}','Morningstar TriStar MPPT: Temperature: Critically high battery temperature','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar MPPT: Temperature: Critically high battery temperature (over {$BATTERY.TEMP.MAX.CRIT}C for 5m)','5ec1c2e4786048fc889a37a12a2f4ad6',''),
('17859','{21108}<{$BATTERY.TEMP.MIN.CRIT}','Morningstar TriStar MPPT: Temperature: Critically low battery temperature','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar MPPT: Temperature: Critically low battery temperature (below {$BATTERY.TEMP.MIN.WARN}C for 5m)','84c059ff133f4f4d8145615c0a98eb50',''),
('17860','{21109}>{$BATTERY.TEMP.MAX.WARN}','Morningstar TriStar MPPT: Temperature: High battery temperature','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar MPPT: Temperature: High battery temperature (over {$BATTERY.TEMP.MAX.WARN}C for 5m)','11d2b988cfec425c9ffb082e9c78490d',''),
('17861','{21110}<{$BATTERY.TEMP.MIN.WARN}','Morningstar TriStar MPPT: Temperature: Low battery temperature','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar MPPT: Temperature: Low battery temperature (below {$BATTERY.TEMP.MIN.WARN}C for 5m)','46122992e8a04c7bb7a8c8037a2da74a',''),
('17866','{21115}=2','Morningstar TriStar PWM: Status: Device has "batterySense" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','121d47c6bbdd45bca261df2e01ea41c6',''),
('17867','{21116}=2','Morningstar TriStar PWM: Status: Device has "batterySenseDisconnected" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','fd2d9290144143d39bb5a3cf0a2d261f',''),
('17868','{21117}=2','Morningstar TriStar PWM: Status: Device has "currentLimit" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','83d5b8d52acd4e21ac6d3a9cf05dcd04',''),
('17869','{21118}=2','Morningstar TriStar PWM: Status: Device has "currentOffset" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','d9529a4372d848038e6ee561d62e9f22',''),
('17870','{21119}=2','Morningstar TriStar PWM: Status: Device has "diversionLoadNearMax" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','5f3983acc1cc417e860c1305b11c15ea',''),
('17871','{21120}=2','Morningstar TriStar PWM: Status: Device has "heatsinkTempSensorOpen" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','878e04df7e7b416bb0d2213b5dbb80e6',''),
('17872','{21121}=2','Morningstar TriStar PWM: Status: Device has "heatsinkTempSensorShorted" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','c642ed9496ce4322809c7142d32929a5',''),
('17873','{21122}=2','Morningstar TriStar PWM: Status: Device has "highVoltageDisconnect" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','532421fe17bf4732a01a6990e34e649a',''),
('17874','{21123}=2','Morningstar TriStar PWM: Status: Device has "loadDisconnectState" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','ae90e8034baf4b21906d56d18bfa4da8',''),
('17875','{21124}=2','Morningstar TriStar PWM: Status: Device has "mosfetSOpen" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','8d8b721c6dee40499b29bee44b21589a',''),
('17876','{21125}=2','Morningstar TriStar PWM: Status: Device has "p12VoltageReferenceOff" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','8cda8e5773de4583b9baa6a6e542e32c',''),
('17877','{21126}=2','Morningstar TriStar PWM: Status: Device has "rtsDisconnected" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','1b6192b8ca364c229b35ba6de89ad56b',''),
('17878','{21127}=2','Morningstar TriStar PWM: Status: Device has "rtsMiswire" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','176de77a142d45a3ac39ea42989e209c',''),
('17879','{21128}=2','Morningstar TriStar PWM: Status: Device has "rtsShorted" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','f63029eabc8e498ea7e6336d312ac169',''),
('17880','{21129}=2','Morningstar TriStar PWM: Status: Device has "systemMiswire" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','480b69c1febf45a2971788c2f967c45d',''),
('17881','{21130}=2','Morningstar TriStar PWM: Status: Device has "tristarHot" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','4a287e4086c4458aaa3dc48bbb8ee219',''),
('17882','{21131}=2','Morningstar TriStar PWM: Status: Device has "uncalibrated" alarm flag','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','de665482d2574730a3a839948dd730ea',''),
('17883','{21132}=2','Morningstar TriStar PWM: Status: Device has "customSettingsEdit" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','514b041aebdd4ddb8ab2d1222c0ef295',''),
('17884','{21133}=2','Morningstar TriStar PWM: Status: Device has "dipSwitchChange" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','1a40ce8b87f04ab1b4f30387e9ce2d9d',''),
('17885','{21134}=2','Morningstar TriStar PWM: Status: Device has "externalShort" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','49b120c3933c43b1b7f5c77f7b359997',''),
('17886','{21135}=2','Morningstar TriStar PWM: Status: Device has "highVoltageDisconnect" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','f063b9f717c44ab988db7ac95bfca68f',''),
('17887','{21136}=2','Morningstar TriStar PWM: Status: Device has "mosfetSShorted" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','468716d748f1470cb764ce1af922164d',''),
('17888','{21137}=2','Morningstar TriStar PWM: Status: Device has "overcurrent" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','b6f65dfca421490eafff48991cdf1e3b',''),
('17889','{21138}=2','Morningstar TriStar PWM: Status: Device has "reset" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','73561a5765694633b1dc0ef1b1f60fd4',''),
('17890','{21139}=2','Morningstar TriStar PWM: Status: Device has "rtsDisconnected" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','d14c7d928f57448390c2b4c588a28c65',''),
('17891','{21140}=2','Morningstar TriStar PWM: Status: Device has "rtsShorted" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','d94067598c234968b4929404067eff86',''),
('17892','{21141}=2','Morningstar TriStar PWM: Status: Device has "softwareFault" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','886b18bee7cd4f8eb454973e2d2ae59f',''),
('17893','{21142}=2','Morningstar TriStar PWM: Status: Device has "systemMiswire" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','2e520cdafaaa4eefad5ebea71819c3a6',''),
('17894','{21143}=2','Morningstar TriStar PWM: Status: Device has "tristarHot" faults flag','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','041be44e639d4d1eadb15230a678e278',''),
('17895','({32314}>0 and {32314}<10m) or ({32314}=0 and {32315}<10m)','Morningstar TriStar PWM: Status: Device has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Morningstar TriStar PWM: Status: Device has been restarted (uptime < 10m)','f0549419f015448497cd7d15a2bf96fa',''),
('17896','{21145}=1','Morningstar TriStar PWM: Status: Failed to fetch data','','0','2','Zabbix has not received data for items for the last 5 minutes.',NULL,'0','0','0','','0','','1','','0','Morningstar TriStar PWM: Status: Failed to fetch data (or no data for 5m)','64aa2a79fe854def8e179a4d27790417',''),
('17897','{21146}>{$BATTERY.TEMP.MAX.CRIT}','Morningstar TriStar PWM: Temperature: Critically high battery temperature','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar PWM: Temperature: Critically high battery temperature (over {$BATTERY.TEMP.MAX.CRIT}C for 5m)','e759b90e2bf44bbb8e5efe5b9e458e40',''),
('17898','{21147}<{$BATTERY.TEMP.MIN.CRIT}','Morningstar TriStar PWM: Temperature: Critically low battery temperature','','0','4','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar PWM: Temperature: Critically low battery temperature (below {$BATTERY.TEMP.MIN.WARN}C for 5m)','e57f335f657d45768509f139d31dcdae',''),
('17899','{21148}>{$BATTERY.TEMP.MAX.WARN}','Morningstar TriStar PWM: Temperature: High battery temperature','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar PWM: Temperature: High battery temperature (over {$BATTERY.TEMP.MAX.WARN}C for 5m)','7d1444dba9334e91ad425a6f2ff9fef9',''),
('17900','{21149}<{$BATTERY.TEMP.MIN.WARN}','Morningstar TriStar PWM: Temperature: Low battery temperature','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Morningstar TriStar PWM: Temperature: Low battery temperature (below {$BATTERY.TEMP.MIN.WARN}C for 5m)','14fe4a22b28c4d08a24da51a54e36e81',''),
('17929','{24442}>0 and {24443}<>{24444}','NetApp FAS3220: Number of failed disks has changed','','0','2',E'{{ITEM.LASTVALUE2}.regsub("(.*)", \\1)}',NULL,'1','0','1','{24442}=0','0','','0','Current value: {ITEM.LASTVALUE1}','0','','3e2d95918f364248ae07a2e436a986a0',''),
('17953','{21231}=0 and length({21232})>0','Jenkins: Disk space is too low','','0','2',E'Jenkins disk space monitors are reporting the disk space as less than the configured threshold. The message will reference the first node which fails this check.
Health check message: {{ITEM.LASTVALUE2}.regsub("(.*)",\\1)}',NULL,'0','0','0','','0','','0','','0','','d79dc9c1dab142d18791172e6df0a4e9',''),
('17954','{21233}=0 and length({21234})>0','Jenkins: One or more Jenkins plugins failed to start','','0','1',E'A failure is typically indicative of a potential issue within the Jenkins installation that will either be solved by explicitly disabling the failing plugin(s) or by resolving the corresponding plugin dependency issues.
Health check message: {{ITEM.LASTVALUE2}.regsub("(.*)",\\1)}',NULL,'0','0','0','','0','','1','','0','','121e23bd172d447cb975595685495a93',''),
('17955','{21235}=0 and length({21236})>0','Jenkins: Temporary space is too low','','0','2',E'Jenkins temporary space monitors are reporting the temporary space as less than the configured threshold. The message will reference the first node which fails this check.
Health check message: {{ITEM.LASTVALUE2}.regsub("(.*)",\\1)}',NULL,'0','0','0','','0','','0','','0','','34de8503a2c84fffb1beb701a4a991ab',''),
('17956','{21237}=0 and length({21238})>0','Jenkins: There are deadlocked threads in Jenkins master JVM','','0','2',E'There are any deadlocked threads in the Jenkins master JVM.
Health check message: {{ITEM.LASTVALUE2}.regsub(''(.*)'',\\1)}',NULL,'0','0','0','','0','','0','','0','','f0a09eb0743948bb8f52a4c28aa728c5',''),
('17957','{21239}>{$JENKINS.FILE_DESCRIPTORS.MAX.WARN}','Jenkins: Current number of used files is too high','','0','2','',NULL,'0','0','0','','0','','0','','0','Jenkins: Current number of used files is too high (over {$JENKINS.FILE_DESCRIPTORS.MAX.WARN}% for 5m)','5ec22ac264d445769039bd4c13e41bf7',''),
('17958','{21240}=0','Jenkins: Service has no online nodes','','0','3','',NULL,'0','0','0','','0','','0','','0','','4cee7d0f5faf4595a67c6c0e33153f4d',''),
('17959','{21241}=0','Jenkins: Service is down','','0','3','',NULL,'0','0','0','','0','','1','','0','','ae12ac7aa5c54858a794eb8fc888f90c',''),
('17960','{21242}<10m','Jenkins: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Jenkins: {HOST.NAME} has been restarted (uptime < 10m)','7d20942598a648ebb2e03f9acdb3e5e3',''),
('17961','{23222}<>{23223} and length({23224})>0','Jenkins: Version has changed','','0','1','The Jenkins version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Jenkins: Version has changed (new version: {ITEM.VALUE})','3dd66b51ed1b4fc2a250daf3e9999e4f',''),
('17965','{21250}=1 or
{21251}=1 or
{21252}=1','Hikvision: Authorisation error','','0','2','Check the correctness of the authorization data',NULL,'0','0','0','','0','','1','','0','','2bd6d99edd0f4b2d8045e43e4586b637',''),
('17966','{21253}=2 or
{21254}=2 or
{21255}=2','Hikvision: Error receiving data','','0','2','Check the availability of the HTTP port',NULL,'0','0','0','','0','','1','','0','','58b5d210fe24434b9aaa365fba764742',''),
('17967','{21256}>{$CPU.UTIL.CRIT}','Hikvision: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Hikvision: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','0ae4dbcc05544fb7b67183fcf3b9654b',''),
('17968','{23325}<>{23326} and length({23327})>0','Hikvision: Version has changed','','0','1','Hikvision camera version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Hikvision: Version has changed (new version: {ITEM.VALUE})','3c0b5a0046894a54803cd984cda13fa2',''),
('17970','{23328}<>{23329} and length({23330})>0','Hikvision: Camera has been replaced','','0','1','Camera serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Hikvision: Camera has been replaced (new serial number received)','281999cbd6324aacbbb86b4945000c60',''),
('17971','{21262}<10m','Hikvision: Camera has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Hikvision: Camera has been restarted (uptime < 10m)','f46b43fe9b354990929e7fdb80b792ec',''),
('18027','{21341}<>200','MS SharePoint: Error getting directory structure.','','0','2','Error getting directory structure. Check the Zabbix server log for more details.',NULL,'0','0','0','','0','','0','','0','','ed1d66a1410e4af79af462e749ce979b',''),
('18028','{21342}>2000','MS SharePoint: Server responds slowly to API request','','0','2','',NULL,'0','0','0','','0','','0','','0','','9e5bcc08d5f040de86afa38f5a653dd7',''),
('18029','{33354}>"{$SHAREPOINT.MAX_HEALTH_SCORE}"','MS SharePoint: Bad health score','','0','3','',NULL,'0','0','0','','0','','0','','0','','3a0451e3edda4a73aded57aa254fd813',''),
('18031','(now() - {48014} < 10m) and {48015} = 1','VMware Guest: VM has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','VMware Guest: VM has been restarted (uptime < 10m)','da703e83e2e146569c173fd9bc6988dd',''),
('18033','{21348}>{$MEMORY.UTIL.MAX}','Hikvision: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Hikvision: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','62cfa0b87f234f1cb67b9b5b6b2fa8f2',''),
('18108','{21566}>{$MEMORY.UTIL.MAX}','Alcatel TiMOS: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Alcatel TiMOS: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','a22f13e245b944e991c2c9850a731a3c',''),
('18109','{21567}>{$MEMORY.UTIL.MAX}','Brocade FC: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Brocade FC: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','1991ae08b008488380db02160b15160e',''),
('18125','{21583}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','e4b4ba5ec80c4d83adbb10739edf4574',''),
('18126','{21584}>{$MEMORY.UTIL.MAX}','Netgear Fastpath: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Netgear Fastpath: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','21c1a017dcc14148a9020207a6fd7488',''),
('18127','{21585}>{$MEMORY.UTIL.MAX}','QTech QSW: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','QTech QSW: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','082a768e190d4e8e97e0857cd3412ea1',''),
('18129','{21587}>{$MEMORY.UTIL.MAX}','Ubiquiti AirOS: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Ubiquiti AirOS: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','30c0c80ae6df45bb96c434016e394bba',''),
('18150','{30967}<{$SWAP.PFREE.MIN.WARN} and {30968}>0','Linux: High swap space usage','','0','2','If there is no swap configured, this trigger is ignored.',NULL,'0','0','0','','0','','0','Free: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Linux: High swap space usage (less than {$SWAP.PFREE.MIN.WARN}% free)','16e6a4d340164dee9379a3fc0aac0576',''),
('18152','{21637}>{$MEMORY.UTIL.MAX}','Linux: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Linux: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','72304b3a167e41ccbcdb75568c65294a',''),
('18183','{24404}<>{24405} and length({24406})>0','Huawei OceanStor 5300 V5: Storage version has been changed','','0','1','OceanStor 5300 V5 version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Huawei OceanStor 5300 V5: Version has changed (new version: {ITEM.VALUE})','b6eb791cc14644dfb0a69a2cce150ab1',''),
('18221','{21744}/({21745}+{21746})*100>{$MONGODB.CONNS.PCT.USED.MAX.WARN}','MongoDB node: Total number of open connections is too high','','0','2','Too few available connections.
If MongoDB runs low on connections, in may not be able to handle incoming requests in a timely manner.',NULL,'0','0','0','','0','','0','','0','MongoDB node: Total number of open connections is too high (over {$MONGODB.CONNS.PCT.USED.MAX.WARN%} in 5m)','58142b2a76114e69af259ea1b5c19bbc',''),
('18222','{21747}>{$MONGODB.CURSOR.OPEN.MAX.WARN}','MongoDB node: Too many cursors opened by MongoDB for clients','','0','2','',NULL,'0','0','0','','0','','0','','0','MongoDB node: Too many cursors opened by MongoDB for clients (over {$MONGODB.CURSOR.OPEN.MAX.WARN} in 5m)','ed4a0c66c76d4ca699d0f2188cc8e71f',''),
('18223','{21748}>{$MONGODB.CURSOR.TIMEOUT.MAX.WARN}','MongoDB node: Too many cursors are timing out','','0','2','',NULL,'0','0','0','','0','','0','','0','MongoDB node: Too many cursors are timing out (over {$MONGODB.CURSOR.TIMEOUT.MAX.WARN} per second in 5m)','41d37791111b461d94da779e4b2c7e46',''),
('18224','{21749}=0','MongoDB node: Connection to MongoDB is unavailable','','0','4','Connection to MongoDB instance is currently unavailable.',NULL,'0','0','0','','0','','0','','0','','c4ab9bfdd6d14634870f8ebb44081655',''),
('18225','{21750}=1','MongoDB node: Failed to fetch info data','','0','2','Zabbix has not received data for items for the last 10 minutes',NULL,'0','0','0','','0','','1','','0','MongoDB node: Failed to fetch info data (or no data for 10m)','166444342def4adc954aa35f3dc22dba',''),
('18226','{21751}<10m','MongoDB node: mongod process has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MongoDB node: mongod process has been restarted (uptime < 10m)','992590e47a7f42dda0e074c2f7a3e5ba',''),
('18227','{23444}<>{23445} and length({23446})>0','MongoDB node: Version has changed','','0','1','MongoDB version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MongoDB node: Version has changed (new version: {ITEM.VALUE})','0856e13b7e7644c5b353fcfa577acb51',''),
('18233','{21760}<{$MONGODB.CONNS.AVAILABLE.MIN.WARN}','MongoDB cluster: Available connections is low','','0','2','Too few available connections.
Consider this value in combination with the value of connections current to understand the connection load on the database.',NULL,'0','0','0','','0','','0','','0','MongoDB cluster: Available connections less then {$MONGODB.CONNS.AVAILABLE.MIN.WARN}','eae86b6f98db49099259a466b78d1c59',''),
('18234','{21761}>{$MONGODB.CURSOR.OPEN.MAX.WARN}','MongoDB cluster: Too many cursors opened by MongoDB for clients','','0','2','',NULL,'0','0','0','','0','','0','','0','MongoDB cluster: Too many cursors opened by MongoDB for clients (over {$MONGODB.CURSOR.OPEN.MAX.WARN} in 5m)','67db1f543818476ca0b07e2cc1709452',''),
('18235','{21762}>{$MONGODB.CURSOR.TIMEOUT.MAX.WARN}','MongoDB cluster: Too many cursors are timing out','','0','2','',NULL,'0','0','0','','0','','0','','0','MongoDB cluster: Too many cursors are timing out (over {$MONGODB.CURSOR.TIMEOUT.MAX.WARN} per second in 5m)','5ea8cf9c955940a6a580cd6f4bb2cc78',''),
('18236','{21763}=0','MongoDB cluster: Connection to mongos proxy is unavailable','','0','4','Connection to mongos proxy instance is currently unavailable.',NULL,'0','0','0','','0','','0','','0','','cd74289970204ca281c5bc7d5c695e95',''),
('18237','{21764}=1','MongoDB cluster: Failed to fetch info data','','0','2','Zabbix has not received data for items for the last 10 minutes',NULL,'0','0','0','','0','','1','','0','MongoDB cluster: Failed to fetch info data (or no data for 10m)','ee70d6da232a4068b574c9c147c622c9',''),
('18238','{21765}<10m','MongoDB cluster: Mongos server has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MongoDB cluster: Mongos server has been restarted (uptime < 10m)','99ff438a7e3e4b0a8190b2ab9f41f076',''),
('18239','{23449}<>{23450} and length({23451})>0','MongoDB cluster: Version has changed','','0','1','MongoDB cluster version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MongoDB cluster: Version has changed (new version: {ITEM.VALUE})','921ee489887943838d69558f103ad646',''),
('18298','{21970}=0','Cisco Catalyst 3750V2-24FS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout.  Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','b0507a7333384bd5bf251fe238a538ad',''),
('18299','{21971}>{$ICMP_LOSS_WARN} and {21971}<100','Cisco Catalyst 3750V2-24FS: High ICMP ping loss','','0','2','',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','089e23bcb4bb41f992947a6970555394',''),
('18300','{21972}>{$ICMP_RESPONSE_TIME_WARN}','Cisco Catalyst 3750V2-24FS: High ICMP ping response time','','0','2','',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','d5449d68d76e49ad9b7c052abff255e2',''),
('18301','{23744}<>{23745} and length({23746})>0','Cisco Catalyst 3750V2-24FS: Device has been replaced','','0','1','The device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-24FS: Device has been replaced (new serial number received)','ef94f8295a2946b9a266afc6c9a5c5c9',''),
('18302','{23747}<>{23748} and length({23749})>0','Cisco Catalyst 3750V2-24FS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-24FS: System name has changed (new name: {ITEM.VALUE})','0d48c5e2b30f4f08b3cec8c89c05d52d',''),
('18303','{23750}<>{23751} and length({23752})>0','Cisco Catalyst 3750V2-24FS: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','2','','0','','1','','0','','77433856d157408d98c72d964fdbf045',''),
('18304','({32154}>0 and {32154}<10m) or ({32154}=0 and {32155}<10m)','Cisco Catalyst 3750V2-24FS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-24FS: {HOST.NAME} has been restarted (uptime < 10m)','6e105d2b8a2c43cc8841abb6995941ba',''),
('18305','{21980}=0','Cisco Catalyst 3750V2-24FS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','4ebd3dd755dd4b1dae2509842d0b7117',''),
('18325','{22013}=0','Cisco Catalyst 3750V2-24PS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout.  Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','e66bcbef8f1d45fc8bc5d64e5dc848dc',''),
('18326','{22014}>{$ICMP_LOSS_WARN} and {22014}<100','Cisco Catalyst 3750V2-24PS: High ICMP ping loss','','0','2','',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','20ee878da19f4d758e4372c6c918c773',''),
('18327','{22015}>{$ICMP_RESPONSE_TIME_WARN}','Cisco Catalyst 3750V2-24PS: High ICMP ping response time','','0','2','',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','0facff81f25c43869e86a0541f0e3ecd',''),
('18328','{23756}<>{23757} and length({23758})>0','Cisco Catalyst 3750V2-24PS: Device has been replaced','','0','1','The device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-24PS: Device has been replaced (new serial number received)','052fb88fae1349d5b9a5fa5bcf24d0fa',''),
('18329','{23759}<>{23760} and length({23761})>0','Cisco Catalyst 3750V2-24PS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-24PS: System name has changed (new name: {ITEM.VALUE})','a678341d899846158fea2deb57f923cf',''),
('18330','{23762}<>{23763} and length({23764})>0','Cisco Catalyst 3750V2-24PS: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','2','','0','','1','','0','','3e5d53072021491bb2af276aff3e1a0b',''),
('18331','({32156}>0 and {32156}<10m) or ({32156}=0 and {32157}<10m)','Cisco Catalyst 3750V2-24PS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-24PS: {HOST.NAME} has been restarted (uptime < 10m)','a9633d3df8724c7cba6dfc6ec790c1fd',''),
('18332','{22023}=0','Cisco Catalyst 3750V2-24PS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','0f2d48a1529c4ae49d58d466ed3a76e7',''),
('18352','{22056}=0','Cisco Catalyst 3750V2-24TS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout.  Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','e536d08729024bbcbe51f63ac1074796',''),
('18353','{22057}>{$ICMP_LOSS_WARN} and {22057}<100','Cisco Catalyst 3750V2-24TS: High ICMP ping loss','','0','2','',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','63bdfa05fcbe455db4dbb28ae333292a',''),
('18354','{22058}>{$ICMP_RESPONSE_TIME_WARN}','Cisco Catalyst 3750V2-24TS: High ICMP ping response time','','0','2','',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','79b80f4faa30401c8aa260a7bc961f9c',''),
('18355','{23768}<>{23769} and length({23770})>0','Cisco Catalyst 3750V2-24TS: Device has been replaced','','0','1','The device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-24TS: Device has been replaced (new serial number received)','be325325a6bd4cf4ae1312b4488af80d',''),
('18356','{23771}<>{23772} and length({23773})>0','Cisco Catalyst 3750V2-24TS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-24TS: System name has changed (new name: {ITEM.VALUE})','d19bce317a4b4ab19485a183d446dcc7',''),
('18357','{23774}<>{23775} and length({23776})>0','Cisco Catalyst 3750V2-24TS: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','2','','0','','1','','0','','c139de21caf94d4b9c2d60977d4756f7',''),
('18358','({32158}>0 and {32158}<10m) or ({32158}=0 and {32159}<10m)','Cisco Catalyst 3750V2-24TS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-24TS: {HOST.NAME} has been restarted (uptime < 10m)','86484c0d62e94532af4202267369f8bf',''),
('18359','{22066}=0','Cisco Catalyst 3750V2-24TS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d78318493148438abca20fed768d4ced',''),
('18379','{22099}=0','Cisco Catalyst 3750V2-48PS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout.  Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','01901a212f7c4fd2976f8ab89ad7eb68',''),
('18380','{22100}>{$ICMP_LOSS_WARN} and {22100}<100','Cisco Catalyst 3750V2-48PS: High ICMP ping loss','','0','2','',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','20104e6a8abe4b0e9bdd32325d506d9c',''),
('18381','{22101}>{$ICMP_RESPONSE_TIME_WARN}','Cisco Catalyst 3750V2-48PS: High ICMP ping response time','','0','2','',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','21b7cefe750048fba80e026afecebcfd',''),
('18382','{23780}<>{23781} and length({23782})>0','Cisco Catalyst 3750V2-48PS: Device has been replaced','','0','1','The device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-48PS: Device has been replaced (new serial number received)','a11a364406534a838c99f89c4136eb5b',''),
('18383','{23783}<>{23784} and length({23785})>0','Cisco Catalyst 3750V2-48PS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-48PS: System name has changed (new name: {ITEM.VALUE})','b881ec6269d54e25810ed2ec2dfe3385',''),
('18384','{23786}<>{23787} and length({23788})>0','Cisco Catalyst 3750V2-48PS: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','2','','0','','1','','0','','cc0071c5d3074123a77ebddd7dd8583c',''),
('18385','({32160}>0 and {32160}<10m) or ({32160}=0 and {32161}<10m)','Cisco Catalyst 3750V2-48PS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-48PS: {HOST.NAME} has been restarted (uptime < 10m)','904571e51fbc4cd0a3a25800e16ec495',''),
('18386','{22109}=0','Cisco Catalyst 3750V2-48PS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','90d5894323074dc8bcd57b212cdbf398',''),
('18406','{22142}=0','Cisco Catalyst 3750V2-48TS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout.  Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','1dd6a211f5e54351a2d4a0854e66fdba',''),
('18407','{22143}>{$ICMP_LOSS_WARN} and {22143}<100','Cisco Catalyst 3750V2-48TS: High ICMP ping loss','','0','2','',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','669ae230efe84f76be95f3ac0eac1102',''),
('18408','{22144}>{$ICMP_RESPONSE_TIME_WARN}','Cisco Catalyst 3750V2-48TS: High ICMP ping response time','','0','2','',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','391b3ac9e1b746c8824af721c472df7b',''),
('18409','{23792}<>{23793} and length({23794})>0','Cisco Catalyst 3750V2-48TS: Device has been replaced','','0','1','The device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-48TS: Device has been replaced (new serial number received)','f63ea5e9c33f465985259c3c8d27a12a',''),
('18410','{23795}<>{23796} and length({23797})>0','Cisco Catalyst 3750V2-48TS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-48TS: System name has changed (new name: {ITEM.VALUE})','55ff869f6acb4f2daddf5c855aa3d76d',''),
('18411','{23798}<>{23799} and length({23800})>0','Cisco Catalyst 3750V2-48TS: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','2','','0','','1','','0','','6724cfef1df145fdb0e6e2cfb35bc890',''),
('18412','({32162}>0 and {32162}<10m) or ({32162}=0 and {32163}<10m)','Cisco Catalyst 3750V2-48TS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco Catalyst 3750V2-48TS: {HOST.NAME} has been restarted (uptime < 10m)','2f1841fb315041a2a437886dc6c23814',''),
('18413','{22152}=0','Cisco Catalyst 3750V2-48TS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','da0596afe59b455bb503a0b2dea1cebe',''),
('18433','{22185}=0','Mellanox: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout.  Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','fe4c81a386814dfa80ffc76e1b7da9a1',''),
('18434','{30944}>{$ICMP_LOSS_WARN} and {30944}<100','Mellanox: High ICMP ping loss','','0','2','',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','52b307324c37481693d419df236cbbd7',''),
('18435','{30945}>{$ICMP_RESPONSE_TIME_WARN}','Mellanox: High ICMP ping response time','','0','2','',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','39a9cff305074e1a8b7c6ed0c526fda9',''),
('18436','{22188}>{$CPU.UTIL.CRIT}','Mellanox: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Mellanox: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','26913093ab414fe69ff157102ae54796',''),
('18437','{23919}<>{23920} and length({23921})>0','Mellanox: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Mellanox: System name has changed (new name: {ITEM.VALUE})','ff7ad0676a774cf49a4568e752dd916b',''),
('18438','({32984}>0 and {32984}<10m)
or ({32984}=0 and {32985}<10m)','Mellanox: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Mellanox: {HOST.NAME} has been restarted (uptime < 10m)','667856dcaad04a108cb0a5150e825a50',''),
('18439','{22192}=0','Mellanox: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','6e476399963a414a847c4c514055bf43',''),
('18462','{30969}<{$MEMORY.AVAILABLE.MIN} and {30970}>0','Linux: Lack of available memory','','0','3','',NULL,'0','0','0','','0','','0','Available: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Linux: Lack of available memory (<{$MEMORY.AVAILABLE.MIN} of {ITEM.VALUE2})','f78ed17586964a46a9de0c4f183984f6',''),
('18473','{22292}=2','APC UPS: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','7e40918732e74b5e8bd854422989e77d',''),
('18474','{22293}=4','APC UPS: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','7ae03f3f307b4f11ad2bc0548911cbd3',''),
('18475','{22294}=3','APC UPS: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','1282326bb61d45d88671bbbde3fab8ff',''),
('18476','{22295} > {$BATTERY.TEMP.MAX.WARN}','APC UPS: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC UPS: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','36a14fe061d1433e9875373307a4e0f4',''),
('18480','{22299} > 0 and ({22299} > {$UPS.INPUT_FREQ.MAX.WARN} or {22300} < {$UPS.INPUT_FREQ.MIN.WARN})','APC UPS: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC UPS: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','1ddd2699b87f452a8893f75f805c0a81',''),
('18481','{22301} > 0 and ({22301} > {$UPS.INPUT_VOLT.MAX.WARN} or {22302} < {$UPS.INPUT_VOLT.MIN.WARN})','APC UPS: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC UPS: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','f6527c4fed3d41168be23f9367f18405',''),
('18482','{22303} > {$UPS.OUTPUT.MAX.WARN}','APC UPS: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC UPS: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','ebef08a42d1e47ffa82ea586c1a5b3d6',''),
('18483','{22304}=16','APC UPS: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','c0e0b1db9a1f41379c340c122426778d',''),
('18484','{22305}=10','APC UPS: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','381a6a75d9084ff1bfcc30b6870a2682',''),
('18485','{22306}=7','APC UPS: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','da75b5277ceb423fac8d90b58d49c21f',''),
('18486','{22307}=3','APC UPS: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','b0330f707fc64605934ed95233bd2246',''),
('18487','{22308}=4','APC UPS: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','f8d75a2fdb6942e6b63831d206c78e56',''),
('18488','{22309}=12','APC UPS: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','8eb59b4873e14acfa8e05791ed30c9d1',''),
('18489','{22310}=8','APC UPS: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','e06247b357b849d3ad1886f797705320',''),
('18490','{22311}=11','APC UPS: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','9b4424babc284dcabfb44dc725c03f40',''),
('18491','{22312}=6','APC UPS: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','9ac2faafee484894bb304da02d6ab0b2',''),
('18492','{22313}=9','APC UPS: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','ce16d33b10e74b129d22378f96ede052',''),
('18493','{22314}=5','APC UPS: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','aa84fc5fd4434101a481481beb616a7c',''),
('18495','({33000}>0 and {33000}<10m)
or ({33000}=0 and {33001}<10m)','APC UPS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC UPS: {HOST.NAME} has been restarted (uptime < 10m)','b0959bdb606542bcb2952e820ac972c9',''),
('18496','{22318}=0','APC UPS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','4572d871f1d944bb855b93fdc6de5e88',''),
('18507','({22330}<>"ok")','NetApp AFF A700: Cluster status is abnormal','','0','3','Any errors associated with the sample. For example, if the aggregation of data over multiple nodes fails then any of the partial errors might be returned, “ok” on success, or “error” on any internal uncategorized failure. Whenever a sample collection is missed but done at a later time, it is back filled to the previous 15 second timestamp and tagged with "backfilled_data". “Inconsistent_ delta_time” is encountered when the time between two collections is not the same for all nodes. Therefore, the aggregated value might be over or under inflated. “Negative_delta” is returned when an expected monotonically increasing value has decreased in value. “Inconsistent_old_data” is returned when one or more nodes do not have the latest data.',NULL,'0','0','0','','0','','0','','0','','c823a2eb325a4153871be705d7c24c72',''),
('18508','{24409}<>{24410} and length({24411})>0','NetApp AFF A700: Version has changed','','0','1','The NetApp AFF A700 version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','NetApp AFF A700: Version has changed (new version: {ITEM.VALUE})','4a2936f068ed486f8c8a2cf2cfa7440b',''),
('18527','{22363}>{22364}/100*{$SQUID.PAGE.FAULT.WARN}','Squid: High sys page faults rate','','0','2','',NULL,'0','0','0','','0','','0','','0','Squid: High sys page faults rate (>{$SQUID.PAGE.FAULT.WARN}% of received HTTP requests)','89a1cfe0f02f4da880f197c2e5605db8',''),
('18528','{33908}>{$ZABBIX.SERVER.UTIL.MAX:"report manager"}','Zabbix server: Utilization of report manager processes is high','','0','3','Indicates potential performance issues with the report manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33908}<{$ZABBIX.SERVER.UTIL.MIN:"report manager"}','0','','0','','0','Zabbix server: Utilization of report manager processes over {$ZABBIX.SERVER.UTIL.MAX:"report manager"}%','32d6f18edd5a45e1999f294f227c600f',''),
('18529','{33909}>{$ZABBIX.SERVER.UTIL.MAX:"report writer"}','Zabbix server: Utilization of report writer processes is high','','0','3','Indicates potential performance issues with the report writer, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33909}<{$ZABBIX.SERVER.UTIL.MIN:"report writer"}','0','','0','','0','Zabbix server: Utilization of report writer processes over {$ZABBIX.SERVER.UTIL.MAX:"report writer"}%','83fa871d54f74c89a7c85d429d40da53',''),
('18530','{33794}>{$ZABBIX.SERVER.UTIL.MAX:"report manager"}','Zabbix server: Utilization of report manager processes is high','','0','3','Indicates potential performance issues with the report manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33794}<{$ZABBIX.SERVER.UTIL.MIN:"report manager"}','0','','0','','0','Zabbix server: Utilization of report manager processes over {$ZABBIX.SERVER.UTIL.MAX:"report manager"}%','82f774b4a47247f49db1ab0480a69eae',''),
('18531','{33795}>{$ZABBIX.SERVER.UTIL.MAX:"report writer"}','Zabbix server: Utilization of report writer processes is high','','0','3','Indicates potential performance issues with the report writer, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33795}<{$ZABBIX.SERVER.UTIL.MIN:"report writer"}','0','','0','','0','Zabbix server: Utilization of report writer processes over {$ZABBIX.SERVER.UTIL.MAX:"report writer"}%','03158d902b854b3495aa76042f361bea',''),
('18534','{22371}>{$MSSQL.WORK_FILES.MAX}','MSSQL: Number of work files created per second is high','','0','3','Too many work files created per second to store temporary results for hash joins and hash aggregates.',NULL,'0','0','0','','0','','0','','0','MSSQL: Number of work files created per second is high (over {$MSSQL.WORK_FILES.MAX} for 5m)','2f7e2dd4a94e4e92b468f4e2e2364f71',''),
('18535','{22372}>{$MSSQL.WORK_TABLES.MAX}','MSSQL: Number of work tables created per second is high','','0','3','Too many work tables created per second to store temporary results for query spool, LOB variables, XML variables, and cursors.',NULL,'0','0','0','','0','','0','','0','MSSQL: Number of work tables created per second is high (over {$MSSQL.WORK_TABLES.MAX} for 5m)','0214004de3084ce6b35d5bba53a66947',''),
('18544','{22381}<{$MYSQL.BUFF_UTIL.MIN.WARN}','MySQL: Buffer pool utilization is too low','','0','2','The buffer pool utilization is less than `{$MYSQL.BUFF_UTIL.MIN.WARN}`% in the last 5 minutes. This means that there is a lot of unused RAM allocated for the buffer pool, which you can easily reallocate at the moment.',NULL,'0','0','0','','0','','0','','0','MySQL: Buffer pool utilization is too low (less than {$MYSQL.BUFF_UTIL.MIN.WARN}% for 5m)','0e8ea91d72a64507aaadf9ea5efa6412',''),
('18545','{22382}<{$MYSQL.BUFF_UTIL.MIN.WARN}','MySQL: Buffer pool utilization is too low','','0','2','The buffer pool utilization is less than `{$MYSQL.BUFF_UTIL.MIN.WARN}`% in the last 5 minutes. This means that there is a lot of unused RAM allocated for the buffer pool, which you can easily reallocate at the moment.',NULL,'0','0','0','','0','','0','','0','MySQL: Buffer pool utilization is too low (less than {$MYSQL.BUFF_UTIL.MIN.WARN}% for 5m)','d785a37fe8d7484d9998e47e0e1d741f',''),
('18546','{22383}<{$MYSQL.BUFF_UTIL.MIN.WARN}','MySQL: Buffer pool utilization is too low','','0','2','The buffer pool utilization is less than `{$MYSQL.BUFF_UTIL.MIN.WARN}`% in the last 5 minutes. This means that there is a lot of unused RAM allocated for the buffer pool, which you can easily reallocate at the moment.',NULL,'0','0','0','','0','','0','','0','MySQL: Buffer pool utilization is too low (less than {$MYSQL.BUFF_UTIL.MIN.WARN}% for 5m)','f4c2e4edf0c34bb1856ed392f2bc7c87',''),
('18547','{22384} > {$ORACLE.CONCURRENCY.MAX.WARN}','Oracle: Too high database concurrency','','0','2','The concurrency rate exceeds `{$ORACLE.CONCURRENCY.MAX.WARN}`%. A high contention value does not indicate the root cause of the problem, but is a signal to review resource consumption (determine the "heaviest" queries in the database, trace sessions, etc.) This will help find the root cause and possible optimization points both in database configuration and the logic of building queries.',NULL,'0','0','0','','0','','0','','0','Oracle: Too high database concurrency (over {$ORACLE.CONCURRENCY.MAX.WARN}% for 5 min)','ff16c7bbeaa5439f98ffe12ce7deff71',''),
('18548','{22385} > {$ORACLE.CONCURRENCY.MAX.WARN}','Oracle: Too high database concurrency','','0','2','The concurrency rate exceeds `{$ORACLE.CONCURRENCY.MAX.WARN}`%. A high contention value does not indicate the root cause of the problem, but is a signal to review resource consumption (determine the "heaviest" queries in the database, trace sessions, etc.) This will help find the root cause and possible optimization points both in database configuration and the logic of building queries.',NULL,'0','0','0','','0','','0','','0','Oracle: Too high database concurrency (over {$ORACLE.CONCURRENCY.MAX.WARN}% for 5 min)','7099e4a160c1446395b9e5b721db7b38',''),
('18549','{22386}=0','TiDB PD: Instance is not responding','','0','3','',NULL,'0','0','0','','0','','0','','0','','ab1d0d23dad844099e42debb71512887',''),
('18550','{22387}<10m','TiDB PD: Instance has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','TiDB PD: Instance has been restarted (uptime < 10m)','9f47a19f6f424df598e74c5a653ebf27',''),
('18551','{23515}<>{23516} and length({23517})>0','TiDB PD: Version has changed','','0','1','PD version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','TiDB PD: Version has changed (new version: {ITEM.VALUE})','6fb6045405af4c89b09750f57ada472a',''),
('18558','{22397}/{22398}*100>{$TIDB.OPEN.FDS.MAX.WARN}','TiDB: Current number of open files is too high','','0','2','Heavy file descriptor usage (i.e., near the process''s file descriptor limit) indicates a potential file descriptor exhaustion issue.',NULL,'0','0','0','','0','','0','','0','TiDB: Current number of open files is too high (over {$TIDB.OPEN.FDS.MAX.WARN}% for 5m)','cfd6ba0dbf294b9e9ab6afc7d44be7b3',''),
('18559','{22399}>{$TIDB.DDL.WAITING.MAX.WARN}','TiDB: Too many DDL waiting jobs','','0','2','',NULL,'0','0','0','','0','','0','','0','TiDB: Too many DDL waiting jobs (over {$TIDB.DDL.WAITING.MAX.WARN} for 5m)','4125d55d9931455091d2f3a0b25e9678',''),
('18560','{22400}>{$TIDB.SCHEMA_LOAD_ERRORS.MAX.WARN}','TiDB: Too many schema lease errors','','0','3','',NULL,'0','0','0','','0','','0','','0','TiDB: Too many schema lease errors (over {$TIDB.SCHEMA_LOAD_ERRORS.MAX.WARN} for 5m)','b4948f37af804c01a2b8887f9e89ec90',''),
('18561','{22401}>{$TIDB.HEAP.USAGE.MAX.WARN}','TiDB: Heap memory usage is too high','','0','2','',NULL,'0','0','0','','0','','0','','0','TiDB: Heap memory usage is too high (over {$TIDB.HEAP.USAGE.MAX.WARN} for 5m)','575a4821ed8c4a1881b7f9bd264b1929',''),
('18562','{22402}<{$TIDB.MONITOR_KEEP_ALIVE.MAX.WARN}','TiDB: Too few keep alive operations','','0','3','Indicates whether the TiDB process still exists. If the number of times for tidb_monitor_keep_alive_total increases less than 10 per minute, the TiDB process might already exit and an alert is triggered.',NULL,'0','0','0','','0','','0','','0','TiDB: Too few keep alive operations (less {$TIDB.MONITOR_KEEP_ALIVE.MAX.WARN} for 5m)','eb3c09904fa843d78401b00eff4f6a08',''),
('18563','{22403}>{$TIDB.TIME_JUMP_BACK.MAX.WARN}','TiDB: Too many time jump backs','','0','2','',NULL,'0','0','0','','0','','0','','0','TiDB: Too many time jump backs (over {$TIDB.TIME_JUMP_BACK.MAX.WARN} for 5m)','c3c1f6eab224453b92534d5393aca2b7',''),
('18564','{22404}>{$TIDB.SCHEMA_LEASE_ERRORS.MAX.WARN}','TiDB: Too many schema lease errors','','0','3','The latest schema information is not reloaded in TiDB within one lease.',NULL,'0','0','0','','0','','0','','0','TiDB: Too many schema lease errors (over {$TIDB.SCHEMA_LEASE_ERRORS.MAX.WARN} for 5m)','b077eb1afe6a4da79707987324fb40c8',''),
('18565','{22405}=0','TiDB: Instance is not responding','','0','3','',NULL,'0','0','0','','0','','0','','0','','82a638ac4a3f4b349ee7bb0d53bc1f29',''),
('18566','{22406}>0','TiDB: There are panicked TiDB threads','','0','3','When a panic occurs, an alert is triggered. The thread is often recovered, otherwise, TiDB will frequently restart.',NULL,'0','0','0','','0','','0','','0','','c457465731c947eab7b477186d8ba876',''),
('18567','{22407}>{$TIDB.REGION_ERROR.MAX.WARN}','TiDB: Too many region related errors','','0','3','',NULL,'0','0','0','','0','','0','','0','TiDB: Too many region related errors (over {$TIDB.REGION_ERROR.MAX.WARN} for 5m)','d3cb81c46e414ff2a7e411a877b899ef',''),
('18568','{22408}<10m','TiDB: Instance has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','TiDB: Instance has been restarted (uptime < 10m)','91adc4c6b9364693891faf58c8cced75',''),
('18569','{23518}<>{23519} and length({23520})>0','TiDB: Version has changed','','0','1','TiDB version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','TiDB: Version has changed (new version: {ITEM.VALUE})','5f863fc0944848fdad145f42c94dbea3',''),
('18571','{33388}>{$TIKV.COPROCESSOR.ERRORS.MAX.WARN}','TiDB TiKV: Too many coprocessor request error','','0','2','',NULL,'0','0','0','','0','','0','','0','TiDB TiKV: Too many coprocessor request error (over {$TIKV.COPROCESSOR.ERRORS.MAX.WARN} in 5m)','31eca27ff6ce4ed78ee428ed3b8d8806',''),
('18573','{22414}>{$TIKV.PENDING_TASKS.MAX.WARN}','TiDB TiKV: Too many pending tasks','','0','3','',NULL,'0','0','0','','0','','0','','0','TiDB TiKV: Too many pending tasks (over {$TIKV.PENDING_TASKS.MAX.WARN} for 5m)','f26874f910e34933983685ae43a90bee',''),
('18574','{22415}<10m','TiDB TiKV: Instance has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','TiDB TiKV: Instance has been restarted (uptime < 10m)','ca06602fa0b64a2ba0c51ed4835c52b2',''),
('18576','{22417} < {$BATTERY.CAPACITY.MIN.WARN}','APC UPS Galaxy: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC UPS Galaxy: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','1800690ba0504df9940a4e667c846132',''),
('18577','{22418}=2','APC UPS Galaxy: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','b4d10f8908f4473facde6d2db1520e0f',''),
('18578','{22419}=4','APC UPS Galaxy: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','d84ec0d0b8d84e3294cbe7ffaed0c83e',''),
('18579','{22420}=3','APC UPS Galaxy: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','8f569ce6c916456581e1cb2cdd8d4dba',''),
('18580','{22421} > {$BATTERY.TEMP.MAX.WARN}','APC UPS Galaxy: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC UPS Galaxy: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','0e1f47f0604d4b1b8769e497d7f328b9',''),
('18581','{22422} > 0 and ({22422} > {$UPS.INPUT_FREQ.MAX.WARN} or {22423} < {$UPS.INPUT_FREQ.MIN.WARN})','APC UPS Galaxy: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC UPS Galaxy: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','786d9928356e41ad9b6b2de3b4f3a96f',''),
('18582','{22424} > 0 and ({22424} > {$UPS.INPUT_VOLT.MAX.WARN} or {22425} < {$UPS.INPUT_VOLT.MIN.WARN})','APC UPS Galaxy: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC UPS Galaxy: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','de88ed3b64644d3f9ad1cc3f965757bc',''),
('18583','{22426} > {$UPS.OUTPUT.MAX.WARN}','APC UPS Galaxy: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC UPS Galaxy: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','fb7ca4b92e714fda95152b698cf1aa92',''),
('18584','{22427}=16','APC UPS Galaxy: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','efed1ccf301740c1a29e71cd89e5659f',''),
('18585','{22428}=10','APC UPS Galaxy: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','44394841911641c4972165b59b8f6a5b',''),
('18586','{22429}=7','APC UPS Galaxy: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','d60b075bfaaa4aeea2398d058fb79c92',''),
('18587','{22430}=3','APC UPS Galaxy: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','4d54e6e979f94801a3c1e9d6080886bb',''),
('18588','{22431}=4','APC UPS Galaxy: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','eb430f5409a24f89b0a9e56fb28087c4',''),
('18589','{22432}=12','APC UPS Galaxy: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','77dbd58283b542cfbca9a9255344e97e',''),
('18590','{22433}=8','APC UPS Galaxy: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','3856ff4ac1d64f8e80c4e0cbb1e04c1a',''),
('18591','{22434}=11','APC UPS Galaxy: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','10d8d392f93a492b9be767c7ccdf06ed',''),
('18592','{22435}=6','APC UPS Galaxy: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','2ab92cb281754de6ad5245509c20056d',''),
('18593','{22436}=9','APC UPS Galaxy: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','8fabe8958cfd4dbbabd70648dff1be06',''),
('18594','{22437}=5','APC UPS Galaxy: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','9846ac1bbf024e63a05a83e2c02de7ba',''),
('18595','{24371}<>{24372} and length({24373})>0','APC UPS Galaxy: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC UPS Galaxy: System name has changed (new name: {ITEM.VALUE})','811ff6e90d904c8c98feadc89a18e733',''),
('18596','({32986}>0 and {32986}<10m)
or ({32986}=0 and {32987}<10m)','APC UPS Galaxy: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC UPS Galaxy: {HOST.NAME} has been restarted (uptime < 10m)','5c50881846c649dbb47adcfb3dfc7d68',''),
('18597','{22441}=0','APC UPS Galaxy: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','e12b11324a634eeba56db1aec1834d5f',''),
('18609','{22455} < {$BATTERY.CAPACITY.MIN.WARN}','APC Smart-UPS: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','58a0749ef9c94cf9802a62d274b6dad9',''),
('18610','{22456}=2','APC Smart-UPS: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','8370727883de45dfa6b6d79f60cc86b3',''),
('18611','{22457}=4','APC Smart-UPS: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','2fb002b1a4584aa0bf0389360171893c',''),
('18612','{22458}=3','APC Smart-UPS: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','05aa81dc53ab45ffaf46580c9f827759',''),
('18613','{22459} > {$BATTERY.TEMP.MAX.WARN}','APC Smart-UPS: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','1e8c0b3d2d65487199e7fc3e1dde6e50',''),
('18614','{22460} > 0 and ({22460} > {$UPS.INPUT_FREQ.MAX.WARN} or {22461} < {$UPS.INPUT_FREQ.MIN.WARN})','APC Smart-UPS: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','b89b059a430842aebbd3e6af71514303',''),
('18615','{22462} > 0 and ({22462} > {$UPS.INPUT_VOLT.MAX.WARN} or {22463} < {$UPS.INPUT_VOLT.MIN.WARN})','APC Smart-UPS: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','2dbc2b96d332488cae4cbf87c985c6b0',''),
('18616','{22464} > {$UPS.OUTPUT.MAX.WARN}','APC Smart-UPS: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','edb059eeee004d80a9b42154f16ab18a',''),
('18617','{22465}=16','APC Smart-UPS: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','20ffc78c2f314ff58b5e75907605c82f',''),
('18618','{22466}=10','APC Smart-UPS: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','ec6e892f4c51414f887d428510d889e7',''),
('18619','{22467}=7','APC Smart-UPS: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','f4cb0ed7e65d4ea29394435cce7600f0',''),
('18620','{22468}=3','APC Smart-UPS: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','e29c2a37586f474f87c388fa8eaf8b9c',''),
('18621','{22469}=4','APC Smart-UPS: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','a07afe38040c4fd08488786ca3f529e5',''),
('18622','{22470}=12','APC Smart-UPS: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','58f44a830386434db0f76553f64ebe67',''),
('18623','{22471}=8','APC Smart-UPS: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','eb99c49157a948769128bc9eeeaff3fc',''),
('18624','{22472}=11','APC Smart-UPS: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','b3d77823096e4bf4a06db8f2307284db',''),
('18625','{22473}=6','APC Smart-UPS: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','000d6b412dd3467aaee40ce230cc059e',''),
('18626','{22474}=9','APC Smart-UPS: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','f1f86a1f23c745658d0c5d10557f67fc',''),
('18627','{22475}=5','APC Smart-UPS: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','434d70c967a9447a9fa927fc2867aa6d',''),
('18628','{24374}<>{24375} and length({24376})>0','APC Smart-UPS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: System name has changed (new name: {ITEM.VALUE})','30153a623f0649e380de8f9ec5086b48',''),
('18629','({32988}>0 and {32988}<10m)
or ({32988}=0 and {32989}<10m)','APC Smart-UPS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: {HOST.NAME} has been restarted (uptime < 10m)','f23282a63bec4b1d951f80439947672d',''),
('18630','{22479}=0','APC Smart-UPS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','e9dc225935594e8aa25fb80fcfa68e4c',''),
('18642','{22493} < {$BATTERY.CAPACITY.MIN.WARN}','APC Smart-UPS: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','13fe1336e40c4bafb8dbd409497abf8f',''),
('18643','{22494}=2','APC Smart-UPS: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','4590ac935e044c19978fe01d117e2995',''),
('18644','{22495}=4','APC Smart-UPS: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','e98ba83e63d246408aeeda76da62d5a4',''),
('18645','{22496}=3','APC Smart-UPS: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','51e3281c49454cf997561c857a34a803',''),
('18646','{22497} > {$BATTERY.TEMP.MAX.WARN}','APC Smart-UPS: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','1c67af712882479bbf7143bd3e16ed77',''),
('18647','{22498} > 0 and ({22498} > {$UPS.INPUT_FREQ.MAX.WARN} or {22499} < {$UPS.INPUT_FREQ.MIN.WARN})','APC Smart-UPS: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','78e47553d4bb488991067f53cc8f8a01',''),
('18648','{22500} > 0 and ({22500} > {$UPS.INPUT_VOLT.MAX.WARN} or {22501} < {$UPS.INPUT_VOLT.MIN.WARN})','APC Smart-UPS: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','28ad85fa6035433f9a7ec45a8393b603',''),
('18649','{22502} > {$UPS.OUTPUT.MAX.WARN}','APC Smart-UPS: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','f667172a5cf44ed6b98f2bb38a3f3806',''),
('18650','{22503}=16','APC Smart-UPS: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','80e30d37b1724c6ba1d58cedbcf6307f',''),
('18651','{22504}=10','APC Smart-UPS: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','9bb143ada4194c0084eb70af7bb2c5dc',''),
('18652','{22505}=7','APC Smart-UPS: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','7132f256542540acadb0caf90144a29c',''),
('18653','{22506}=3','APC Smart-UPS: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','737693e5e4274823a9a21ff92a6ca98a',''),
('18654','{22507}=4','APC Smart-UPS: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','c2fd31cfe3b8474f80b52a2340108b6a',''),
('18655','{22508}=12','APC Smart-UPS: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','2c3a2e962c1e45f6858e5c1aaecee4a3',''),
('18656','{22509}=8','APC Smart-UPS: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','59d415b15bbf43de85453f5b2ffb73d7',''),
('18657','{22510}=11','APC Smart-UPS: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','6811d34cec57401089af9accfd66ca8f',''),
('18658','{22511}=6','APC Smart-UPS: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','3c96ce14f54a4a59a2568f1f62117e7b',''),
('18659','{22512}=9','APC Smart-UPS: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','60e83c77157741cbb3d24920e87d7d59',''),
('18660','{22513}=5','APC Smart-UPS: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','da442de0e8874736aaab88f009aabe76',''),
('18661','{24377}<>{24378} and length({24379})>0','APC Smart-UPS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: System name has changed (new name: {ITEM.VALUE})','c9b1f69a882148a180ec1e2600068671',''),
('18662','({32990}>0 and {32990}<10m)
or ({32990}=0 and {32991}<10m)','APC Smart-UPS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: {HOST.NAME} has been restarted (uptime < 10m)','15764a5819174d3fadc75436f42650fb',''),
('18663','{22517}=0','APC Smart-UPS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','71994587c45546bfb0950606d7f69936',''),
('18675','{22531} < {$BATTERY.CAPACITY.MIN.WARN}','APC Smart-UPS: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','8ab182b26a0443539a1a114767d8acd7',''),
('18676','{22532}=2','APC Smart-UPS: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','ab0db1327cf04a9c9a9ee757f0869603',''),
('18677','{22533}=4','APC Smart-UPS: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','c8787a09c2ea4aeb977b868ae0a3218b',''),
('18678','{22534}=3','APC Smart-UPS: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','40d1fdcec63d4c3785b5ba77fbd14ee7',''),
('18679','{22535} > {$BATTERY.TEMP.MAX.WARN}','APC Smart-UPS: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','e2debe06675d4d4584b60b768633887b',''),
('18680','{22536} > 0 and ({22536} > {$UPS.INPUT_FREQ.MAX.WARN} or {22537} < {$UPS.INPUT_FREQ.MIN.WARN})','APC Smart-UPS: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','b29cd7e33c1e4e16b10fe436c1f7e6d6',''),
('18681','{22538} > 0 and ({22538} > {$UPS.INPUT_VOLT.MAX.WARN} or {22539} < {$UPS.INPUT_VOLT.MIN.WARN})','APC Smart-UPS: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','d38f2151f0eb486e8d44b72a2e361a5f',''),
('18682','{22540} > {$UPS.OUTPUT.MAX.WARN}','APC Smart-UPS: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','57197c601f8a433d8ccdcb040d047f6f',''),
('18683','{22541}=16','APC Smart-UPS: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','e9289d8f4e124097990e2af98e916368',''),
('18684','{22542}=10','APC Smart-UPS: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','13735964f51d4d1bb17e6b0587a43020',''),
('18685','{22543}=7','APC Smart-UPS: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','d74ae82199884a7fb4a20b48f3c7ff1f',''),
('18686','{22544}=3','APC Smart-UPS: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','4df5271075904c228a0372d5f667530e',''),
('18687','{22545}=4','APC Smart-UPS: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','3f02d9cb7f5142599e59e7781808e5c3',''),
('18688','{22546}=12','APC Smart-UPS: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','515ad03892694fd4a2f2350a6bb8af6f',''),
('18689','{22547}=8','APC Smart-UPS: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','2a2d35e4e4674b6aa49068a7970caa03',''),
('18690','{22548}=11','APC Smart-UPS: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','ef1ddb8869074847b70e8f669883c56b',''),
('18691','{22549}=6','APC Smart-UPS: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','0d6e4e664ddf425e8c03155802fe45be',''),
('18692','{22550}=9','APC Smart-UPS: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','12a3a33152824ffe863a8d79c1372195',''),
('18693','{22551}=5','APC Smart-UPS: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','273c561c2afb4d78be86218e370c9a1f',''),
('18694','{24380}<>{24381} and length({24382})>0','APC Smart-UPS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: System name has changed (new name: {ITEM.VALUE})','b13b087b9828426aac82a281071ceb8b',''),
('18695','({32992}>0 and {32992}<10m)
or ({32992}=0 and {32993}<10m)','APC Smart-UPS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: {HOST.NAME} has been restarted (uptime < 10m)','87ebd137f2744ae6879d6fd9d51314ef',''),
('18696','{22555}=0','APC Smart-UPS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','53263bf0536d479785b45883b9b7ab21',''),
('18708','{22569} < {$BATTERY.CAPACITY.MIN.WARN}','APC Smart-UPS: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','b5d618c6090447429191fe4d07e85afa',''),
('18709','{22570}=2','APC Smart-UPS: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','dc92c19a5b7e43a4b155d6d51912aaf8',''),
('18710','{22571}=4','APC Smart-UPS: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','70c32834ea40487c8f13a55b7ed7c88f',''),
('18711','{22572}=3','APC Smart-UPS: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','e7aeaae896664729b66b42a94f626f9b',''),
('18712','{22573} > {$BATTERY.TEMP.MAX.WARN}','APC Smart-UPS: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','33695c02cf6141f78e21ca899af10c03',''),
('18713','{22574} > 0 and ({22574} > {$UPS.INPUT_FREQ.MAX.WARN} or {22575} < {$UPS.INPUT_FREQ.MIN.WARN})','APC Smart-UPS: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','167de2d832984944878767571b0b5fe4',''),
('18714','{22576} > 0 and ({22576} > {$UPS.INPUT_VOLT.MAX.WARN} or {22577} < {$UPS.INPUT_VOLT.MIN.WARN})','APC Smart-UPS: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','b8741bc0081a4a9db2824c9f93ecb399',''),
('18715','{22578} > {$UPS.OUTPUT.MAX.WARN}','APC Smart-UPS: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','a4faec3975134cd59e83f1ca7fa3ef7d',''),
('18716','{22579}=16','APC Smart-UPS: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','deedd977f1ed4b9fbb5cc161dde0c116',''),
('18717','{22580}=10','APC Smart-UPS: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','a7bbe6ca410743919f7c611a6faec9ba',''),
('18718','{22581}=7','APC Smart-UPS: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','974042a124b945068c6c16c4a01433dc',''),
('18719','{22582}=3','APC Smart-UPS: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','90e810043e41467b8460278fc7923397',''),
('18720','{22583}=4','APC Smart-UPS: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','656ae233f3a946799c3ed3d48914c0b0',''),
('18721','{22584}=12','APC Smart-UPS: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','3fcbd14931854831ac603a254ffea0c3',''),
('18722','{22585}=8','APC Smart-UPS: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','65085178eef54189afdaf4937de49177',''),
('18723','{22586}=11','APC Smart-UPS: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','0aa402907ee446c0a13fa086b500fa87',''),
('18724','{22587}=6','APC Smart-UPS: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','be6cdd1fc22a4f0eacdbce4361cd6788',''),
('18725','{22588}=9','APC Smart-UPS: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','b4375fc980ae4bee87531d18ea9a5397',''),
('18726','{22589}=5','APC Smart-UPS: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','7ae9e31ac32944928065d1cefb2c4e2f',''),
('18727','{24383}<>{24384} and length({24385})>0','APC Smart-UPS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: System name has changed (new name: {ITEM.VALUE})','31bb0ff1ea334cd59d9f8b8f489611ef',''),
('18728','({32994}>0 and {32994}<10m)
or ({32994}=0 and {32995}<10m)','APC Smart-UPS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: {HOST.NAME} has been restarted (uptime < 10m)','860d3beb50c0400283a71c2c4b4ea5e2',''),
('18729','{22593}=0','APC Smart-UPS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','21fc3a198f3b423fa14676278f53a4be',''),
('18774','{22645} < {$BATTERY.CAPACITY.MIN.WARN}','APC Smart-UPS: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','92e6a65ffc6d4a6bae62303ee2796580',''),
('18775','{22646}=2','APC Smart-UPS: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','0e8030c0028144728361153c2b47016b',''),
('18776','{22647}=4','APC Smart-UPS: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','cf186014cfd94ccbad3cc4cbd22b6aa1',''),
('18777','{22648}=3','APC Smart-UPS: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','e1957ee82be847e7bfb171560fc59293',''),
('18778','{22649} > {$BATTERY.TEMP.MAX.WARN}','APC Smart-UPS: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','1e883961b65e445997c57870734a58ca',''),
('18779','{22650} > 0 and ({22650} > {$UPS.INPUT_FREQ.MAX.WARN} or {22651} < {$UPS.INPUT_FREQ.MIN.WARN})','APC Smart-UPS: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','b9a134c942da46ffba1acdf85a7832e4',''),
('18780','{22652} > 0 and ({22652} > {$UPS.INPUT_VOLT.MAX.WARN} or {22653} < {$UPS.INPUT_VOLT.MIN.WARN})','APC Smart-UPS: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','694ab76079b1447b99ef510d80faab6a',''),
('18781','{22654} > {$UPS.OUTPUT.MAX.WARN}','APC Smart-UPS: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','68f92026e7b345c88bf4aa679f9b642c',''),
('18782','{22655}=16','APC Smart-UPS: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','9952679fada845228bbbf05bcdada305',''),
('18783','{22656}=10','APC Smart-UPS: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','ee306606159f4930bcf580b5084c846a',''),
('18784','{22657}=7','APC Smart-UPS: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','c4623dc4c6ae4c5b9ff4bdf4f43ed8b2',''),
('18785','{22658}=3','APC Smart-UPS: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','26c0b9b62d864c1ead7b16e0076a7226',''),
('18786','{22659}=4','APC Smart-UPS: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','5c8408069c03421cb60b388451869b6f',''),
('18787','{22660}=12','APC Smart-UPS: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','156c5260ed4444c19313ba491ce9352c',''),
('18788','{22661}=8','APC Smart-UPS: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','c233bc86198140659ec3dd609c94ec94',''),
('18789','{22662}=11','APC Smart-UPS: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','944e49d1b6d44adc8d720bd689d8c8cf',''),
('18790','{22663}=6','APC Smart-UPS: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','9b376dbd2d614878b681b42bb2c7fe4d',''),
('18791','{22664}=9','APC Smart-UPS: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','499ac46836c1454dad3c1ffc5714c073',''),
('18792','{22665}=5','APC Smart-UPS: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','8a0a5af39647494681e52595d179c336',''),
('18793','{24389}<>{24390} and length({24391})>0','APC Smart-UPS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: System name has changed (new name: {ITEM.VALUE})','852083234a55441aa2fa57b202227bef',''),
('18794','({32998}>0 and {32998}<10m)
or ({32998}=0 and {32999}<10m)','APC Smart-UPS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: {HOST.NAME} has been restarted (uptime < 10m)','6f0fbe74ad4945e987e7ffdfa741d92f',''),
('18795','{22669}=0','APC Smart-UPS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','9a0cb26712c14045a18a0e86de4cdd54',''),
('18807','{22683} < {$BATTERY.CAPACITY.MIN.WARN}','APC UPS: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC UPS: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','aa0bbfb321d440438fb421825f23e140',''),
('18808','{24392}<>{24393} and length({24394})>0','APC UPS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC UPS: System name has changed (new name: {ITEM.VALUE})','facbfd1f8bb04401b563c162d7fe13a5',''),
('18811','{22689} < {$BATTERY.CAPACITY.MIN.WARN}','APC UPS Symmetra: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','fdece80f2fc44ac1974fafe190ce186f',''),
('18812','{22690}=2','APC UPS Symmetra: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','a1bd434a249b48b2ac0ef69ede417a72',''),
('18813','{22691}=4','APC UPS Symmetra: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','955d79a0cf5447dd9a11d4608758e983',''),
('18814','{22692}=3','APC UPS Symmetra: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','3ca8156ecc1c4ee4b5623c4a085b993f',''),
('18815','{22693} > {$BATTERY.TEMP.MAX.WARN}','APC UPS Symmetra: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','5b43659a10644a51861282bc72116f9f',''),
('18816','{22694} > 0 and ({22694} > {$UPS.INPUT_FREQ.MAX.WARN} or {22695} < {$UPS.INPUT_FREQ.MIN.WARN})','APC UPS Symmetra: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','94a5c26b89e2416f96b61bbfc6e60a97',''),
('18817','{22696} > 0 and ({22696} > {$UPS.INPUT_VOLT.MAX.WARN} or {22697} < {$UPS.INPUT_VOLT.MIN.WARN})','APC UPS Symmetra: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','2b640b94d48446609802ce6e57c7bd46',''),
('18818','{22698} > {$UPS.OUTPUT.MAX.WARN}','APC UPS Symmetra: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','34562b5c734d492c89c386902dfd6e90',''),
('18819','{22699}=16','APC UPS Symmetra: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','6ade2b9fb9ad432596d16b3df6237ec4',''),
('18820','{22700}=10','APC UPS Symmetra: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','da9a0fa7669e454b8ba44c0458a94ea8',''),
('18821','{22701}=7','APC UPS Symmetra: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','01a2bcb5f20b4fe889a48e4bed2a2a63',''),
('18822','{22702}=3','APC UPS Symmetra: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','d0b154dd92424af8bb841d91d4e7ddd5',''),
('18823','{22703}=4','APC UPS Symmetra: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','afc071d0ccfb4226a3c5ee3058270937',''),
('18824','{22704}=12','APC UPS Symmetra: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','12259f4a961a40b39de12d0202d41c56',''),
('18825','{22705}=8','APC UPS Symmetra: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','ef9d1e4b1ec244f6bcf36d19a9e7c9c7',''),
('18826','{22706}=11','APC UPS Symmetra: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','c673928e7b764b5db0fa3168edd2cc67',''),
('18827','{22707}=6','APC UPS Symmetra: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','c9b24aa16e124d8c9cd6cfb188ded816',''),
('18828','{22708}=9','APC UPS Symmetra: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','02904426801d4d42b3f634267f8697e7',''),
('18829','{22709}=5','APC UPS Symmetra: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','fa08f8a60c2c4d88a3f9ebf317fcd06e',''),
('18830','{24395}<>{24396} and length({24397})>0','APC UPS Symmetra: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC UPS Symmetra: System name has changed (new name: {ITEM.VALUE})','61d0836efd33437894e1edd595373f1e',''),
('18831','({33002}>0 and {33002}<10m)
or ({33002}=0 and {33003}<10m)','APC UPS Symmetra: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC UPS Symmetra: {HOST.NAME} has been restarted (uptime < 10m)','9d0c32f93c0c44f69b54c91fabfa1529',''),
('18832','{22713}=0','APC UPS Symmetra: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','aeaaa7e2bd2d46a481f9d8b33ec18cb5',''),
('18844','{22727} < {$BATTERY.CAPACITY.MIN.WARN}','APC UPS Symmetra: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','dbfdc4e6eaca4d65adcde13b0682c1c2',''),
('18845','{22728}=2','APC UPS Symmetra: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','0af287bae1ee44ba997a02ae585bdd4b',''),
('18846','{22729}=4','APC UPS Symmetra: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','aedb557acbe44390809a27b95919e10f',''),
('18847','{22730}=3','APC UPS Symmetra: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','1afe1859563f481faa623781028a38ca',''),
('18848','{22731} > {$BATTERY.TEMP.MAX.WARN}','APC UPS Symmetra: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','0b4490eaaf964fdabf228d34d2992d30',''),
('18849','{22732} > 0 and ({22732} > {$UPS.INPUT_FREQ.MAX.WARN} or {22733} < {$UPS.INPUT_FREQ.MIN.WARN})','APC UPS Symmetra: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','af166242e3674f2da489a232c7bba6f1',''),
('18850','{22734} > 0 and ({22734} > {$UPS.INPUT_VOLT.MAX.WARN} or {22735} < {$UPS.INPUT_VOLT.MIN.WARN})','APC UPS Symmetra: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','3b51bbae66914b19a93e7a2da289b056',''),
('18851','{22736} > {$UPS.OUTPUT.MAX.WARN}','APC UPS Symmetra: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','a25499c49d0043cda248136eb6307ef9',''),
('18852','{22737}=16','APC UPS Symmetra: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','f7b0e2f05c9b4b14916f99ecb89fcd49',''),
('18853','{22738}=10','APC UPS Symmetra: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','77081726414047a5a1c698fcfbf19e73',''),
('18854','{22739}=7','APC UPS Symmetra: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','87beb54ac57848e3896fd715a5918a88',''),
('18855','{22740}=3','APC UPS Symmetra: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','5f46c436fab741ec86cb32339e8bd7b4',''),
('18856','{22741}=4','APC UPS Symmetra: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','a7457e3d6c6f4e99a3ccc08a1436d34a',''),
('18857','{22742}=12','APC UPS Symmetra: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','976395b6acea4f5cb4f7f3d4f0bc67af',''),
('18858','{22743}=8','APC UPS Symmetra: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','72c9677a2157412ebd14004a5e024a3a',''),
('18859','{22744}=11','APC UPS Symmetra: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','75d189cd8b5944c4b7987931c834e949',''),
('18860','{22745}=6','APC UPS Symmetra: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','24e1cfde22da48b0bf28ca2cdf8cd917',''),
('18861','{22746}=9','APC UPS Symmetra: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','4fff7b4a29b84cdea245b2704e357f5d',''),
('18862','{22747}=5','APC UPS Symmetra: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','647178a4cb674815a65517c073b4adee',''),
('18863','{24398}<>{24399} and length({24400})>0','APC UPS Symmetra: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC UPS Symmetra: System name has changed (new name: {ITEM.VALUE})','e3cf119c19b54dddb3d26d9b789ea4f5',''),
('18864','({33004}>0 and {33004}<10m)
or ({33004}=0 and {33005}<10m)','APC UPS Symmetra: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC UPS Symmetra: {HOST.NAME} has been restarted (uptime < 10m)','fb2b4e564040422da234cdb309163b7b',''),
('18865','{22751}=0','APC UPS Symmetra: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','56f25581382a43efbddd4aba44aa86b3',''),
('18877','{22765} < {$BATTERY.CAPACITY.MIN.WARN}','APC UPS Symmetra: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','5626e87891ec4c28a17a6b5965b47e46',''),
('18878','{22766}=2','APC UPS Symmetra: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','a74eccd4442c401a98ac3c80dd3baa13',''),
('18879','{22767}=4','APC UPS Symmetra: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','107454c372cb413bad4d4a807c254ae0',''),
('18880','{22768}=3','APC UPS Symmetra: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','4a410279dba04d37924eade4bb927228',''),
('18881','{22769} > {$BATTERY.TEMP.MAX.WARN}','APC UPS Symmetra: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','225ccc34992f4c718277b436bfecdc72',''),
('18882','{22770} > 0 and ({22770} > {$UPS.INPUT_FREQ.MAX.WARN} or {22771} < {$UPS.INPUT_FREQ.MIN.WARN})','APC UPS Symmetra: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','03b674d215604dc8acc3449610b05878',''),
('18883','{22772} > 0 and ({22772} > {$UPS.INPUT_VOLT.MAX.WARN} or {22773} < {$UPS.INPUT_VOLT.MIN.WARN})','APC UPS Symmetra: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','bf495f3ffefd4e65af488d91b360539c',''),
('18884','{22774} > {$UPS.OUTPUT.MAX.WARN}','APC UPS Symmetra: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC UPS Symmetra: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','f2790aa869724c5bbeff6031561f2ca4',''),
('18885','{22775}=16','APC UPS Symmetra: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','48a2bee152664ede98bed55c05cc437d',''),
('18886','{22776}=10','APC UPS Symmetra: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','ccd80d5877e0401b8f56f22ca2da2f94',''),
('18887','{22777}=7','APC UPS Symmetra: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','e54fd69ac4354716a107d4d094b387f0',''),
('18888','{22778}=3','APC UPS Symmetra: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','92df44ef170d471394f4cf8ff6882c39',''),
('18889','{22779}=4','APC UPS Symmetra: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','b6f6c160466e43d8b7f210b2efdd8ca3',''),
('18890','{22780}=12','APC UPS Symmetra: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','7d6323e1a03a48efb9f349ecd7e10153',''),
('18891','{22781}=8','APC UPS Symmetra: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','18a31f11313b47c8ab9e9cd4791c1532',''),
('18892','{22782}=11','APC UPS Symmetra: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','142e25b05d1547f0a683f6caee773ef5',''),
('18893','{22783}=6','APC UPS Symmetra: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','b6e22e8295c84fbebb8061c96ddd75f9',''),
('18894','{22784}=9','APC UPS Symmetra: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','1c97c8ca6d6640fe829bf896f989bd91',''),
('18895','{22785}=5','APC UPS Symmetra: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','0683dbba9f4b4480ba15e040b8b83211',''),
('18896','{24401}<>{24402} and length({24403})>0','APC UPS Symmetra: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC UPS Symmetra: System name has changed (new name: {ITEM.VALUE})','5224767a1bee42738c49361ddabfed4b',''),
('18897','({33006}>0 and {33006}<10m)
or ({33006}=0 and {33007}<10m)','APC UPS Symmetra: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC UPS Symmetra: {HOST.NAME} has been restarted (uptime < 10m)','990c0545543c42a78022589838a8a1ff',''),
('18898','{22789}=0','APC UPS Symmetra: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','c0ad0941746546aeb6de2fee087c8252',''),
('18910','{23106}<10m','WildFly Domain: WildFly: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','WildFly Domain: WildFly: {HOST.NAME} has been restarted (uptime < 10m)','926f1767aae74529a972c7b8b09f4442',''),
('18911','{23284}<>{23285} and length({23286})>0','WildFly Domain: WildFly: Version has changed','','0','1','WildFly version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','WildFly Domain: WildFly: Version has changed (new version: {ITEM.VALUE})','76d500211fd9479fafbd0fb7d41ffd68',''),
('18914','{23116}=1','WildFly Server: Failed to fetch info data','','0','2','Zabbix has not received data for items for the last 15 minutes',NULL,'0','0','0','','0','','0','','0','WildFly Server: Failed to fetch info data (or no data for 15m)','8a4fab49eb1e4ebbb1459d9b0f848771',''),
('18915','{23117}<10m','WildFly Server: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','WildFly Server: {HOST.NAME} has been restarted (uptime < 10m)','71db189440ec4355aa06262e3200d47e',''),
('18916','{23293}<>{23294} and length({23295})>0','WildFly Server: Version has changed','','0','1','WildFly version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','WildFly Server: Version has changed (new version: {ITEM.VALUE})','2923ab6f81d64579b6ba778bc0467042',''),
('18917','{23121}=0','WildFly Server: Server needs to restart for configuration change.','','0','2','',NULL,'0','0','0','','0','','0','','0','','c5702304641748e4bb04be89f3a38326',''),
('18918','{23122}=0','WildFly Server: Server controller is not in RUNNING state','','0','2','',NULL,'0','0','0','','0','','0','','0','','81de7058e3b64f73a14e03728dcf1c9b',''),
('18927','{23134} < {$BATTERY.CAPACITY.MIN.WARN}','APC Smart-UPS: Battery has low capacity','','0','4','',NULL,'0','0','0','','0','','0','Current capacity: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has low capacity (below {$BATTERY.CAPACITY.MIN.WARN}%)','0103da3d5f414d8ba1e9914d5c8d5f76',''),
('18928','{23135}=2','APC Smart-UPS: Battery needs replacement','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','09573345f6ce4d648f56117c8755e368',''),
('18929','{23136}=4','APC Smart-UPS: Battery has an internal error condition','','0','3','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','','0','','743aef1e53ee464da48d2953ddc3b85c',''),
('18930','{23137}=3','APC Smart-UPS: Battery is Low','','0','3','The UPS will be unable to sustain the current load, and its services will be lost if power is not restored.',NULL,'0','0','0','','0','','0','','0','','d648d686ff994625bd17f959c311fddd',''),
('18931','{23138} > {$BATTERY.TEMP.MAX.WARN}','APC Smart-UPS: Battery has high temperature','','0','4','',NULL,'0','0','0','','0','','0','Current temperature: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Battery has high temperature (over {$BATTERY.TEMP.MAX.WARN}℃ for {$TIME.PERIOD})','e47ba98e74c94bd3886ac65cd1075359',''),
('18932','{30979} > 0 and ({30979} > {$UPS.INPUT_FREQ.MAX.WARN} or {30980} < {$UPS.INPUT_FREQ.MIN.WARN})','APC Smart-UPS: Unacceptable input frequency','','0','4','',NULL,'0','0','0','','0','','0','Current frequency: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input frequency (out of range {$UPS.INPUT_FREQ.MIN.WARN}-{$UPS.INPUT_FREQ.MAX.WARN}Hz for {$TIME.PERIOD})','3fa853edcebe42eba858e45f1a4465ee',''),
('18933','{30981} > 0 and ({30981} > {$UPS.INPUT_VOLT.MAX.WARN} or {30982} < {$UPS.INPUT_VOLT.MIN.WARN})','APC Smart-UPS: Unacceptable input voltage','','0','4','',NULL,'0','0','0','','0','','0','Current voltage: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Unacceptable input voltage (out of range {$UPS.INPUT_VOLT.MIN.WARN}-{$UPS.INPUT_VOLT.MAX.WARN}V for {$TIME.PERIOD})','74b42439050b48b6bf41abb5bb39808b',''),
('18934','{23143} > {$UPS.OUTPUT.MAX.WARN}','APC Smart-UPS: Output load is high','','0','4','A battery installed has an internal error condition.',NULL,'0','0','0','','0','','0','Current load: {ITEM.LASTVALUE1}','0','APC Smart-UPS: Output load is high (over {$UPS.OUTPUT.MAX.WARN}% for {$TIME.PERIOD})','e099efa7266f44008819979830147665',''),
('18935','{23144}=16','APC Smart-UPS: UPS is Emergency Static Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','edcc1dc962fa4a228b2f5cd3617efbc6',''),
('18936','{23145}=10','APC Smart-UPS: UPS is Hardware Failure Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','869fed8cdd5a4f369e3b1ff2474280de',''),
('18937','{23146}=7','APC Smart-UPS: UPS is Off','','0','3','',NULL,'0','0','0','','0','','0','','0','','378a246b34454d73b2248757be60a7ea',''),
('18938','{23147}=3','APC Smart-UPS: UPS is on battery','','0','3','',NULL,'0','0','0','','0','','0','','0','','286dc25a245f45c3bdcc64925b41aef6',''),
('18939','{23148}=4','APC Smart-UPS: UPS is on Smart Boost','','0','3','',NULL,'0','0','0','','0','','0','','0','','4d02a4c4f25a4efda7bd30def8364972',''),
('18940','{23149}=12','APC Smart-UPS: UPS is On Smart Trim','','0','3','',NULL,'0','0','0','','0','','0','','0','','ae91f99b089748cdaeb0185e31ffe82e',''),
('18941','{23150}=8','APC Smart-UPS: UPS is Rebooting','','0','3','',NULL,'0','0','0','','0','','0','','0','','0bb0ef56d82e4c2a9414468c61fb3a96',''),
('18942','{23151}=11','APC Smart-UPS: UPS is Sleeping Until Power Return','','0','3','',NULL,'0','0','0','','0','','0','','0','','6a5a7e4b17384131a337619ec4a9c1e6',''),
('18943','{23152}=6','APC Smart-UPS: UPS is Software Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','232c98b7ca654c91a20d52ce6f21d7a1',''),
('18944','{23153}=9','APC Smart-UPS: UPS is Switched Bypass','','0','3','',NULL,'0','0','0','','0','','0','','0','','65b8d109db8d4448a7ead131581fcbbe',''),
('18945','{23154}=5','APC Smart-UPS: UPS is Timed Sleeping','','0','3','',NULL,'0','0','0','','0','','0','','0','','917c1f3c82e044a89f2f56a2c8a602a6',''),
('18946','{24386}<>{24387} and length({24388})>0','APC Smart-UPS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: System name has changed (new name: {ITEM.VALUE})','154aad534c35473cb4513cb4e3d4a082',''),
('18947','({32996}>0 and {32996}<10m)
or ({32996}=0 and {32997}<10m)','APC Smart-UPS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','APC Smart-UPS: {HOST.NAME} has been restarted (uptime < 10m)','7793a5e111c6466584ef6610aae707c1',''),
('18948','{23159}=0','APC Smart-UPS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','6e0f9b15effd4c9e9c416a99fd8f4517',''),
('18963','{23189} < {$CLOUDFLARE.CACHED_BANDWIDTH.MIN.WARN}','Cloudflare: Cached bandwidth is too low','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Cloudflare: Cached bandwidth is too low (less than {$CLOUDFLARE.CACHED_BANDWIDTH.MIN.WARN}% for 3 last measurements)','acf573785c394924aae8ef74b2683fd1',''),
('18964','{23190} > {$CLOUDFLARE.ERRORS.MAX.WARN}','Cloudflare: Ratio of non-2xx responses is too high','','0','3','A large number of errors can indicate a malfunction of the site.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Cloudflare: Ratio of non-2xx responses is too high (more than {$CLOUDFLARE.ERRORS.MAX.WARN}% for 3 last measurements)','e76f4a61dd094419b6e0af706758e545',''),
('18967','{23237} > {$NGINX.DROP_RATE.MAX.WARN}','NGINX Plus: High connections drop rate','','0','2','The rate of dropped connections is greater than `{$NGINX.DROP_RATE.MAX.WARN}` for the last 5 minutes.',NULL,'0','0','0','','0','','0','','0','NGINX Plus: High connections drop rate (more than {$NGINX.DROP_RATE.MAX.WARN} for 5m)','91c9dab8147a4d0086019119e4e55b5e',''),
('18968','length({23238})>0','NGINX Plus: Server response error','','0','4','',NULL,'0','0','0','','0','','0','','0','NGINX Plus: Server response error (text: {ITEM.VALUE})','e444c708371748bd831bba6c8d9a92e0',''),
('18969','{23239}=1','NGINX Plus: Failed to fetch info data','','0','2','Zabbix has not received any data for metrics for the last 30 minutes',NULL,'0','0','0','','0','','1','','0','NGINX Plus: Failed to fetch info data (or no data for 30m)','396fb4be618e45578566971d5399d611',''),
('18970','{23240}<10m','NGINX Plus: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','NGINX Plus: {HOST.NAME} has been restarted (uptime < 10m)','95622a29bd58444b9f0bd985db99f922',''),
('18971','{23241}<>{23242} and length({23243})>0','NGINX Plus: Version has changed','','0','1','The Nginx version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','NGINX Plus: Version has changed (new version: {ITEM.VALUE})','a91ff018fe4f4a1495b08adeb2b0005f',''),
('18978','{33797}>{$ZABBIX.SERVER.UTIL.MAX:"service manager"}','Zabbix server: Utilization of service manager processes is high','','0','3','Indicates potential performance issues with the service manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33797}<{$ZABBIX.SERVER.UTIL.MIN:"service manager"}','0','','0','','0','Zabbix server: Utilization of service manager processes over {$ZABBIX.SERVER.UTIL.MAX:"service manager"}%','c4cdbce205e843d6b882503961a15376',''),
('18979','{33803}>{$ZABBIX.SERVER.UTIL.MAX:"trigger housekeeper"}','Zabbix server: Utilization of trigger housekeeper processes is high','','0','3','Indicates potential performance issues with the trigger housekeeper, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33803}<{$ZABBIX.SERVER.UTIL.MIN:"trigger housekeeper"}','0','','0','','0','Zabbix server: Utilization of trigger housekeeper processes over {$ZABBIX.SERVER.UTIL.MAX:"trigger housekeeper"}%','5ffa02f393d34c49bcb9eed2b2b89704',''),
('18980','{23305}<>{23306} and length({23307})>0','Zabbix server: Version has changed','','0','1','Zabbix server version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Zabbix server: Version has changed (new version: {ITEM.VALUE})','456403a2063c4e2298f9e3f60a7a3180',''),
('18984','{33911}>{$ZABBIX.SERVER.UTIL.MAX:"service manager"}','Zabbix server: Utilization of service manager processes is high','','0','3','Indicates potential performance issues with the service manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33911}<{$ZABBIX.SERVER.UTIL.MIN:"service manager"}','0','','0','','0','Zabbix server: Utilization of service manager processes over {$ZABBIX.SERVER.UTIL.MAX:"service manager"}%','001c9e2027ca4e7c8f5dc5b78681c573',''),
('18985','{33917}>{$ZABBIX.SERVER.UTIL.MAX:"trigger housekeeper"}','Zabbix server: Utilization of trigger housekeeper processes is high','','0','3','Indicates potential performance issues with the trigger housekeeper, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33917}<{$ZABBIX.SERVER.UTIL.MIN:"trigger housekeeper"}','0','','0','','0','Zabbix server: Utilization of trigger housekeeper processes over {$ZABBIX.SERVER.UTIL.MAX:"trigger housekeeper"}%','9c0daf6e85884122aa8c5b8432709c92',''),
('19012','{23734}<10m','Cisco ASAv: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco ASAv: {HOST.NAME} has been restarted (uptime < 10m)','7fcf46583d2b42f4be6758e85784f28f',''),
('19013','{23735}=0','Cisco ASAv: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','9ee945a0b0b942d7a7e3fcf218f0e82f',''),
('19018','{25022}<>{25023} and length({25024})>0','F5 Big-IP: Chassis has been replaced','','0','1','Chassis serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','F5 Big-IP: Chassis has been replaced (new serial number received)','8a55167ddebb43f2ac8f6d028aef87c2',''),
('19019','{23870}<10m','F5 Big-IP: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','F5 Big-IP: {HOST.NAME} has been restarted (uptime < 10m)','551fd3b77d144ed58f138865e4862901',''),
('19020','{23871}=0','F5 Big-IP: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','9ec4425af8dd4cf59dcb3146e6a8263c',''),
('19029','{23961}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','40839f3008b84e3c9ffa8858bd2ab616',''),
('19030','{23962}<>{23963} and length({23964})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','02ba3941993f48ca8d5f40b3b19804e8',''),
('19031','{23965}<>"AAM1212-51 / IES-612"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel AAM1212-51 / IES-612, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','5a3f459afc4f42fb90849e98c7639a96',''),
('19032','{23966}<>{23967} and length({23968})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','7528520bca7c4524b7451aeaca440cc5',''),
('19033','{23969}=0','ZYXEL: Port {#SNMPINDEX} alarm','','0','3','The slot reported an error.',NULL,'0','0','0','','0','','0','','0','','eec541b07a434770b2a3301825cc5e82',''),
('19034','({32324}>0 and {32324}<10m) or ({32324}=0 and {32325}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','819190f68248439292fc4622c3eec5a9',''),
('19043','{23983}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','3bbbd93c114f4bf5b8f4788ca6825afd',''),
('19044','{23984}>{$CPU.UTIL.CRIT}','ZYXEL: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','ZYXEL: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','3cf67f911a854d2ebeb9e006f3f97738',''),
('19045','{23985}<>{23986} and length({23987})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','bd6d0fe201094c00b6c93d7c04c27729',''),
('19046','{23988}<>"ES3500-8PD"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel ES3500-8PD, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','e03ca45643354a18a9d6ffbb38a07654',''),
('19047','{23989}<>{23990} and length({23991})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','83548aba74c148e28e6611d5abfb9694',''),
('19048','({32326}>0 and {32326}<10m) or ({32326}=0 and {32327}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','eb7a268bfa324366953221e3c1788127',''),
('19056','{24004}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','07b74d3face24c838c7efe8dfb87564e',''),
('19057','{24005}>{$CPU.UTIL.CRIT}','ZYXEL: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','ZYXEL: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','2052d9e6becd48e5a3aed8037eaf9e87',''),
('19058','{24006}<>{24007} and length({24008})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','ecde6db248674039a30874f29e704e65',''),
('19059','{24009}<>"GS-4012F"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel GS-4012F, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','1ba1faabe15c4d46adaa4dc74c5dc05c',''),
('19060','{24010}<>{24011} and length({24012})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','ae941404115d4b10809bce603528ceaa',''),
('19061','({32328}>0 and {32328}<10m) or ({32328}=0 and {32329}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','93c70a5dd2504d0d9b13a17af942d45e',''),
('19066','{24020}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','73967d1d3d01458c8e947a1aacb838b0',''),
('19067','not({24021}="IES-5000" or {24021}="IES-5005")','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel IES-500x, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','d4b378535f5c4299af1295029e94f9d1',''),
('19068','({32330}>0 and {32330}<10m) or ({32330}=0 and {32331}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','d618295a763f42cd9063fad5cd600c34',''),
('19088','{24056}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','41eb76d6be3e47b8b0ca1296470372aa',''),
('19089','{24057}<>"IES-6000"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel IES-6000, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','7f6f8bdde2644182a892792ff2bb7c68',''),
('19090','({32332}>0 and {32332}<10m) or ({32332}=0 and {32333}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','7a52520cc3dc4350bd7aa14260899f1c',''),
('19110','{24092}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','40466f29b8e54dc88cb49e818fc48281',''),
('19111','{24093}<>{24094} and length({24095})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','b64e891456674457ab4abf994b097277',''),
('19112','{24096}<>"IES1248-51"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel IES1248-51, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','21b638f9f1154b6bb78a652d8e54c1c2',''),
('19113','{24097}<>{24098} and length({24099})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','2f2972169c164053a8d439b0e572b0c6',''),
('19114','{24100}=0','ZYXEL: Port {#SNMPINDEX} alarm','','0','3','The slot reported an error.',NULL,'0','0','0','','0','','0','','0','','6b1b1b27241f42229e8b159320371356',''),
('19115','({32334}>0 and {32334}<10m) or ({32334}=0 and {32335}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','bbccceac3dc24b9ab76a820fe5be4788',''),
('19125','{24115}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','0e38d148fc29439488b3b23ee308b1d9',''),
('19126','{24116}>{$CPU.UTIL.CRIT}','ZYXEL: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','ZYXEL: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','247a25a4976a45eca78853aea112cdd6',''),
('19127','{24117}<>{24118} and length({24119})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','7c4cfa75447a4eeda874d916d052eb6e',''),
('19128','{24120}<>"MES-3528"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel MES-3528, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','b98e244abe2a4bd481be50048234afe6',''),
('19129','{24121}<>{24122} and length({24123})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','d08bc1ffb11e4bbc98851c30595e996c',''),
('19130','({32336}>0 and {32336}<10m) or ({32336}=0 and {32337}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','d138c874f4de4f3a97a0c615d589826a',''),
('19135','{24133}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','c33a4bffd5464934b4b9f1e7160806e1',''),
('19136','{24134}>{$CPU.UTIL.CRIT}','ZYXEL: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','ZYXEL: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','0d31c154f8f34ed18a99558f7839bbb6',''),
('19137','{24135}<>{24136} and length({24137})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','db567c7693b6437e89ef7a5b78c889f9',''),
('19138','{24138}<>"MES3500-10"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel MES3500-10, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','27f1cb5a297c4b1eafd4056317a37f01',''),
('19139','{24139}<>{24140} and length({24141})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','ee14abdf61b04a90adf6e2afcc3d73f4',''),
('19140','({32338}>0 and {32338}<10m) or ({32338}=0 and {32339}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','9899ada82b0e4507948a8a0068e5640d',''),
('19148','{24154}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','96435fde17384c6bb4f9811ad9ca184a',''),
('19149','{24155}>{$CPU.UTIL.CRIT}','ZYXEL: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','ZYXEL: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','911d1c7e921f43af8ab3c0035be57a27',''),
('19150','{24156}<>{24157} and length({24158})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','f3daea29a34b4cf992d3c23ba8a64d2e',''),
('19151','{24159}<>"MES3500-24"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel MES3500-24, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','ab363c150ecd447ea4d3a3a9c311b992',''),
('19152','{24160}<>{24161} and length({24162})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','a475d29129664eec82fc7ed85cb74df9',''),
('19153','({32340}>0 and {32340}<10m) or ({32340}=0 and {32341}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','c389b0db83bc404e8cb84ce65db79700',''),
('19161','{24175}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','60787fd1204b42bfb515b1b204c1d14f',''),
('19162','{24176}>{$CPU.UTIL.CRIT}','ZYXEL: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','ZYXEL: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','b1ca06637dbe4c9ca84e2811e780d5d5',''),
('19163','{24177}<>{24178} and length({24179})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','de7d7e7d976c4b9894259c4e7fb5a4dd',''),
('19164','{24180}<>"MGS-3712"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel MGS-3712, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','e0b4c4f09f6f496cb035af320fcf96a0',''),
('19165','{24181}<>{24182} and length({24183})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','4a9495748e09477ca5f12443fff533c9',''),
('19166','({32342}>0 and {32342}<10m) or ({32342}=0 and {32343}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','eefe29ad784d40d3980a4cb1118dd816',''),
('19174','{24196}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','c4244d60e8aa4cc380442992c031b2fd',''),
('19175','{24197}>{$CPU.UTIL.CRIT}','ZYXEL: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','ZYXEL: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','084cf3c89c9c48eeac9131d831a4f71b',''),
('19176','{24198}<>{24199} and length({24200})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','fbf62d3f9ce54baab9a16f3e123811ef',''),
('19177','{24201}<>"MGS-3712F"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel MGS-3712F, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','bf3d28b088db48a59aaa9e88f6b13cb8',''),
('19178','{24202}<>{24203} and length({24204})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','ccb3fe676cd742af954b8c5e7898e5f0',''),
('19179','({32344}>0 and {32344}<10m) or ({32344}=0 and {32345}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','6a31fdd61b9f4aa99c8ad15ff243c6b2',''),
('19187','{24217}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d80bc493096b4da4857651e7e28829e7',''),
('19188','{24218}>{$CPU.UTIL.CRIT}','ZYXEL: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','ZYXEL: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','7bf51ce2b7a64f3f8151edc224c601e8',''),
('19189','{24219}<>{24220} and length({24221})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','182e8b14935445268c096a3e4fdb5795',''),
('19190','{24222}>{$MEMORY.UTIL.MAX}','ZYXEL: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','ZYXEL: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','d3a4dca93ad946589b1b83e0fe647dde',''),
('19191','{24223}<>"MES3500-24S"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel MES3500-24S series, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','96c011542d5b4473934e0de9e442479c',''),
('19192','{24224}<>{24225} and length({24226})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','90268ffbf33049d6adc6ed96badd67ec',''),
('19193','({32346}>0 and {32346}<10m) or ({32346}=0 and {32347}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','6c8fce36fd9c49569be0ba2bfb70f478',''),
('19201','{24239}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','3bf5d80d383e4e98853caa02063d69c9',''),
('19202','{24240}>{$CPU.UTIL.CRIT}','ZYXEL: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','ZYXEL: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','96ed7ee3906541ea9cb2c95cf4da1a62',''),
('19203','{24241}<>{24242} and length({24243})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','3785991565b948c2a1e1a2a140c42df4',''),
('19204','{24244}>{$MEMORY.UTIL.MAX}','ZYXEL: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','ZYXEL: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','1a999dff1dd9481083681741e71aba76',''),
('19205','not({24245}="MGS3520-28" or {24245}="MGS3520-28F")','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel MGS3520-28x series, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','d72bc70a67014d818d593d6c484fc9ee',''),
('19206','{24246}<>{24247} and length({24248})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','e953886c5a464fc18bb1e221d801901c',''),
('19207','({32348}>0 and {32348}<10m) or ({32348}=0 and {32349}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','308761b6dffb44c7b827f6ca76312233',''),
('19215','{24261}=0','ZYXEL: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','fd9a321842544253896e5a4c1a58ced3',''),
('19216','{24262}>{$CPU.UTIL.CRIT}','ZYXEL: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','ZYXEL: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','20f368f955f74fc9b8380b1bbff7e057',''),
('19217','{24263}<>{24264} and length({24265})>0','ZYXEL: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','5da304609e8c45d980c46579f6848f0a',''),
('19218','{24266}<>"XGS-4728F"','ZYXEL: Template does not match hardware','','0','1','This template is for Zyxel XGS-4728F, but connected to {ITEM.VALUE}',NULL,'0','0','0','','0','','0','','0','','0329f3f5aa6a4315a4f3611ad662103e',''),
('19219','{24267}<>{24268} and length({24269})>0','ZYXEL: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','ZYXEL: Device has been replaced (new serial number received)','4df7c31c3079411baabd4ae66e580652',''),
('19220','({32350}>0 and {32350}<10m) or ({32350}=0 and {32351}<10m)','ZYXEL: Host has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','ZYXEL: {HOST.NAME} has been restarted (uptime < 10m)','36b9a7d3d3fb45f782a5ea05de6816f9',''),
('19229','{24447}<>{24448} and length({24449})>0','Cisco UCS Manager: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco UCS Manager: System name has changed (new name: {ITEM.VALUE})','622ac72c0e534bba94bb93636e4dc103',''),
('19230','({32382}>0 and {32382}<10m) or ({32382}=0 and {32383}<10m)','Cisco UCS Manager: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco UCS Manager: {HOST.NAME} has been restarted (uptime < 10m)','9026e680b409424e8fa29934878cb771',''),
('19231','{24451}=0','Cisco UCS Manager: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','010a749e3a3242cd8e3ea30459fae5a4',''),
('19464','{24788}<>{24789} and length({24790})>0','HPE ProLiant BL460: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant BL460: Device has been replaced (new serial number received)','1bc442ba67dc42d298d98feb845d8730',''),
('19465','{24791}<>{24792} and length({24793})>0','HPE ProLiant BL460: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant BL460: System name has changed (new name: {ITEM.VALUE})','87570f607b174ebe887920034a1be1ef',''),
('19466','{24794}={$HEALTH.STATUS.CRIT}','HPE ProLiant BL460: System status is in critical state','','0','4','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','4d7ac12aec954df2b369ddd0536d3bd5',''),
('19467','{24795}={$HEALTH.STATUS.WARN}','HPE ProLiant BL460: System status is in warning state','','0','2','Please check the device for warnings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','9ffbca9c012541b9a36956b4ae06d339',''),
('19468','({32396}>0 and {32396}<10m) or ({32396}=0 and {32397}<10m)','HPE ProLiant BL460: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant BL460: {HOST.NAME} has been restarted (uptime < 10m)','9159ee66dbe4498cba29daca24ddcb5f',''),
('19469','{24797}=0','HPE ProLiant BL460: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','236a5d37e58a415aa81db6e59eb826dc',''),
('19510','{24840}<>{24841} and length({24842})>0','HPE ProLiant BL920: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant BL920: Device has been replaced (new serial number received)','9eb77df5f95149e49d63a7191e68756c',''),
('19511','{24843}<>{24844} and length({24845})>0','HPE ProLiant BL920: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant BL920: System name has changed (new name: {ITEM.VALUE})','c0eed9d2eccc4ae99128a318de92df8d',''),
('19512','{24846}={$HEALTH.STATUS.CRIT}','HPE ProLiant BL920: System status is in critical state','','0','4','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','187f7a3872a2481f962f16c422911827',''),
('19513','{24847}={$HEALTH.STATUS.WARN}','HPE ProLiant BL920: System status is in warning state','','0','2','Please check the device for warnings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','51c633cbed0d4684b2e0619e2f0ab64d',''),
('19514','({32398}>0 and {32398}<10m) or ({32398}=0 and {32399}<10m)','HPE ProLiant BL920: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant BL920: {HOST.NAME} has been restarted (uptime < 10m)','97f107c88b6048f1b74412e8dfedc857',''),
('19515','{24849}=0','HPE ProLiant BL920: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','35cce5a461c04163a0575d7f831ea3d9',''),
('19556','{24892}<>{24893} and length({24894})>0','HPE ProLiant DL360: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant DL360: Device has been replaced (new serial number received)','1316d7def24a4a80adfdf4bc8ac5a12c',''),
('19557','{24895}<>{24896} and length({24897})>0','HPE ProLiant DL360: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant DL360: System name has changed (new name: {ITEM.VALUE})','6431a1a0b8494b50bcbd18e283e7158e',''),
('19558','{24898}={$HEALTH.STATUS.CRIT}','HPE ProLiant DL360: System status is in critical state','','0','4','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','6cc840d5bccc4f1abfd7df6a161154ad',''),
('19559','{24899}={$HEALTH.STATUS.WARN}','HPE ProLiant DL360: System status is in warning state','','0','2','Please check the device for warnings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','eab6760dda124629a9edcb2218ad3ad3',''),
('19560','({32400}>0 and {32400}<10m) or ({32400}=0 and {32401}<10m)','HPE ProLiant DL360: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant DL360: {HOST.NAME} has been restarted (uptime < 10m)','383e0e2d556d4354ae50f68c94333ded',''),
('19561','{24901}=0','HPE ProLiant DL360: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','0b91663d4b684e46aaccdf480d1622f0',''),
('19602','{24944}<>{24945} and length({24946})>0','HPE ProLiant DL380: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant DL380: Device has been replaced (new serial number received)','bd81b8c420904f0bafa4fbf90d195967',''),
('19603','{24947}<>{24948} and length({24949})>0','HPE ProLiant DL380: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant DL380: System name has changed (new name: {ITEM.VALUE})','168b1742abc340558631a577a1a3c4d9',''),
('19604','{24950}={$HEALTH.STATUS.CRIT}','HPE ProLiant DL380: System status is in critical state','','0','4','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','e9bf032edb2e45f0b64cb904bf8d8403',''),
('19605','{24951}={$HEALTH.STATUS.WARN}','HPE ProLiant DL380: System status is in warning state','','0','2','Please check the device for warnings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','537c411a3d454a8b9dc64378e0e9a6cd',''),
('19606','({32402}>0 and {32402}<10m) or ({32402}=0 and {32403}<10m)','HPE ProLiant DL380: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','HPE ProLiant DL380: {HOST.NAME} has been restarted (uptime < 10m)','9612f37005e5420582d499d7cb84a24e',''),
('19607','{24953}=0','HPE ProLiant DL380: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','97c3665497ae46eb91d81c14c5f4ac06',''),
('19648','{25008}>={$AMI.TRUNK_ACTIVE_CHANNELS_TOTAL.MAX.WARN:"IAX"}','Asterisk: Total number of active channels of IAX trunks is too high','','0','2','The IAX trunks may not be able to process new calls.',NULL,'0','0','0','','0','','0','','0','Asterisk: Total number of active channels of IAX trunks is too high (over {$AMI.TRUNK_ACTIVE_CHANNELS_TOTAL.MAX.WARN:"IAX"} for 10m)','0ae0a5b6123a42dd9722219e5e5839df',''),
('19649','{25009}>={$AMI.TRUNK_ACTIVE_CHANNELS_TOTAL.MAX.WARN:"PJSIP"}','Asterisk: Total number of active channels of PJSIP trunks is too high','','0','2','The PJSIP trunks may not be able to process new calls.',NULL,'0','0','0','','0','','0','','0','Asterisk: Total number of active channels of PJSIP trunks is too high (over {$AMI.TRUNK_ACTIVE_CHANNELS_TOTAL.MAX.WARN:"PJSIP"} for 10m)','9b158fe0efb4416cb6ad5d53b38c3e38',''),
('19650','{25010}>={$AMI.TRUNK_ACTIVE_CHANNELS_TOTAL.MAX.WARN:"SIP"}','Asterisk: Total number of active channels of SIP trunks is too high','','0','2','The SIP trunks may not be able to process new calls.',NULL,'0','0','0','','0','','0','','0','Asterisk: Total number of active channels of SIP trunks is too high (over {$AMI.TRUNK_ACTIVE_CHANNELS_TOTAL.MAX.WARN:"SIP"} for 10m)','d2fde5d26d284a129346a12ba0949b60',''),
('19651','{25011}=1','Travis CI: Failed to fetch home page','','0','2','Zabbix has not received any data for items for the last 30 minutes.',NULL,'0','0','0','','0','','1','','0','Travis CI: Failed to fetch home page (or no data for 30m)','6baed695cac34d349a42ab6e8295910d',''),
('19652','{25012}=0','Travis CI: Service is unavailable','','0','4','Travis API is unavailable. Please check if the correct macros are set.',NULL,'0','0','0','','0','','1','','0','','e8398acab5a74505a85ade5d3ca5f590',''),
('19655','{25015}=0','InfluxDB: Health check was failed','','0','4','The InfluxDB instance is not available or unhealthy.',NULL,'0','0','0','','0','','0','','0','','de130833b4514481aa56d3ba06e648fc',''),
('19656','{25016}>{$INFLUXDB.TASK.RUN.FAIL.MAX.WARN}','InfluxDB: Too many tasks failure runs','','0','2','"Number of failure runs completed across all tasks is too high."',NULL,'0','0','0','','0','','0','','0','InfluxDB: Too many tasks failure runs (over {$INFLUXDB.TASK.RUN.FAIL.MAX.WARN} for 5m)','f0d2137905bc477f979d035c06111844',''),
('19657','{25017}<10m','InfluxDB: Service has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','InfluxDB: Service has been restarted (uptime < 10m)','335f27fb002544838f7150b11238d86b',''),
('19658','{25018}<>{25019} and length({25020})>0','InfluxDB: Version has changed','','0','1','InfluxDB version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','InfluxDB: Version has changed (new version: {ITEM.VALUE})','d2b02cc426c748608968ae08c0823461',''),
('19660','{25025}>8 and {25026}>6','F5 Big-IP: Cluster not in sync','','0','2','',NULL,'0','0','0','','0','','1','{ITEM.LASTVALUE}','0','F5 Big-IP: Cluster not in sync: {ITEM.VALUE}','f93a7ff7cc614c0b84789f325ebb662b',''),
('19661','{25027}=2','F5 Big-IP: Changes have been made on the device not sync','','0','2','Changes have been made on the device not sync to the device group, requires user intervention',NULL,'0','0','0','','0','','1','{ITEM.LASTVALUE}','0','F5 Big-IP: Changes have been made on the device not sync to the device group: {ITEM.VALUE}','098fe258e8cc4216b0c1800913ba8e18',''),
('19662','{25028}=4','F5 Big-IP: The device is inconsistent with the device group','','0','2','The device is inconsistent with the device group, requires user intervention',NULL,'0','0','0','','0','','1','{ITEM.LASTVALUE}','0','F5 Big-IP: The device is inconsistent with the device group: {ITEM.VALUE}','eb3517626c6d425f9b88a2bc35641ab6',''),
('19679','{25060}<>{25061} and length({25062})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','79b791b5ce1a4e5e8f68b561aeaac838',''),
('19680','{25063}<>{25064} and length({25065})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','a981ac3d5e7843049eb581ab284edd04',''),
('19681','{25066}<>{25067} and length({25068})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','f7e4983c483944869d44fe5ea4289786',''),
('19682','{25069}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','6a571f6691ec459bbc63e1a8dece1c04',''),
('19707','{25119}<>{25120} and length({25121})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','7469aef39ea84a729b87d06d3dd0e9af',''),
('19708','{25122}<>{25123} and length({25124})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','a30f1485711d4a649503638fd3a7d702',''),
('19709','{25125}<>{25126} and length({25127})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','8574af8f375a4443bbf030ebf8d904b5',''),
('19710','{25128}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','18ae9503588a4d398f387ab0d9015e26',''),
('19735','{25178}<>{25179} and length({25180})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','de61b57b4fd54166a207bc040aa482a4',''),
('19736','{25181}<>{25182} and length({25183})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','1776f8b97fba4feb962b0a47e4780076',''),
('19737','{25184}<>{25185} and length({25186})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','0b8bd128fed047c591b839f3f46412dd',''),
('19738','{25187}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','2dec63fe94b943549c8351fe1e737975',''),
('19763','{25237}<>{25238} and length({25239})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','4ff0ad1fe7a043f28e46403ab4ce500b',''),
('19764','{25240}<>{25241} and length({25242})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','0abb489d471e414b84d9bfe5d6d0e453',''),
('19765','{25243}<>{25244} and length({25245})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','3146fc39809741a09a46852ef392b694',''),
('19766','{25246}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','4093f81ecb9f4320b5c5ca719a6b8574',''),
('19791','{25296}<>{25297} and length({25298})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','8012e0275fc24d9e9688cfccb3134aae',''),
('19792','{25299}<>{25300} and length({25301})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','c6e011ff0a1f41c5b90bb8fba507fe7d',''),
('19793','{25302}<>{25303} and length({25304})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','f8ac6aaa8c06474d9a9b86e5e43b5ed5',''),
('19794','{25305}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','63e95c315b6f422e9d4f6e532e847e9c',''),
('19819','{25355}<>{25356} and length({25357})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','e0decdba5c7a44ef9983da4d0912ba37',''),
('19820','{25358}<>{25359} and length({25360})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','ee34d0bdac3f4b0489fc96a3feecb72b',''),
('19821','{25361}<>{25362} and length({25363})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','65ac535fb0114cc098bd89d1e2a5cfed',''),
('19822','{25364}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','1ed5e95e003d4119bd578ac4f572ba16',''),
('19847','{25414}<>{25415} and length({25416})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','565c94a00dde43c1af72f8c2d00edcb5',''),
('19848','{25417}<>{25418} and length({25419})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','6d02cc3ff4144efda53554446feb0058',''),
('19849','{25420}<>{25421} and length({25422})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','18900918495f4dd99cbde564a071bf34',''),
('19850','{25423}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','d89ab73e0c534f84ae9481a1a48d5064',''),
('19875','{25473}<>{25474} and length({25475})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','a42442ce9d7d4a378964296eed6a6b33',''),
('19876','{25476}<>{25477} and length({25478})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','2da3a78731324233be1563691f353d04',''),
('19877','{25479}<>{25480} and length({25481})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','855a1e17110e49eaaaf4dd263f16a591',''),
('19878','{25482}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','9a83e6b6a0874a49a983cb610a7e0e50',''),
('19903','{25532}<>{25533} and length({25534})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','26d7b5b5fc4149d4869a4e3a94173172',''),
('19904','{25535}<>{25536} and length({25537})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','79405589edba4a878d7d2ab5d0399076',''),
('19905','{25538}<>{25539} and length({25540})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','1ed2e0368bb94a4fbfa8a82764b3b40d',''),
('19906','{25541}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','03cdc40813dd4d5093512db3c5e574ff',''),
('19931','{25591}<>{25592} and length({25593})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','385231b6c7eb4ce6a275969b437c8d44',''),
('19932','{25594}<>{25595} and length({25596})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','bb2cc5758a154bc0ad07138e87f353a4',''),
('19933','{25597}<>{25598} and length({25599})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','ff7510d9e2d44057a089b9486af74971',''),
('19934','{25600}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','a7fa3a261f0c4362938700ff8954cdc9',''),
('19959','{25650}<>{25651} and length({25652})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','6172f360bcca4bc6a105a5093be8665c',''),
('19960','{25653}<>{25654} and length({25655})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','80072866ba994094a279eb45020311d1',''),
('19961','{25656}<>{25657} and length({25658})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','d66d2b488b784574943c90f20d0153ce',''),
('19962','{25659}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','02a8b7e7ebbb4d1baf5ee155167e36ba',''),
('19987','{25709}<>{25710} and length({25711})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','324d699f4767400e88e16f37ffcd2abd',''),
('19988','{25712}<>{25713} and length({25714})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','53e8fc3eac46426fbce375cc2ce983c8',''),
('19989','{25715}<>{25716} and length({25717})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','2a0736cbd3324122b51c4ac4629c1323',''),
('19990','{25718}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','8246aab86f954be8968169f55889a842',''),
('20015','{25768}<>{25769} and length({25770})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','6739b5af597443449dcfb946d2b89393',''),
('20016','{25771}<>{25772} and length({25773})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','dfc2b8c7f27049a6bd51c283cc6a29ce',''),
('20017','{25774}<>{25775} and length({25776})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','dc48fc089a314b7ebae646f2dfb925c5',''),
('20018','{25777}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','fdcc98f2475247f29fdf48c3a4a69058',''),
('20043','{25827}<>{25828} and length({25829})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','07248a02609a4964be773df77f86f30a',''),
('20044','{25830}<>{25831} and length({25832})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','a79318151008414cb9a0c3d788b76f76',''),
('20045','{25833}<>{25834} and length({25835})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','829598b7b1b4404bbd959ae186734251',''),
('20046','{25836}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','7f44b9ee964f4ae798f3af4c12799e12',''),
('20071','{25886}<>{25887} and length({25888})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','6729f53f42ff445c8ab26b91cdb811e2',''),
('20072','{25889}<>{25890} and length({25891})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','24e52c80e5544295b778c677d0de35b2',''),
('20073','{25892}<>{25893} and length({25894})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','8846801d462142938e7e0683dd481087',''),
('20074','{25895}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','d9f9ee61646a4881bcb34a5e564738f3',''),
('20099','{25945}<>{25946} and length({25947})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','0f66010aec32455eb56414c1ba576982',''),
('20100','{25948}<>{25949} and length({25950})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','59c929b470d342b691b01b5d12f87456',''),
('20101','{25951}<>{25952} and length({25953})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','c9fb96d72f6942d1b4320014b2e40b0c',''),
('20102','{25954}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','72863d07fe654e78b740e2f48e0cebe5',''),
('20127','{26004}<>{26005} and length({26006})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','f0c59541e6df4c649e7c2ef76d7bda4b',''),
('20128','{26007}<>{26008} and length({26009})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','a1cf2d27ddc447988aa808318aef167f',''),
('20129','{26010}<>{26011} and length({26012})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','9bfebd1764bb4acc82fa8c7f175c0b87',''),
('20130','{26013}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','9af92a1dddd0405587bb090b8fd5757d',''),
('20155','{26063}<>{26064} and length({26065})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','70a98e004bd34fb48e9c410ca52f4bc0',''),
('20156','{26066}<>{26067} and length({26068})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','e4da63844b774f4eb9e0188f659f256d',''),
('20157','{26069}<>{26070} and length({26071})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','9f738a1caee34259a3d38e52ddb6c791',''),
('20158','{26072}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','640203769816409d883d5ba38a6ff4e5',''),
('20183','{26122}<>{26123} and length({26124})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','66ea5bdabba4438ba8f9959e0c4b24ec',''),
('20184','{26125}<>{26126} and length({26127})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','425777ce38e54daba1f6501bd4f6bf6b',''),
('20185','{26128}<>{26129} and length({26130})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','73aec359593a4ce9ae07e66a39ea2275',''),
('20186','{26131}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','179753654a4849d48935c10417994eb7',''),
('20211','{26181}<>{26182} and length({26183})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','32127aca202644c5915255006e9544b5',''),
('20212','{26184}<>{26185} and length({26186})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','7bb01da1713c42c1ab28c1ae2adc1260',''),
('20213','{26187}<>{26188} and length({26189})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','28568c2163ee4a0aa262241064922c7d',''),
('20214','{26190}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','7224d01c717a4dd3800fbd8d8e9399b8',''),
('20239','{26240}<>{26241} and length({26242})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','58b860a92baa43158419a843ae89687f',''),
('20240','{26243}<>{26244} and length({26245})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','54368f9d9e9f494ba55f8f5fac20196b',''),
('20241','{26246}<>{26247} and length({26248})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','dd39ada0b3b14009968866d766e9e16d',''),
('20242','{26249}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','de55f957c95d404380cb490126f88e3d',''),
('20267','{26299}<>{26300} and length({26301})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','0d646e6c03f14c259b81862187a6eec1',''),
('20268','{26302}<>{26303} and length({26304})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','992d3bd742224ad7abc375d20e60e1af',''),
('20269','{26305}<>{26306} and length({26307})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','b3e063c9221d4bf69acb21a16859bb15',''),
('20270','{26308}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','95ac8c277d8940ecb1545be2dc514c54',''),
('20295','{26358}<>{26359} and length({26360})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','65e43afe1d04447fb334d5efbd76c185',''),
('20296','{26361}<>{26362} and length({26363})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','3a3ac7e0d5fc4feca67eb2447fcbcf34',''),
('20297','{26364}<>{26365} and length({26366})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','2f18268819414337aca3f919343d6577',''),
('20298','{26367}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','cfd67344627840a081d286d8188c0888',''),
('20323','{26417}<>{26418} and length({26419})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','f91e54b227304a688092ffcbabf88d41',''),
('20324','{26420}<>{26421} and length({26422})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','aeb6d1d52ee24d7393a4a5a31f7267fb',''),
('20325','{26423}<>{26424} and length({26425})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','be2544b8b967408288a750c82a8f9059',''),
('20326','{26426}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','4fbf859b65774291850b37f700945a36',''),
('20351','{26476}<>{26477} and length({26478})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','db665e87151d441395fce421949a9bb0',''),
('20352','{26479}<>{26480} and length({26481})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','a5e267a8584a4d099f0d36d30ce17d0b',''),
('20353','{26482}<>{26483} and length({26484})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','9fe8a423c0a8411191337e48818cd835',''),
('20354','{26485}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','ef73c971f14444f18a8b0956c8bd5796',''),
('20379','{26535}<>{26536} and length({26537})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','98b8b373def34eec9e814c039dcfb20b',''),
('20380','{26538}<>{26539} and length({26540})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','da1a900485be412996f607b9669daf83',''),
('20381','{26541}<>{26542} and length({26543})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','41ec834afc7a49409cc9996459b15452',''),
('20382','{26544}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','86bc4c3dbd024d8d84a90f25fa8c0932',''),
('20407','{26594}<>{26595} and length({26596})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','656a970a84fd4f65adc021b317f8db04',''),
('20408','{26597}<>{26598} and length({26599})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','ba6f7f02b3dc47b6a15a40f81c86ee1e',''),
('20409','{26600}<>{26601} and length({26602})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','b720a6b27e14473db885682085ce07e1',''),
('20410','{26603}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','6d68e3acb5a34a9eb68f6ea1e329241d',''),
('20435','{26653}<>{26654} and length({26655})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','7e708c7bf76445959909bf03adf676dc',''),
('20436','{26656}<>{26657} and length({26658})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','0b2e29ba173346248fb4d799f7e16cf1',''),
('20437','{26659}<>{26660} and length({26661})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','b0c3673f0aee4a23a7811f54416924bf',''),
('20438','{26662}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','5e104649223b40cdadeaa338321ca690',''),
('20463','{26712}<>{26713} and length({26714})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','9b20e7d8a4c844069a75adc95dcb6223',''),
('20464','{26715}<>{26716} and length({26717})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','ec99b185eb1d4af2943cd49f4b1e3dcf',''),
('20465','{26718}<>{26719} and length({26720})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','54ca398b57a8450ba004aa15a310f599',''),
('20466','{26721}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','a60e5b95514e4a6ba5bdc1d2bc95818c',''),
('20491','{26771}<>{26772} and length({26773})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','6be0e3bc49134d8c9823736e1c4dcb98',''),
('20492','{26774}<>{26775} and length({26776})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','a6c0fe000ca34b7490c4a56f5c57346b',''),
('20493','{26777}<>{26778} and length({26779})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','660fbce28f334bb79afc6a9ba8596316',''),
('20494','{26780}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','ac97984b2153426c89247bd88797b4a2',''),
('20519','{26830}<>{26831} and length({26832})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','1a920e11feb447deba1aa2d8fbb24f85',''),
('20520','{26833}<>{26834} and length({26835})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','1167a5bf26e24eb89479904841ef890b',''),
('20521','{26836}<>{26837} and length({26838})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','4a1aacf6350844e5858c3eed35b544eb',''),
('20522','{26839}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','f58eb093a57948f1bf674be6a207b0d3',''),
('20547','{26889}<>{26890} and length({26891})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','2a00f0a84a274bf98254d1bbb9f1ad93',''),
('20548','{26892}<>{26893} and length({26894})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','519f97f0275f4e9caf7e320e932ee911',''),
('20549','{26895}<>{26896} and length({26897})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','97933a27c0eb4e0cb67fceb9877641d9',''),
('20550','{26898}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','72662034829d4d008f19cd3231b18bd1',''),
('20575','{26948}<>{26949} and length({26950})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','fe286c10b77a4178b53136d088c09977',''),
('20576','{26951}<>{26952} and length({26953})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','b84f0bcdae4a4ef7887877b7f054ca3c',''),
('20577','{26954}<>{26955} and length({26956})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','8d2847030c154c958ae3cc72841f7b73',''),
('20578','{26957}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','4e4df5360a9b40b5a4f6d1aa706d23d7',''),
('20603','{27007}<>{27008} and length({27009})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','2deae9223199442b895df43cb2b0904c',''),
('20604','{27010}<>{27011} and length({27012})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','ae8533bd4fa84d8f8e8969498d5530ed',''),
('20605','{27013}<>{27014} and length({27015})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','b0b935a8197e4188962b7d859d2b412b',''),
('20606','{27016}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','f9d7f4390619408eb5a20baa5e4ebbfe',''),
('20631','{27066}<>{27067} and length({27068})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','9f571e3e7d7b4025a62cb4d61684a63f',''),
('20632','{27069}<>{27070} and length({27071})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','6c56d13df5a84f8c81e3b11b5979fe2f',''),
('20633','{27072}<>{27073} and length({27074})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','cbc5e573f7ff4d4186782e18abb18323',''),
('20634','{27075}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','41dc7494d2d04e2e8fd9f31d744cdf94',''),
('20659','{27125}<>{27126} and length({27127})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','9c552d88fc734c2d8b9976831396dcc4',''),
('20660','{27128}<>{27129} and length({27130})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','59393bfb9a2b4fe9acf09735ab9b6dd7',''),
('20661','{27131}<>{27132} and length({27133})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','d517281567044119bdc82dccb20c9724',''),
('20662','{27134}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','ce1f7003b6dc4ca6a0e435c06aba6e1a',''),
('20687','{27184}<>{27185} and length({27186})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','84b149555c7a4ba896260eef821e65e4',''),
('20688','{27187}<>{27188} and length({27189})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','5444e9d45fd5482b9913f33a0e46afac',''),
('20689','{27190}<>{27191} and length({27192})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','7297756962334a7e92bec8fba24cc346',''),
('20690','{27193}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','3f856c135f7a4124b606a368ddbaea70',''),
('20715','{27243}<>{27244} and length({27245})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','e0f5e6575df14242a14813cf95f763d2',''),
('20716','{27246}<>{27247} and length({27248})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','09d6eff5d5e24ba9801d29a594913c5e',''),
('20717','{27249}<>{27250} and length({27251})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','2cfe859d44ee4088b3a62f832391091f',''),
('20718','{27252}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','f32f4750dd6f469d84560e0a27dad550',''),
('20743','{27302}<>{27303} and length({27304})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','0bc8753d55d047cd870eb7bd2db7849c',''),
('20744','{27305}<>{27306} and length({27307})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','4a87af156bc44861bcd76514d60183f5',''),
('20745','{27308}<>{27309} and length({27310})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','b5b061ff649547e6b63bdd9dc545c652',''),
('20746','{27311}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','8e0b50b2687a4259ba9b9457c6a2d911',''),
('20771','{27361}<>{27362} and length({27363})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','5924d076b0724fbcaa2090c786b20068',''),
('20772','{27364}<>{27365} and length({27366})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','5df5c72272694a7f8a698ddda7b662cb',''),
('20773','{27367}<>{27368} and length({27369})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','18fce4771aad421e949e78ec9484a888',''),
('20774','{27370}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','454c77360eb44d6aacf067327d1aecbe',''),
('20799','{27420}<>{27421} and length({27422})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','2349e4eac44548349cc9f7806f8726db',''),
('20800','{27423}<>{27424} and length({27425})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','f43a3aa77c8e4e9f81add08ac624be88',''),
('20801','{27426}<>{27427} and length({27428})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','76d4c429deaf491982b7b1049634550a',''),
('20802','{27429}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','cfca5a71a1534e199e9c3b867b8c6c3b',''),
('20827','{27479}<>{27480} and length({27481})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','1f05ddb5fc1c4d18a5d9f5755b22a080',''),
('20828','{27482}<>{27483} and length({27484})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','9bc744f5b70748e68b13933b618f9550',''),
('20829','{27485}<>{27486} and length({27487})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','72cedbd4d23948c3941d5b2011f5cdab',''),
('20830','{27488}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','971f8265db9348ce942f4e0adb49bd1a',''),
('20855','{27538}<>{27539} and length({27540})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','a5f7839a9a0d4272ae0312b8954a9313',''),
('20856','{27541}<>{27542} and length({27543})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','672fcd1d34374373b0992d80d46d885c',''),
('20857','{27544}<>{27545} and length({27546})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','7538c487e4f14cdcb6fc3a6b415ed559',''),
('20858','{27547}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','6975f0abf1504caebd3a13193da1bdcc',''),
('20883','{27597}<>{27598} and length({27599})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','4a440903276347d9827dcfa3653d496c',''),
('20884','{27600}<>{27601} and length({27602})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','7b48c923659d4569b24692da4037b824',''),
('20885','{27603}<>{27604} and length({27605})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','80b76f59fdfd407ea5c3294736113749',''),
('20886','{27606}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','d55a4746f70a4d539a9fadd9a335794f',''),
('20911','{27656}<>{27657} and length({27658})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','a61fd73d9dea4257bfbfc3d705475ae5',''),
('20912','{27659}<>{27660} and length({27661})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','c31be8015ce640629af6cd3ed09dc617',''),
('20913','{27662}<>{27663} and length({27664})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','991217a368944e34abe41bd465921a47',''),
('20914','{27665}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','5b0479439c444be284cac4c699f64b53',''),
('20939','{27715}<>{27716} and length({27717})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','d6de889ff3dc4c07a57bb5396a25a760',''),
('20940','{27718}<>{27719} and length({27720})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','6c509b4e298e4df7b4e9cecc064dc8eb',''),
('20941','{27721}<>{27722} and length({27723})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','aafa92f02db4429b8ea5c43f1e13ad4e',''),
('20942','{27724}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','570f6f393cf24ee9b0731978bca9d7d7',''),
('20967','{27774}<>{27775} and length({27776})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','81f162170b3f4cf0a5376f43ba8c826d',''),
('20968','{27777}<>{27778} and length({27779})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','ba2f0b5e00a94aff9db6b436a64b91bd',''),
('20969','{27780}<>{27781} and length({27782})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','857cc7715ae243879509d5ba827f0533',''),
('20970','{27783}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','f328399a209d4adaa8fed3dc9577539f',''),
('20995','{27833}<>{27834} and length({27835})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','fe1e4e312e5a4ee48fecb03895b51201',''),
('20996','{27836}<>{27837} and length({27838})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','250374059d8a45f78107f1f5b9bda7b1',''),
('20997','{27839}<>{27840} and length({27841})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','2615116273594f659184fdc9f2612c91',''),
('20998','{27842}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','851e15f5b81a43b3be5d3eda921c9430',''),
('21023','{27892}<>{27893} and length({27894})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','bdc6d6b5a4be4bba95f1635d8cf165d7',''),
('21024','{27895}<>{27896} and length({27897})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','9bcc039b8f1e4b3c84414d0d62d6c52d',''),
('21025','{27898}<>{27899} and length({27900})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','21dd8dc14526470493b31ebddf14574c',''),
('21026','{27901}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','bdd1ff379f214b1896c0e7ee5d6e6e16',''),
('21051','{27951}<>{27952} and length({27953})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','8fb6d0748d5a4e589e397f0523944bc5',''),
('21052','{27954}<>{27955} and length({27956})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','c76bf7b6d13b49a4916a00709ee7c9ba',''),
('21053','{27957}<>{27958} and length({27959})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','b5cddf34bbe74bb08663b85c83035f57',''),
('21054','{27960}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','4a08a50891814c0d813c39a4615bffac',''),
('21079','{28010}<>{28011} and length({28012})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','0c58b3a529a541c5813e6d374fb1af38',''),
('21080','{28013}<>{28014} and length({28015})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','3a683df3455e4c3b9693f70d7cc2312c',''),
('21081','{28016}<>{28017} and length({28018})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','752e3b231fb9428baa28a7dffd90b2a5',''),
('21082','{28019}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','3887f8ec0f8a4eadb45b3d3388fdd3bf',''),
('21107','{28069}<>{28070} and length({28071})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','86d3bc7830274e24b19f0b7120f9c957',''),
('21108','{28072}<>{28073} and length({28074})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','8964055d1c7445e68b9ba2eb30faf1fc',''),
('21109','{28075}<>{28076} and length({28077})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','ad61f9029ba449aab240fee852d1e49e',''),
('21110','{28078}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','660db85a472349e7878bcdf41faa4689',''),
('21135','{28128}<>{28129} and length({28130})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','4b2840d437844c54aa8328a2af6ab16a',''),
('21136','{28131}<>{28132} and length({28133})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','356423e8d963491c84c0ff910a324db9',''),
('21137','{28134}<>{28135} and length({28136})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','381ec628763d43e8a7f287d4bab024ee',''),
('21138','{28137}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','35b88fa6b15845e78a3a7211fe2ed0af',''),
('21163','{28187}<>{28188} and length({28189})>0','MikroTik: Firmware has changed','','0','1','Firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','c9b18f3abf444a849606d278d9db0924',''),
('21164','{28190}<>{28191} and length({28192})>0','MikroTik: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: Device has been replaced (new serial number received)','42d7e9c9f03e4b2a8af09b1c54913bba',''),
('21165','{28193}<>{28194} and length({28195})>0','MikroTik: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','4400b69762f948f78365b74569ed54af',''),
('21166','{28196}>{$MEMORY.UTIL.MAX}','MikroTik: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','MikroTik: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','348923e33c3049ea8b27a5d920528300',''),
('21181','length({28223})>0','VeloCloud: There are errors in aggregate script item','','0','2','There are errors in the aggregate script item.',NULL,'0','0','0','','0','','0','','0','','a0623655a2fa4f60962ad560b8bb5a13',''),
('21185','{28231}<>{28232}','VeloCloud: System properties have changed','','0','1','The system properties have changed.',NULL,'0','0','0','','0','','1','','0','','58541dfe798843fa822276e84a32b919',''),
('21197','{33789}>{$ZABBIX.SERVER.UTIL.MAX:"ODBC poller"}','Zabbix server: Utilization of ODBC poller processes is high','','0','3','Indicates potential performance issues with the ODBC poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33789}<{$ZABBIX.SERVER.UTIL.MIN:"ODBC poller"}','0','','0','','0','Zabbix server: Utilization of ODBC poller processes over {$ZABBIX.SERVER.UTIL.MAX:"ODBC poller"}%','f536b921e9444c6eb0ac805ab9302af9',''),
('21199','{33903}>{$ZABBIX.SERVER.UTIL.MAX:"ODBC poller"}','Zabbix server: Utilization of ODBC poller processes is high','','0','3','Indicates potential performance issues with the ODBC poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33903}<{$ZABBIX.SERVER.UTIL.MIN:"ODBC poller"}','0','','0','','0','Zabbix server: Utilization of ODBC poller processes over {$ZABBIX.SERVER.UTIL.MAX:"ODBC poller"}%','eadd70080005430c8b11666d7e93a095',''),
('21200','{28406}>{$ZABBIX.PROXY.UTIL.MAX:"ODBC poller"}','Zabbix proxy: Utilization of ODBC poller processes is high','','0','3','Indicates potential performance issues with the ODBC poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{28406}<{$ZABBIX.PROXY.UTIL.MIN:"ODBC poller"}','0','','0','','0','Zabbix proxy: Utilization of ODBC poller processes over {$ZABBIX.PROXY.UTIL.MAX:"ODBC poller"}%','7f83ff01200c4862aa22057b079da6f8',''),
('21201','{28375}>{$ZABBIX.PROXY.UTIL.MAX:"ODBC poller"}','Zabbix proxy: Utilization of ODBC poller processes is high','','0','3','Indicates potential performance issues with the ODBC poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{28375}<{$ZABBIX.PROXY.UTIL.MIN:"ODBC poller"}','0','','0','','0','Zabbix proxy: Utilization of ODBC poller processes over {$ZABBIX.PROXY.UTIL.MAX:"ODBC poller"}%','3177430235ac4eeaa23b8c39987989cc',''),
('21202','{28259}>{$KUBE.API.HTTP.SERVER.ERROR}','Kubernetes API server: Too many server errors','','0','2','"Kubernetes API server is experiencing high error rate (with 5xx HTTP code).',NULL,'0','0','0','','0','','0','','0','Kubernetes API server: Too many server errors (over {$KUBE.API.HTTP.SERVER.ERROR} for 5m)','0e1ef1630b5d4cb98270564f324f5382',''),
('21205','{28262}>{$KUBE.API.HTTP.CLIENT.ERROR}','Kubernetes API server: Too many client errors','','0','2','"Kubernetes API client is experiencing high error rate (with 5xx HTTP code).',NULL,'0','0','0','','0','','0','','0','Kubernetes API server: Too many client errors (over {$KUBE.API.HTTP.CLIENT.ERROR} for 5m)','4c79888da91448738092c86e5f427a6a',''),
('21206','{28263}>{$KUBE.CONTROLLER.HTTP.CLIENT.ERROR}','Kubernetes Controller manager: Too many HTTP client errors','','0','2','"Kubernetes Controller manager is experiencing high error rate (with 5xx HTTP code).',NULL,'0','0','0','','0','','0','','0','Kubernetes Controller manager: Too many HTTP client errors (over {$KUBE.CONTROLLER.HTTP.CLIENT.ERROR} for 5m)','13c32daebddd454bb5908a9a27c3a76f',''),
('21207','length({28264})>0','Kubernetes nodes: Failed to get nodes','','0','2','',NULL,'0','0','0','','0','','0','','0','','827016cf41254f38aa58ff99e22f9e6f',''),
('21225','{28292}>{$KUBE.SCHEDULER.HTTP.CLIENT.ERROR}','Kubernetes Scheduler: Too many REST Client errors','','0','2','"Kubernetes Scheduler REST Client requests is experiencing high error rate (with 5xx HTTP code).',NULL,'0','0','0','','0','','0','','0','Kubernetes Scheduler: Too many REST Client errors (over {$KUBE.SCHEDULER.HTTP.CLIENT.ERROR} for 5m)','ea92474a61214053b2cd20775817010e',''),
('21226','{28293}>{$KUBE.SCHEDULER.ERROR}','Kubernetes Scheduler: Too many schedule attempts with errors','','0','2','Number of attempts to schedule pods with ''error'' result is too high. ''error'' means an internal scheduler problem.',NULL,'0','0','0','','0','','0','','0','Kubernetes Scheduler: Too many schedule attempts with errors (over {$KUBE.SCHEDULER.ERROR} for 5m)','9116327bc14f4f189ca867b43187f6bd',''),
('21227','{28294}>{$KUBE.SCHEDULER.UNSCHEDULABLE}','Kubernetes Scheduler: Too many unschedulable pods','','0','2','Number of attempts to schedule pods with ''unschedulable'' result is too high. ''unschedulable'' means a pod could not be scheduled.',NULL,'0','0','0','','0','','0','','0','Kubernetes Scheduler: Too many unschedulable pods (over {$KUBE.SCHEDULER.UNSCHEDULABLE} for 5m)','16efba4ba322416fa2b8986273b83904',''),
('21241','{28315}=0','PFSense: DHCP server is not running','','0','3','Please check DHCP server settings https://docs.netgate.com/pfsense/en/latest/services/dhcp/index.html',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','80fc3672290d45d49c250ccc120f3606',''),
('21242','{28316}=0','PFSense: DNS server is not running','','0','3','Please check DNS server settings https://docs.netgate.com/pfsense/en/latest/services/dns/index.html',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','67b862f6aa3a4833af44d513aad517b5',''),
('21243','{28317}=0','PFSense: Web server is not running','','0','3','Please check nginx service status.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','9f7a47055ee64edcbb70b047a35f7774',''),
('21244','{28318}<>1','PFSense: Packet filter is not running','','0','4','Please check PF status.',NULL,'0','0','0','','0','','0','Current running state: {ITEM.LASTVALUE1}','0','','4a7ff4c437054ce88c6c069ffcb6434f',''),
('21245','{28319}>{$SOURCE.TRACKING.TABLE.UTIL.MAX}','PFSense: Source tracking table usage is high','','0','2','Please check the number of sticky connections https://docs.netgate.com/pfsense/en/latest/monitoring/status/firewall-states-sources.html',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','PFSense: Source tracking table usage more than {$SOURCE.TRACKING.TABLE.UTIL.MAX}.','7983ee28646d4327ae0814c88c7b213f',''),
('21246','{28320}>{$STATE.TABLE.UTIL.MAX}','PFSense: State table usage is high','','0','2','Please check the number of connections https://docs.netgate.com/pfsense/en/latest/config/advanced-firewall-nat.html#config-advanced-firewall-maxstates',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','PFSense: State table usage more than {$STATE.TABLE.UTIL.MAX}.','ce0e7dec597e4148abd9b699c787decd',''),
('21250','{28326}=0','PFSense: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d06bdb79a48c438798286a89680eb3e1',''),
('21265','{28389}<10m','Zabbix proxy: {HOST.NAME} has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Zabbix proxy: {HOST.NAME} has been restarted (uptime < 10m)','b505a16c50f64adb8c5528907925f798',''),
('21266','{28390}<>{28391} and length({28392})>0','Zabbix proxy: Version has changed','','0','1','Zabbix proxy version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Zabbix proxy: Version has changed (new version: {ITEM.VALUE})','bf7eef07faf14fc4b2603ae952f001da',''),
('21267','{28418}>{$ZABBIX.PROXY.UTIL.MAX:"preprocessing manager"}','Zabbix proxy: Utilization of preprocessing manager processes is high','','0','3','Indicates potential performance issues with the preprocessing manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{28418}<{$ZABBIX.PROXY.UTIL.MIN:"preprocessing manager"}','0','','0','','0','Zabbix proxy: Utilization of preprocessing manager processes over {$ZABBIX.PROXY.UTIL.MAX:"preprocessing manager"}%','4c681b0775b54fd79e4aba669e219967',''),
('21268','{28419}>{$ZABBIX.PROXY.UTIL.MAX:"preprocessing worker"}','Zabbix proxy: Utilization of preprocessing worker processes is high','','0','3','Indicates potential performance issues with the preprocessing worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{28419}<{$ZABBIX.PROXY.UTIL.MIN:"preprocessing worker"}','0','','0','','0','Zabbix proxy: Utilization of preprocessing worker processes over {$ZABBIX.PROXY.UTIL.MAX:"preprocessing worker"}%','f1c97c56e2d04cabaaa4c9b41e2bbad3',''),
('21269','{28420}<10m','Zabbix proxy: {HOST.NAME} has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Zabbix proxy: {HOST.NAME} has been restarted (uptime < 10m)','8940efd3c68b4ded80ea1e89d55dfa7c',''),
('21543','{28714}=0','Alcatel TiMOS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','72f8bcb4dfde4d338c31c83b72a36129',''),
('21544','{28715}>{$ICMP_LOSS_WARN} and {28715}<100','Alcatel TiMOS: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','0c0a32b98df84c07acbe51caabc8c012',''),
('21545','{28716}>{$ICMP_RESPONSE_TIME_WARN}','Alcatel TiMOS: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','06fd317938784236b3e17b2b4080925d',''),
('21546','{28717}<>{28718} and length({28719})>0','Alcatel TiMOS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Alcatel TiMOS: System name has changed (new name: {ITEM.VALUE})','5f11cacfd4a94cf696897b3f3fa80601',''),
('21547','({32144}>0 and {32144}<10m) or ({32144}=0 and {32145}<10m)','Alcatel TiMOS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Alcatel TiMOS: {HOST.NAME} has been restarted (uptime < 10m)','3b6324116e5940b5aaea72adca4dbbf6',''),
('21548','{28721}=0','Alcatel TiMOS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','60187191b268499784a70ef1dfe058ae',''),
('21554','{28738}=0','Arista: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','736dc5694fc741e6bcb96e2ba27a0898',''),
('21555','{28739}>{$ICMP_LOSS_WARN} and {28739}<100','Arista: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','dfa6f280b6304bfdb0063be94f7a4c5e',''),
('21556','{28740}>{$ICMP_RESPONSE_TIME_WARN}','Arista: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','18aeec70f72d43ceb4994501fb36d434',''),
('21557','{28741}>{$CPU.UTIL.CRIT}','Arista: High CPU utilization','','0','2','CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Arista: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','6737f0672c244e048509358d220874a6',''),
('21558','{28742}<>{28743} and length({28744})>0','Arista: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Arista: System name has changed (new name: {ITEM.VALUE})','362d455c9d9944cea7c37d58bcabc0a0',''),
('21559','({32146}>0 and {32146}<10m) or ({32146}=0 and {32147}<10m)','Arista: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Arista: {HOST.NAME} has been restarted (uptime < 10m)','e3907a8b6aba4512a24a677ed31e4362',''),
('21560','{28746}=0','Arista: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','53501c72392a4bbc8fa0f5ed086d2591',''),
('21569','{28772}=0','Brocade FC: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','0c73f37e7ffc4acf83a7edeb84398aba',''),
('21570','{28773}>{$ICMP_LOSS_WARN} and {28773}<100','Brocade FC: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','eea2256c85764c12b1da83dd8d1a9fe3',''),
('21571','{28774}>{$ICMP_RESPONSE_TIME_WARN}','Brocade FC: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','17df26093a5f42fdb19715371c85f733',''),
('21572','{28775}<>{28776} and length({28777})>0','Brocade FC: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Brocade FC: System name has changed (new name: {ITEM.VALUE})','0e624c73fdca490e809ffe9235cda610',''),
('21573','({32148}>0 and {32148}<10m) or ({32148}=0 and {32149}<10m)','Brocade FC: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Brocade FC: {HOST.NAME} has been restarted (uptime < 10m)','42bb10d788484b92ac7290e171ee28a2',''),
('21574','{28779}=0','Brocade FC: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','1c67a764531b48f1a931a9a928a8708d',''),
('21579','{28795}=0','Brocade Nonstackable: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','3e93707bfbed4541a90548f64b2dfc18',''),
('21580','{28796}>{$ICMP_LOSS_WARN} and {28796}<100','Brocade Nonstackable: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','3f3500c666bb47208115b6ca43fc8458',''),
('21581','{28797}>{$ICMP_RESPONSE_TIME_WARN}','Brocade Nonstackable: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','e1bcb2ad662f4e4fb0ff67f0f1fc39e5',''),
('21582','{28798}>{$CPU.UTIL.CRIT}','Brocade Nonstackable: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Brocade Nonstackable: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','bf59d38703f44bcb9497dcbda684b071',''),
('21583','{28799}<>{28800} and length({28801})>0','Brocade Nonstackable: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Brocade Nonstackable: System name has changed (new name: {ITEM.VALUE})','ee0c67c575cb4b01bc3733d719baac4f',''),
('21584','({32150}>0 and {32150}<10m) or ({32150}=0 and {32151}<10m)','Brocade Nonstackable: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Brocade Nonstackable: {HOST.NAME} has been restarted (uptime < 10m)','99208318a05445518bebae305dd53d34',''),
('21585','{28803}>{$MEMORY.UTIL.MAX}','Brocade Nonstackable: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Brocade Nonstackable: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','07bba62d70fa4e7b81f82fc44036ce6e',''),
('21586','{28804}=0','Brocade Nonstackable: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','fb3168f6539c4a55b5aab3efbcad117d',''),
('21587','{28805}=0','Brocade Stackable: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','06ed32e60b9d4fb387116b5bb9c1700a',''),
('21588','{28806}>{$ICMP_LOSS_WARN} and {28806}<100','Brocade Stackable: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','305f5a75aed34094a1721653ba6cafda',''),
('21589','{28807}>{$ICMP_RESPONSE_TIME_WARN}','Brocade Stackable: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','6e7e8f250fbb47778405daeea7a2b852',''),
('21590','{28808}>{$CPU.UTIL.CRIT}','Brocade Stackable: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Brocade Stackable: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','c390ed19b59a45b29f80cb95ee6e635a',''),
('21591','{28809}<>{28810} and length({28811})>0','Brocade Stackable: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Brocade Stackable: System name has changed (new name: {ITEM.VALUE})','1e455a8b19994e9a9f9147d4c3abfa59',''),
('21592','({32152}>0 and {32152}<10m) or ({32152}=0 and {32153}<10m)','Brocade Stackable: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Brocade Stackable: {HOST.NAME} has been restarted (uptime < 10m)','0fd4a268d6d34a2d925a97babe365b65',''),
('21593','{28813}>{$MEMORY.UTIL.MAX}','Brocade Stackable: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Brocade Stackable: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','18623226ce15406488bc99f075cf2590',''),
('21594','{28814}=0','Brocade Stackable: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','a4bb03ba3e4645fdb7ecab56ddde776f',''),
('21603','{28845}=0','Cisco IOS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','fd317d3e8d3d45bf97322b8578f30c04',''),
('21604','{28846}>{$ICMP_LOSS_WARN} and {28846}<100','Cisco IOS: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','3576c96601ef40abbeedbde11768141a',''),
('21605','{28847}>{$ICMP_RESPONSE_TIME_WARN}','Cisco IOS: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','2941d30058b14d52bd9a723889c8be26',''),
('21606','{28848}>{$CPU.UTIL.CRIT}','Cisco IOS: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Cisco IOS: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','74773fc279864e7daf89cffe9cb2067c',''),
('21607','{28849}<>{28850} and length({28851})>0','Cisco IOS: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco IOS: Device has been replaced (new serial number received)','d53c0d22a67544cf8a2fcd2c8de4d4eb',''),
('21608','{28852}<>{28853} and length({28854})>0','Cisco IOS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco IOS: System name has changed (new name: {ITEM.VALUE})','33b42b1aa448408fa3fb5aadf7375cf8',''),
('21609','{28855}<>{28856} and length({28857})>0','Cisco IOS: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','abe57415ff574b878a2ce2a318be86ee',''),
('21610','({32164}>0 and {32164}<10m) or ({32164}=0 and {32165}<10m)','Cisco IOS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco IOS: {HOST.NAME} has been restarted (uptime < 10m)','f278b8b4eb784107a6d8d3e8437e8a66',''),
('21611','{28859}=0','Cisco IOS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','86d8603903504287b07a25530c8eda2b',''),
('21612','{28860}=0','Cisco IOS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','77e52d690bc043e389ad8d705dbb86b9',''),
('21613','{28861}>{$ICMP_LOSS_WARN} and {28861}<100','Cisco IOS: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','62b3c0a2654f4372a1bad40a0fd2898d',''),
('21614','{28862}>{$ICMP_RESPONSE_TIME_WARN}','Cisco IOS: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','1ba34b5e344147d5b27431906037bc04',''),
('21615','{28863}<>{28864} and length({28865})>0','Cisco IOS: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco IOS: Device has been replaced (new serial number received)','7d1460eaf7ad46fd8a1b5df3c20051ba',''),
('21616','{28866}<>{28867} and length({28868})>0','Cisco IOS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco IOS: System name has changed (new name: {ITEM.VALUE})','2105744d4efd4a239c5b6ab615746a40',''),
('21617','{28869}<>{28870} and length({28871})>0','Cisco IOS: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','2d97173405594074bfe2cc6f3d0cae70',''),
('21618','({32166}>0 and {32166}<10m) or ({32166}=0 and {32167}<10m)','Cisco IOS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco IOS: {HOST.NAME} has been restarted (uptime < 10m)','b98092ddf87247ff91710e2f310dbfb9',''),
('21619','{28873}=0','Cisco IOS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','df7c9ed5d3164e73a792f82ecad6ba13',''),
('21620','{28874}=0','Cisco IOS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','f6fae61d08644d5fa3929f526aee34e4',''),
('21621','{28875}>{$ICMP_LOSS_WARN} and {28875}<100','Cisco IOS: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','5c7eae9701be4661a34bbcdb99c094fe',''),
('21622','{28876}>{$ICMP_RESPONSE_TIME_WARN}','Cisco IOS: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','9aebe4a1cfa34c5d92178abc8a6ce06e',''),
('21623','{28877}<>{28878} and length({28879})>0','Cisco IOS: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco IOS: Device has been replaced (new serial number received)','78723249679b4a288861f4ad8621fd77',''),
('21624','{28880}<>{28881} and length({28882})>0','Cisco IOS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco IOS: System name has changed (new name: {ITEM.VALUE})','3e09d5d308e449a4974393650b33e64d',''),
('21625','{28883}<>{28884} and length({28885})>0','Cisco IOS: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','df85813bb6af4accab8d5191cd452329',''),
('21626','({32168}>0 and {32168}<10m) or ({32168}=0 and {32169}<10m)','Cisco IOS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco IOS: {HOST.NAME} has been restarted (uptime < 10m)','806f54999d064eb68a3f46a0d84ee4df',''),
('21627','{28887}=0','Cisco IOS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','778749b260bb45c3a926d6bb49c07257',''),
('21666','{28981}=0','Dell Force S-Series: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','f186488b337f4b1b8971992e8118d9cc',''),
('21667','{28982}>{$ICMP_LOSS_WARN} and {28982}<100','Dell Force S-Series: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','46798adec54c47a38cb599773767a2a7',''),
('21668','{28983}>{$ICMP_RESPONSE_TIME_WARN}','Dell Force S-Series: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','04828676081147b4bfad0ad03385986e',''),
('21669','{28984}<>{28985} and length({28986})>0','Dell Force S-Series: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Dell Force S-Series: System name has changed (new name: {ITEM.VALUE})','2dc35c5813b042fd96f2ebc53f565799',''),
('21670','({32170}>0 and {32170}<10m) or ({32170}=0 and {32171}<10m)','Dell Force S-Series: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Dell Force S-Series: {HOST.NAME} has been restarted (uptime < 10m)','4246a064d33f428c8441491402ae8090',''),
('21671','{28988}=0','Dell Force S-Series: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','da99689aa1394d17af5008e5678915bc',''),
('21677','{29005}=0','D-Link DES 7200: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','a568e0a3c0074e6dbad92890067976f3',''),
('21678','{29006}>{$ICMP_LOSS_WARN} and {29006}<100','D-Link DES 7200: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','12dea4dbaa3c4ef1a53456090ae3eb0e',''),
('21679','{29007}>{$ICMP_RESPONSE_TIME_WARN}','D-Link DES 7200: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','88f2c517c1ba4f7881491a4b2b7f7ad0',''),
('21680','{29008}<>{29009} and length({29010})>0','D-Link DES 7200: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','D-Link DES 7200: System name has changed (new name: {ITEM.VALUE})','0c7a629e028e489c89647bf3ca51850e',''),
('21681','({32172}>0 and {32172}<10m) or ({32172}=0 and {32173}<10m)','D-Link DES 7200: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','D-Link DES 7200: {HOST.NAME} has been restarted (uptime < 10m)','6b200163bfcd4899a82bcf98aa026aa2',''),
('21682','{29012}=0','D-Link DES 7200: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','dc5b0dda2d684665a5444e39db5e2257',''),
('21687','{29028}=0','D-Link DES_DGS Switch: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','5d134da7ad044ab591e1b96e1dca1641',''),
('21688','{29029}>{$ICMP_LOSS_WARN} and {29029}<100','D-Link DES_DGS Switch: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','9c48d97b5d4a4668ad382e1d0d9c8e87',''),
('21689','{29030}>{$ICMP_RESPONSE_TIME_WARN}','D-Link DES_DGS Switch: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','3959884457a7420a9a9007c550d9b886',''),
('21690','{29031}<>{29032} and length({29033})>0','D-Link DES_DGS Switch: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','D-Link DES_DGS Switch: System name has changed (new name: {ITEM.VALUE})','91e1a9f579c64954a89b6efbf6b523dd',''),
('21691','({32174}>0 and {32174}<10m) or ({32174}=0 and {32175}<10m)','D-Link DES_DGS Switch: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','D-Link DES_DGS Switch: {HOST.NAME} has been restarted (uptime < 10m)','7a51877b860a479da9bc9f02ee36e01f',''),
('21692','{29035}=0','D-Link DES_DGS Switch: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','2b56c7cfef454441863d2f7cc01a330f',''),
('21698','{29052}=0','Extreme EXOS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','445766fc99c1480eac4d3d403c3ede2b',''),
('21699','{29053}>{$ICMP_LOSS_WARN} and {29053}<100','Extreme EXOS: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','fb0abe322fd644b4bb3c1255d564bb47',''),
('21700','{29054}>{$ICMP_RESPONSE_TIME_WARN}','Extreme EXOS: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','d29defd9360c489a892821989eeda10c',''),
('21701','{29055}<>{29056} and length({29057})>0','Extreme EXOS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Extreme EXOS: System name has changed (new name: {ITEM.VALUE})','2923c342e8474e3ea3d7411c104a6988',''),
('21702','({32176}>0 and {32176}<10m) or ({32176}=0 and {32177}<10m)','Extreme EXOS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Extreme EXOS: {HOST.NAME} has been restarted (uptime < 10m)','bb967f81aaad4a00ae7916ea80574ae0',''),
('21703','{29059}=0','Extreme EXOS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','ecc42656a3d845ee8ad42d0fe45319c2',''),
('21709','{29076}=0','Network Generic Device: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','d08cae0e7fa54dfea41449f0adabe05d',''),
('21710','{29077}>{$ICMP_LOSS_WARN} and {29077}<100','Network Generic Device: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','d70eb18878114ae69e5f5f95f4b898cc',''),
('21711','{29078}>{$ICMP_RESPONSE_TIME_WARN}','Network Generic Device: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','09bcfc7a9e3d45d99d37b56a404df610',''),
('21712','{29079}<>{29080} and length({29081})>0','Network Generic Device: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Network Generic Device: System name has changed (new name: {ITEM.VALUE})','5f11afa80f534add85dd03e06466fbc9',''),
('21713','({32178}>0 and {32178}<10m) or ({32178}=0 and {32179}<10m)','Network Generic Device: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Network Generic Device: {HOST.NAME} has been restarted (uptime < 10m)','536fafc0bb664fcb8b4c8acc18fe5c29',''),
('21714','{29083}=0','Network Generic Device: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d534ea9f1ad34633bdd361f20733b749',''),
('21720','{29100}=0','HP Comware HH3C: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','1bd6a4748e29498e99ccd3b23d83cdf7',''),
('21721','{29101}>{$ICMP_LOSS_WARN} and {29101}<100','HP Comware HH3C: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','d41edaea369d40d2944af72a3ee76850',''),
('21722','{29102}>{$ICMP_RESPONSE_TIME_WARN}','HP Comware HH3C: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','2698115b6f014e8cbdb11c2d5eeb8f08',''),
('21723','{29103}<>{29104} and length({29105})>0','HP Comware HH3C: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HP Comware HH3C: System name has changed (new name: {ITEM.VALUE})','cf1d0aa58a194904902899dbba814514',''),
('21724','({32180}>0 and {32180}<10m) or ({32180}=0 and {32181}<10m)','HP Comware HH3C: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','HP Comware HH3C: {HOST.NAME} has been restarted (uptime < 10m)','c1372deba2b148f4ac8be6493f0b9868',''),
('21725','{29107}=0','HP Comware HH3C: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','bc6e9c399c3d4d43aaeb5a1b03deb7d4',''),
('21731','{29124}=0','HP Enterprise Switch: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','8fb33a256deb49a096b287493285e300',''),
('21732','{29125}>{$ICMP_LOSS_WARN} and {29125}<100','HP Enterprise Switch: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','589e13a6ab084dd4b7d1456f7707f44d',''),
('21733','{29126}>{$ICMP_RESPONSE_TIME_WARN}','HP Enterprise Switch: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','75bdd8a0cd664815aa3e4fa54d4f0b97',''),
('21734','{29127}<>{29128} and length({29129})>0','HP Enterprise Switch: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HP Enterprise Switch: System name has changed (new name: {ITEM.VALUE})','63f6f85bfed94821a8339c46544dde0e',''),
('21735','({32182}>0 and {32182}<10m) or ({32182}=0 and {32183}<10m)','HP Enterprise Switch: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','HP Enterprise Switch: {HOST.NAME} has been restarted (uptime < 10m)','1395e02bc63e48daa779b8b685e91868',''),
('21736','{29131}=0','HP Enterprise Switch: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d64df6c48ce44bbcafcdd60a3102b41c',''),
('21742','{29148}=0','Huawei VRP: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','49df55106af2439eb79e66caa2717ec9',''),
('21743','{29149}>{$ICMP_LOSS_WARN} and {29149}<100','Huawei VRP: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','b7ca2b5273be4f50b5c20b422a534868',''),
('21744','{29150}>{$ICMP_RESPONSE_TIME_WARN}','Huawei VRP: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','c322fda29bab4f99a0ea204814390551',''),
('21745','{29151}<>{29152} and length({29153})>0','Huawei VRP: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Huawei VRP: System name has changed (new name: {ITEM.VALUE})','740f78d69b20405da79525365fdc29fe',''),
('21746','({32184}>0 and {32184}<10m) or ({32184}=0 and {32185}<10m)','Huawei VRP: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Huawei VRP: {HOST.NAME} has been restarted (uptime < 10m)','c8c41677f4ba463b90cea501e9112483',''),
('21747','{29155}=0','Huawei VRP: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','cefe56d564434018b6a31c196cc7eb55',''),
('21753','{29172}=0','Intel Qlogic: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','a3a6c95c0a32405d81b1bc7690f1bd1f',''),
('21754','{29173}>{$ICMP_LOSS_WARN} and {29173}<100','Intel Qlogic: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','9c78f78339724840b7ab6db4c62f5aa0',''),
('21755','{29174}>{$ICMP_RESPONSE_TIME_WARN}','Intel Qlogic: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','3c5e0b2660764386ac162ed5d2778a56',''),
('21756','{29175}<>{29176} and length({29177})>0','Intel Qlogic: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Intel Qlogic: System name has changed (new name: {ITEM.VALUE})','cfcabcb7d9ca4fd59ed79775bcf059bb',''),
('21757','({32186}>0 and {32186}<10m) or ({32186}=0 and {32187}<10m)','Intel Qlogic: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Intel Qlogic: {HOST.NAME} has been restarted (uptime < 10m)','20166f9c8d5448a494b6b578471df8cc',''),
('21758','{29179}=0','Intel Qlogic: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','ccbd4c4da58f4b72a82371c2f3eaf4e1',''),
('21763','{29195}=0','Juniper: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','d90e80fd900246dcab90447ee2a6a7a1',''),
('21764','{29196}>{$ICMP_LOSS_WARN} and {29196}<100','Juniper: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','d3911ede372e4eb3b89b30e8e340a716',''),
('21765','{29197}>{$ICMP_RESPONSE_TIME_WARN}','Juniper: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','751d9855903f4f00b674b511fe992121',''),
('21766','{29198}<>{29199} and length({29200})>0','Juniper: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Juniper: System name has changed (new name: {ITEM.VALUE})','97157acd882944e29d6fb9fa1a2d9506',''),
('21767','({32188}>0 and {32188}<10m) or ({32188}=0 and {32189}<10m)','Juniper: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Juniper: {HOST.NAME} has been restarted (uptime < 10m)','23e25e580543411ab8ffc2a4c1ca3c54',''),
('21768','{29202}=0','Juniper: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','417527b3749c4a1c891d761c0978fb2e',''),
('21774','{29219}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','feca40f53ed54c84afbb83d2650bbab6',''),
('21775','{29220}>{$ICMP_LOSS_WARN} and {29220}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','bca3c4bf4f89480e9c6ccfaaed0039bf',''),
('21776','{29221}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','b78ca1d148624deb95177f56eb738338',''),
('21777','{29222}<>{29223} and length({29224})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','203415c1da0d4e36b1e52904c8f77ad7',''),
('21778','({32192}>0 and {32192}<10m) or ({32192}=0 and {32193}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','7cb3423e736d435b87a21687c09debf0',''),
('21779','{29226}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','c48e5ab4112d46898f219f4e9d2e4bae',''),
('21784','{29242}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','5021ba3d848e4c0d80c9644ab70b313b',''),
('21785','{29243}>{$ICMP_LOSS_WARN} and {29243}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','b4c65c535f9841d98da1d32a9aaed7b8',''),
('21786','{29244}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','493e740c3b3a48c3a308492d67ea11f8',''),
('21787','{29245}<>{29246} and length({29247})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','cada2ef5e9b14392885a05f9d50186d8',''),
('21788','({32194}>0 and {32194}<10m) or ({32194}=0 and {32195}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','354a68e77ee043a684ab8be18628ffca',''),
('21789','{29249}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','b19e8ce655fb48e389a384a78826d5d6',''),
('21794','{29265}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','fe75c4f4867942638e3d39face2aea7f',''),
('21795','{29266}>{$ICMP_LOSS_WARN} and {29266}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','ebb9113e215a4ab999b5faf043c3cdd3',''),
('21796','{29267}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','ac9ee5f5347945eaa12f8551ca54ec9b',''),
('21797','{29268}<>{29269} and length({29270})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','796b3caf5996404c93c8266fe7c5aa89',''),
('21798','({32196}>0 and {32196}<10m) or ({32196}=0 and {32197}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','99da791be26943ec806a2c690f74a66d',''),
('21799','{29272}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','a6a88593c32342deb0b72e998872a3c9',''),
('21804','{29288}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','81ff4b462e134758bf758ea598a89ac5',''),
('21805','{29289}>{$ICMP_LOSS_WARN} and {29289}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','5cf5ce1e93f54801a94370f4db68422a',''),
('21806','{29290}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','f9e60c1f73a24df5a9d84ebb81b28861',''),
('21807','{29291}<>{29292} and length({29293})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','5a2e293b0f664c93ac675f925f0ee3e0',''),
('21808','({32198}>0 and {32198}<10m) or ({32198}=0 and {32199}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','4748e443639d47b2a969070386524eee',''),
('21809','{29295}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','f8bfaedd5b0f45ae9e91831865b2c1fa',''),
('21814','{29311}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','ace4ead8482a47fea59f346d0cc41c62',''),
('21815','{29312}>{$ICMP_LOSS_WARN} and {29312}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','e474571997454a96a7e86294c876c0a7',''),
('21816','{29313}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','d4e0d30eadce4dd5a37afd48a10ed379',''),
('21817','{29314}<>{29315} and length({29316})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','1060d8c4dda547d9902dc94ac68f1b33',''),
('21818','({32200}>0 and {32200}<10m) or ({32200}=0 and {32201}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','916fbb00982f4fb38b1942cf44daf5f2',''),
('21819','{29318}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','c98fffdacb89455aa6f4f62060d360de',''),
('21824','{29334}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','f9fd5f6cd1a24a22ae48b0628193e0c4',''),
('21825','{29335}>{$ICMP_LOSS_WARN} and {29335}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','c72587594cfb49a6a8b39575e39ea8eb',''),
('21826','{29336}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','7d3593f5ee8f4350867de676743c4f60',''),
('21827','{29337}<>{29338} and length({29339})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','10caf9fc68e14308a0dbe730e7e4199e',''),
('21828','({32202}>0 and {32202}<10m) or ({32202}=0 and {32203}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','8138034748544325bad6bdc90484ad21',''),
('21829','{29341}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d4932539ba7245ff8975cc8c224f8d36',''),
('21834','{29357}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','65c639dc46a345da90e22ca0dc491d8c',''),
('21835','{29358}>{$ICMP_LOSS_WARN} and {29358}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','65eb4b94fead4b57acda0b7ac001c41c',''),
('21836','{29359}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','410faf17c1ca41408cb773270dc614b3',''),
('21837','{29360}<>{29361} and length({29362})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','ed7279478045454b809f46211c5c71b9',''),
('21838','({32204}>0 and {32204}<10m) or ({32204}=0 and {32205}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','ecf84d7e28504c23a40b013683d1cfee',''),
('21839','{29364}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','56f238340c7e40b39eb8cc04a67cf465',''),
('21844','{29380}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','151029088e374c23bb89abe498da70ef',''),
('21845','{29381}>{$ICMP_LOSS_WARN} and {29381}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','f719d0a102d84edb8c2672502ee28b25',''),
('21846','{29382}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','acba03a0cc9a40fb89258e1ece7dce30',''),
('21847','{29383}<>{29384} and length({29385})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','f2d7211cd2ca476facec96075e06298c',''),
('21848','({32206}>0 and {32206}<10m) or ({32206}=0 and {32207}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','75e9434ddcb34c5489190d8b6de07e87',''),
('21849','{29387}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','b14b41ca31c342be803852075ff5c9f9',''),
('21854','{29403}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','00453dcba3e74c4cb1bfce45c0d29590',''),
('21855','{29404}>{$ICMP_LOSS_WARN} and {29404}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','ef9c639da1fb4c7d9e9082b76468353e',''),
('21856','{29405}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','8a7a50a814854217bae736f9766a9f42',''),
('21857','{29406}<>{29407} and length({29408})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','3d3902234c994181819a311b9f1947dd',''),
('21858','({32208}>0 and {32208}<10m) or ({32208}=0 and {32209}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','7b5ce136e1524c2c85febecb055e50f8',''),
('21859','{29410}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','2fdfcfe056e848f2b0a628d87ad4aa6c',''),
('21864','{29426}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','2510c2fd36cf4379b15e3e18abffea95',''),
('21865','{29427}>{$ICMP_LOSS_WARN} and {29427}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','48a93170038b41af9fd8b6f25500ee37',''),
('21866','{29428}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','1e70b999e9854c4093a75a960f8282a2',''),
('21867','{29429}<>{29430} and length({29431})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','9e3ce4eb299547199e67c131556d5bc5',''),
('21868','({32210}>0 and {32210}<10m) or ({32210}=0 and {32211}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','be74bf6810694df98cd43a669e247aab',''),
('21869','{29433}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','a2d66f40be294b8b81a96e11afcfe7ec',''),
('21874','{29449}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','f37a32635c674102aaf1b7ceafa8532a',''),
('21875','{29450}>{$ICMP_LOSS_WARN} and {29450}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','1889f2943a044c49830914fd18846172',''),
('21876','{29451}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','805b3e4698dc4c55a4cc40712e14e494',''),
('21877','{29452}<>{29453} and length({29454})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','9ffbe2020d8b46f1ac730c038e9d1f51',''),
('21878','({32212}>0 and {32212}<10m) or ({32212}=0 and {32213}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','a885ccc0d0e546fe8a970ff4876f9471',''),
('21879','{29456}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','6c2ff9e7f39a46918bf5d1843c7bf615',''),
('21884','{29472}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','d17f5a29c6104de78dd9b66ae8144e9b',''),
('21885','{29473}>{$ICMP_LOSS_WARN} and {29473}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','f3ad9f5ef4734e6da08c699d937a1521',''),
('21886','{29474}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','831afefc75dc472ab3d010757abab4e2',''),
('21887','{29475}<>{29476} and length({29477})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','ed353db14a0742a7a865e9805025e9a9',''),
('21888','({32214}>0 and {32214}<10m) or ({32214}=0 and {32215}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','285c2be6116d4e5fae7d0cbad5ccecb2',''),
('21889','{29479}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','7a821734dc78455fa363bf7a8c2f2dc2',''),
('21894','{29495}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','93236f96ce364b1ab95c603503c6984f',''),
('21895','{29496}>{$ICMP_LOSS_WARN} and {29496}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','e7c3d84b4e3f4faabd28f36984116925',''),
('21896','{29497}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','4219929d04dd4367bf82c0c97f85eae7',''),
('21897','{29498}<>{29499} and length({29500})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','3bbc3dcf8127414abb426c830e8fddee',''),
('21898','({32216}>0 and {32216}<10m) or ({32216}=0 and {32217}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','f445d5e35c2b4296a670165e332be78c',''),
('21899','{29502}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','e38ee3ff9c5a438fa7785db98162b84a',''),
('21904','{29518}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','04d896fcaf2c4573bb077432604ca2ad',''),
('21905','{29519}>{$ICMP_LOSS_WARN} and {29519}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','c6468c0bef2c4ad2958d69df8364722a',''),
('21906','{29520}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','2b339fa462ce498fbf5d7557e8548930',''),
('21907','{29521}<>{29522} and length({29523})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','3517d04dc5c34d07aad7ec73381deaaf',''),
('21908','({32218}>0 and {32218}<10m) or ({32218}=0 and {32219}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','40fac3f864c442f9bcbcbd5757070c38',''),
('21909','{29525}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','bb5432b89f7248758d05d4c44cdf0d0a',''),
('21914','{29541}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','c63272b308134676a35c7b8311d71589',''),
('21915','{29542}>{$ICMP_LOSS_WARN} and {29542}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','09d55f6987784bffb6024266e0895878',''),
('21916','{29543}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','235acd3457814902b4bf316065d05e00',''),
('21917','{29544}<>{29545} and length({29546})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','5431acc090c34d879e911cd90a52eb48',''),
('21918','({32220}>0 and {32220}<10m) or ({32220}=0 and {32221}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','7bcd342f9c4f467a98ab38a5ea3e174b',''),
('21919','{29548}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','2f271102d58b4068b87eab5ff70b7798',''),
('21924','{29564}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','16ef2e7fa1a949298407a0a0b4d77746',''),
('21925','{29565}>{$ICMP_LOSS_WARN} and {29565}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','1dbb087e217944aebb6cd2ed14685a46',''),
('21926','{29566}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','2dd9b73423b946f89dc7a421e12fd58e',''),
('21927','{29567}<>{29568} and length({29569})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','40ae2f08e95b4affab12454007f4bdc6',''),
('21928','({32222}>0 and {32222}<10m) or ({32222}=0 and {32223}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','d81cc3699a454ae3bd9bf813fff8e286',''),
('21929','{29571}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d720c3c0a669406cad47bf135de9be8c',''),
('21934','{29587}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','eccaf3e02f9944638588b82322322c32',''),
('21935','{29588}>{$ICMP_LOSS_WARN} and {29588}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','71286dd187734ee18b53fdf73602ef7d',''),
('21936','{29589}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','18e8caa0b7a44c64aaec1d5eecf76297',''),
('21937','{29590}<>{29591} and length({29592})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','681af1da9ba7432aa407019b1ff5192f',''),
('21938','({32224}>0 and {32224}<10m) or ({32224}=0 and {32225}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','6cbc680faf50402a8aa5eb6b2b848f7b',''),
('21939','{29594}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','147de2ef3a3447cf9401f4197e911b17',''),
('21944','{29610}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','6883be571ae343a791670f2f0c36cd02',''),
('21945','{29611}>{$ICMP_LOSS_WARN} and {29611}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','ea3e5695d49f4868bd6a83e67689e5d6',''),
('21946','{29612}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','4439b1b6d31d4824ba1ed448d9bda1b4',''),
('21947','{29613}<>{29614} and length({29615})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','ab81c691a90a409fa0d24ddac4ee455f',''),
('21948','({32226}>0 and {32226}<10m) or ({32226}=0 and {32227}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','1d5170eb0ba14c4e8799d712ee84d004',''),
('21949','{29617}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','94b83963c4474cd5a8d21a8cdae584f4',''),
('21954','{29633}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','31542fecf2794dcb8b96293087b71526',''),
('21955','{29634}>{$ICMP_LOSS_WARN} and {29634}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','ded01e910a0046fa94a89c7011cc9514',''),
('21956','{29635}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','5c9b3116dc4140bdb7903a094fbf098f',''),
('21957','{29636}<>{29637} and length({29638})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','1e2f2debb1cc4f13b133cbe6600c99cc',''),
('21958','({32228}>0 and {32228}<10m) or ({32228}=0 and {32229}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','a888ad0e55f14ba0803bf6923dc7d227',''),
('21959','{29640}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','3efee76288274e42921647d5a1d82ab1',''),
('21964','{29656}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','16bfb1a39fe54fa0b512ed93c8c3b00a',''),
('21965','{29657}>{$ICMP_LOSS_WARN} and {29657}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','d166ae7475f5416499b46a00cf5de374',''),
('21966','{29658}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','a59d0752d5724f01a783ef8b4131b9d4',''),
('21967','{29659}<>{29660} and length({29661})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','01cb61daac1f42d3ab0a5fafd2b113a4',''),
('21968','({32230}>0 and {32230}<10m) or ({32230}=0 and {32231}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','a1d58fc2668b465a81a86536c1f646ad',''),
('21969','{29663}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','a564c084ec414271b212db6c9b301db7',''),
('21974','{29679}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','db42c8af11744c5ab3f47f72ebc4a510',''),
('21975','{29680}>{$ICMP_LOSS_WARN} and {29680}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','844a3542770748cf9a99070e6f55fba6',''),
('21976','{29681}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','4b4911507b374dfc9c1b105c4c09e3b8',''),
('21977','{29682}<>{29683} and length({29684})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','dc073a13e66f4d528af68db048184c2f',''),
('21978','({32232}>0 and {32232}<10m) or ({32232}=0 and {32233}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','1cfae25fa7b041b98b5b97a5bca0796a',''),
('21979','{29686}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','cb430613680b4bd087d79a4f1004f453',''),
('21984','{29702}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','f4acabb314ea4a38935ebb722bf47ed9',''),
('21985','{29703}>{$ICMP_LOSS_WARN} and {29703}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','629b35a8b5414240953062d4b4caad60',''),
('21986','{29704}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','28ce838e43004acebc74c42e782b65cb',''),
('21987','{29705}<>{29706} and length({29707})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','f01bb34d5f30454bb72e6b00e187c066',''),
('21988','({32234}>0 and {32234}<10m) or ({32234}=0 and {32235}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','bd172615c09147ed8deb102f88eb8900',''),
('21989','{29709}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','1c20500d7efe42e59d3562c980201ef1',''),
('21994','{29725}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','d914dc20fb664be7832aae19f07df37f',''),
('21995','{29726}>{$ICMP_LOSS_WARN} and {29726}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','70d6789335b74cdd87a1a23bf4a3f875',''),
('21996','{29727}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','49f77a9948164eb7aeffc3efe3f60ce1',''),
('21997','{29728}<>{29729} and length({29730})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','63f90de57f5f4b5b92d0db0b54d0b1d2',''),
('21998','({32236}>0 and {32236}<10m) or ({32236}=0 and {32237}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','b31c237e2046464c95b1ab70dc08e118',''),
('21999','{29732}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','1b222c2531f140399fe94a54556c6422',''),
('22004','{29748}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','b74334acbba2407d8baff550f0db6d64',''),
('22005','{29749}>{$ICMP_LOSS_WARN} and {29749}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','160e58bf2d05433882e3e0c8f187c42e',''),
('22006','{29750}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','ee3f5dbb8f5848c888c0d599be2dd4fa',''),
('22007','{29751}<>{29752} and length({29753})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','635b2c749af2495aa87688001bd73a6c',''),
('22008','({32238}>0 and {32238}<10m) or ({32238}=0 and {32239}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','869d6bd39ef1440193978c60518a91f7',''),
('22009','{29755}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','6ed1c046ba1a4246a6e30d5147e58250',''),
('22014','{29771}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','d81a92c3079b4d25be205b1e56b15a73',''),
('22015','{29772}>{$ICMP_LOSS_WARN} and {29772}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','cd4376c2f8e449b9b4923720374198af',''),
('22016','{29773}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','9e00ffd6364d4e238985a4f23601e1c6',''),
('22017','{29774}<>{29775} and length({29776})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','968c0bef31dc4ae89426b7dee5b76ea1',''),
('22018','({32240}>0 and {32240}<10m) or ({32240}=0 and {32241}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','119f36d60a1141f5a5dee9ee3aba894b',''),
('22019','{29778}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','cd1295131197495183bcc095622fb296',''),
('22024','{29794}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','0f59da9697304abd8c074c51ce3a4bef',''),
('22025','{29795}>{$ICMP_LOSS_WARN} and {29795}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','14b723dee48541a3a8b36c128681a200',''),
('22026','{29796}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','f8666db5e5a64d3fa7119deac48c317c',''),
('22027','{29797}<>{29798} and length({29799})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','375ba33fbee4425d97cbb15e410e52d3',''),
('22028','({32242}>0 and {32242}<10m) or ({32242}=0 and {32243}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','4e0a9fd604b04e6295108f8edf7910a9',''),
('22029','{29801}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','5ea3db8ebb2f49ab9fe7d38de50a4003',''),
('22034','{29817}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','fa71a2bcc742439a8eb76923db6dd34c',''),
('22035','{29818}>{$ICMP_LOSS_WARN} and {29818}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','c315770210b94fe39126514c41d6fa5d',''),
('22036','{29819}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','fe1eba68b565403a968bec8561362376',''),
('22037','{29820}<>{29821} and length({29822})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','caff4557fe8d4e0cb994c16a4d1c3eae',''),
('22038','({32244}>0 and {32244}<10m) or ({32244}=0 and {32245}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','661c463acbed4777b8269b9277a255fc',''),
('22039','{29824}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','eaa6f1c7bd334122af4cb08af35ebd86',''),
('22044','{29840}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','987ae7ade202464ba51fd8fcc67d3a19',''),
('22045','{29841}>{$ICMP_LOSS_WARN} and {29841}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','bf7a369d3b2a455496f8920177666d91',''),
('22046','{29842}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','9a35ff4d142640e387f247a8ae5021bc',''),
('22047','{29843}<>{29844} and length({29845})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','135707c751764f9087ebd32e1fe0b7ba',''),
('22048','({32246}>0 and {32246}<10m) or ({32246}=0 and {32247}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','1906ad6961664c74a2de31d20cd279b2',''),
('22049','{29847}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','239d876c15fe45ccb33ca87aba3a170f',''),
('22054','{29863}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','94618414658d4f5bad5f1cf544fba55d',''),
('22055','{29864}>{$ICMP_LOSS_WARN} and {29864}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','ecb0d03f65144dbe8e8e22339576fe1a',''),
('22056','{29865}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','bb70a4e882224f9d8302f8726ff81a8d',''),
('22057','{29866}<>{29867} and length({29868})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','f4c43870fa484e4088c1d9c973387140',''),
('22058','({32248}>0 and {32248}<10m) or ({32248}=0 and {32249}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','ec03a67de5ca4d8d834e1689a1cd28bf',''),
('22059','{29870}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','ce74c74936194791b8f8a09acd9d5501',''),
('22064','{29886}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','7c5ac0cbe19b4a119e8cd02802169849',''),
('22065','{29887}>{$ICMP_LOSS_WARN} and {29887}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','4b63a258093a4b5f8c7f415c054e290c',''),
('22066','{29888}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','8d37fb7e0f32438ea1b1f55389c4c024',''),
('22067','{29889}<>{29890} and length({29891})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','23b043f4b2344b8ea9140387454e6b02',''),
('22068','({32250}>0 and {32250}<10m) or ({32250}=0 and {32251}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','e2283150bf9e4248aa9bb5bd9cc1881e',''),
('22069','{29893}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','8d9d64c66ffe48899e799bf720182b6c',''),
('22074','{29909}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','4c4560f84de94f36a3e7d4941ded2cba',''),
('22075','{29910}>{$ICMP_LOSS_WARN} and {29910}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','44efdc627091496baa1fbe4bbe078e6f',''),
('22076','{29911}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','0a8c65b849dd4cb1a0d740d57323f76c',''),
('22077','{29912}<>{29913} and length({29914})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','56b334cfbcf54eba95c229b097e3cfd7',''),
('22078','({32252}>0 and {32252}<10m) or ({32252}=0 and {32253}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','3afcbbeb91004c2dae24efaf37fec710',''),
('22079','{29916}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','a63e914da20a47ef9d478b53d5e18042',''),
('22084','{29932}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','6a7f532a2e4a4b4cbe9435e560f8d281',''),
('22085','{29933}>{$ICMP_LOSS_WARN} and {29933}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','17c92f554c45423eb5b44bd08f34ad7f',''),
('22086','{29934}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','3b093888ce154887afaa6f738218d718',''),
('22087','{29935}<>{29936} and length({29937})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','dd116049df75471b8aacbedd082f2634',''),
('22088','({32254}>0 and {32254}<10m) or ({32254}=0 and {32255}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','63045c3ca20d4cd390b1247dfd3876c4',''),
('22089','{29939}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','7b8af02b531842e2b7f50037a8b3679a',''),
('22094','{29955}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','a3fbb030723c45208c51c923ca11fe1c',''),
('22095','{29956}>{$ICMP_LOSS_WARN} and {29956}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','6e46f7a198bb4cbcb4555e80a4ce7045',''),
('22096','{29957}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','1ac1be3472d04dddaadfa68228997594',''),
('22097','{29958}<>{29959} and length({29960})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','39c5e6d11d4c4866adac2a145a18dfb7',''),
('22098','({32256}>0 and {32256}<10m) or ({32256}=0 and {32257}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','b3004ef6450848c8bb55e7c802c2bd96',''),
('22099','{29962}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','67cd4c3273394776a7e7497ec8c1a091',''),
('22104','{29978}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','b1a43fa0251248fa897994575b8a27ac',''),
('22105','{29979}>{$ICMP_LOSS_WARN} and {29979}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','740b195a7246457ea28635c4b8ef0f83',''),
('22106','{29980}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','d85b8d94139d44c69349898d2149e7bd',''),
('22107','{29981}<>{29982} and length({29983})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','90a6f09f02ba4a36b019c6624ad13812',''),
('22108','({32258}>0 and {32258}<10m) or ({32258}=0 and {32259}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','2d0d281a078546959a644e758ede97d6',''),
('22109','{29985}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','36ee677a31184b738cd02b91aee5ff78',''),
('22114','{30001}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','c093758529824015be966f41e9e27757',''),
('22115','{30002}>{$ICMP_LOSS_WARN} and {30002}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','05873e7bbc8347f48daf707af0a3a1df',''),
('22116','{30003}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','f0a1435b054f46a3a496ab8c92591d96',''),
('22117','{30004}<>{30005} and length({30006})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','64b6467c681f43f4954a24d7bc326588',''),
('22118','({32260}>0 and {32260}<10m) or ({32260}=0 and {32261}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','81a1b9e9630c4b28b035da3b9fa7e6d7',''),
('22119','{30008}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','289a3d4d39e14627bb26817d21221c05',''),
('22124','{30024}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','169edfa3b9c94c61899cc540a5f4bd5c',''),
('22125','{30025}>{$ICMP_LOSS_WARN} and {30025}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','cb4bbbd51e854ac5b6877b85fd7b8bf5',''),
('22126','{30026}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','01e6c7a1fc2243dcabfd5ac1dec841ad',''),
('22127','{30027}<>{30028} and length({30029})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','53e27314562746fb803664ddbd13876f',''),
('22128','({32262}>0 and {32262}<10m) or ({32262}=0 and {32263}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','f71809adab344e60a2f6260548359167',''),
('22129','{30031}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','a462a1b6a16e4636aa3a70bbed7cc1cd',''),
('22134','{30047}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','f38f2bf1b3954e87afaae1b24f051705',''),
('22135','{30048}>{$ICMP_LOSS_WARN} and {30048}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','2384103bcdef45e48026fbb913a09e41',''),
('22136','{30049}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','492c760974924a489adf628a78facf20',''),
('22137','{30050}<>{30051} and length({30052})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','2783c5306701462290c245ff68ce0804',''),
('22138','({32264}>0 and {32264}<10m) or ({32264}=0 and {32265}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','f96b1dcd1cf84538a0d7729c5e4c683b',''),
('22139','{30054}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','8a6f02ead39b4b42be807585266c1fec',''),
('22144','{30070}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','ec9cc9ca00754d17a9ee8ff38e4aca2f',''),
('22145','{30071}>{$ICMP_LOSS_WARN} and {30071}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','1377c7e423284ac487afdeac6252f1e7',''),
('22146','{30072}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','143e8c34dc344611ace63e6bcfbfa556',''),
('22147','{30073}<>{30074} and length({30075})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','ecfbc704498740ee89afbffd1a2db22d',''),
('22148','({32266}>0 and {32266}<10m) or ({32266}=0 and {32267}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','e2afe16e11e14b80aa4a228eb9182f6a',''),
('22149','{30077}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','7d47b1df3a984db891811b14832ba2ee',''),
('22154','{30093}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','5dea6d7aa1344f27b66dbdce2350e93a',''),
('22155','{30094}>{$ICMP_LOSS_WARN} and {30094}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','a8d51531113a4017b732eb8d7247c777',''),
('22156','{30095}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','7acce40acf3a4eb28af79fc6d95bf190',''),
('22157','{30096}<>{30097} and length({30098})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','e09f00f0ad144e7a96e3abb38e4ab109',''),
('22158','({32268}>0 and {32268}<10m) or ({32268}=0 and {32269}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','27e64b9d917d4163b2f66c6f790b5a44',''),
('22159','{30100}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','096f1ccc1fd24cffb48720def5297031',''),
('22164','{30116}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','5ec7bb4a650f4c53a76ec3f89769952d',''),
('22165','{30117}>{$ICMP_LOSS_WARN} and {30117}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','66718f4417324cd7a88de35776b26c64',''),
('22166','{30118}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','95b144dfafeb40be96155e0a6e53515e',''),
('22167','{30119}<>{30120} and length({30121})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','5d609e8337b94830a52752ef8db4fd75',''),
('22168','({32270}>0 and {32270}<10m) or ({32270}=0 and {32271}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','0dcc036b17de4d00bf7d51b7b6076e3c',''),
('22169','{30123}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','c36eb285f1a94d29a40afb4bb8e923d4',''),
('22174','{30139}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','7257cb86a65547b5901cac08cacee3aa',''),
('22175','{30140}>{$ICMP_LOSS_WARN} and {30140}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','ae82608801a642d9b3ef8ddd06cee7f6',''),
('22176','{30141}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','d2f60c5c4a124a549eb02f62874dba8b',''),
('22177','{30142}<>{30143} and length({30144})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','f64be38a3557482087d75ed423ced500',''),
('22178','({32272}>0 and {32272}<10m) or ({32272}=0 and {32273}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','2139aea23b214169a369b4776865f501',''),
('22179','{30146}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','81af7d744ebf422ba065308fcb3c225a',''),
('22184','{30162}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','247cdbc159624b33a4b415d3e048c087',''),
('22185','{30163}>{$ICMP_LOSS_WARN} and {30163}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','4d4cde77c8324a88ac0798e2f096be69',''),
('22186','{30164}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','0f9f0ffd9322422babb52a5a5058d97e',''),
('22187','{30165}<>{30166} and length({30167})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','a5fed81db3c7447c8c62b02974765f57',''),
('22188','({32274}>0 and {32274}<10m) or ({32274}=0 and {32275}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','a3c432e1d04448d3940f69f8d9633c8f',''),
('22189','{30169}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','a82f1cafcb424685bb2f562c1c6dce11',''),
('22194','{30185}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','4db071c60daf4a6a836754875b22d27d',''),
('22195','{30186}>{$ICMP_LOSS_WARN} and {30186}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','5ce287958dc743abaa50a18c8ad3f2a5',''),
('22196','{30187}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','314db7fe9ce6403785f737263ee87914',''),
('22197','{30188}<>{30189} and length({30190})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','6f811bec794348e4937cbff22dbf5fb4',''),
('22198','({32276}>0 and {32276}<10m) or ({32276}=0 and {32277}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','44a2d709f4d0471997697905b8e3b456',''),
('22199','{30192}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','9a5729d397ad431aa79048b69a65fbd9',''),
('22204','{30208}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','4c7a404a7e7b413bbbac7a21c77b3fcc',''),
('22205','{30209}>{$ICMP_LOSS_WARN} and {30209}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','a9c3882f12d94b84a2cbed81db007011',''),
('22206','{30210}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','20cb06fa668d459e80505b23501735a7',''),
('22207','{30211}<>{30212} and length({30213})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','bf71167252cf48c99477a03d09523aa0',''),
('22208','({32278}>0 and {32278}<10m) or ({32278}=0 and {32279}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','3dfea70b489141e1ba7e967a8de964b8',''),
('22209','{30215}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','7a790a7c2af34786838280924d2cb252',''),
('22214','{30231}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','7651bd1c9c3b431eba1db692abe311a1',''),
('22215','{30232}>{$ICMP_LOSS_WARN} and {30232}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','433634cc1ce0426ba8337add07ee07f0',''),
('22216','{30233}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','a114fb9720bd429f8d406bac7b40a6d2',''),
('22217','{30234}<>{30235} and length({30236})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','58cd8a4c443e43d595a1afc5d045b67b',''),
('22218','({32280}>0 and {32280}<10m) or ({32280}=0 and {32281}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','7419d6e22c5d493ba843adf4f4f85529',''),
('22219','{30238}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','463cc0b4e29d4dddba8ddb16b8faa12b',''),
('22224','{30254}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','afd45d5f0f1b48d68af5e58e5b13f7d2',''),
('22225','{30255}>{$ICMP_LOSS_WARN} and {30255}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','bea20e4b6a634c3bb4c3c3f2c0ae91ce',''),
('22226','{30256}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','30e3c09970614f7eb6434aacdc427fcb',''),
('22227','{30257}<>{30258} and length({30259})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','78efe7ad5d8740f7ae087beb2952f74d',''),
('22228','({32282}>0 and {32282}<10m) or ({32282}=0 and {32283}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','f4c5126396ce4a07b9f0ef82aea599e3',''),
('22229','{30261}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','265226f23bfc4bd58cddd2a154c168ac',''),
('22234','{30277}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','9d1eaf8c440842b6867f539d8e4580b9',''),
('22235','{30278}>{$ICMP_LOSS_WARN} and {30278}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','bb1bddbd5b3b4c97a056a3030cb8220c',''),
('22236','{30279}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','4de979003a374346a66e18e0dc0ae8b3',''),
('22237','{30280}<>{30281} and length({30282})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','0b1965fc09b549f8a0301c3b560f6e04',''),
('22238','({32284}>0 and {32284}<10m) or ({32284}=0 and {32285}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','f6de5bd6b737473fa0bb8adcd7388f2f',''),
('22239','{30284}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','7b2ebd40ed1f4e72ac77c9bc31eab800',''),
('22244','{30300}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','c187031a85c340219bf773e53b1eb70b',''),
('22245','{30301}>{$ICMP_LOSS_WARN} and {30301}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','c30d9d87e01d4a4fb5f859b9b96a9597',''),
('22246','{30302}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','71bd6b58f328466fa8855e45f98d9148',''),
('22247','{30303}<>{30304} and length({30305})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','689814337c114068a71c0d510b6ffdee',''),
('22248','({32286}>0 and {32286}<10m) or ({32286}=0 and {32287}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','6919d6afa065438b976979a4f782414e',''),
('22249','{30307}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','dbe7f9e93602427e81932c39b4383974',''),
('22254','{30323}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','99b9920681f941c187f81d1c91755891',''),
('22255','{30324}>{$ICMP_LOSS_WARN} and {30324}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','530db893da94415db5fa5b1f26570bd5',''),
('22256','{30325}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','662e7c6a20bb4038b171f39f88bc5c5a',''),
('22257','{30326}<>{30327} and length({30328})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','ed72b3a73f5d498586ddfe57e9ad8638',''),
('22258','({32288}>0 and {32288}<10m) or ({32288}=0 and {32289}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','3b0a33b89325422c90a05950eb7b4ece',''),
('22259','{30330}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','e33c3d29eb9f41b49cc6002a5ee14058',''),
('22264','{30346}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','78f7c3cb9ad94841b6ef337df5a41914',''),
('22265','{30347}>{$ICMP_LOSS_WARN} and {30347}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','899836cd67f74868954af828bcf35521',''),
('22266','{30348}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','f5930e10af6e43d380c97f2522780a8e',''),
('22267','{30349}<>{30350} and length({30351})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','6aeb9e554ba1411f868668b8f31dca49',''),
('22268','({32290}>0 and {32290}<10m) or ({32290}=0 and {32291}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','d893994cfe8145b8bb0cf294b8a49f1f',''),
('22269','{30353}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','fea996e6b5e14205ad6e41faa9f53263',''),
('22274','{30369}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','2759e7d4eb114d0984aff53e6656e57e',''),
('22275','{30370}>{$ICMP_LOSS_WARN} and {30370}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','32d2897f2f1d42b0b2d4f40d6332cf48',''),
('22276','{30371}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','138f10a500aa4b29abf9760c80e22b06',''),
('22277','{30372}<>{30373} and length({30374})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','d6d2aa238d864cc1902b94e44e46b627',''),
('22278','({32292}>0 and {32292}<10m) or ({32292}=0 and {32293}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','40869f938b4f470cad6f5d8996edd088',''),
('22279','{30376}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','9a95ecc339b34b3a8713d62c68e2b330',''),
('22284','{30392}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','8b77ade2f79b4e3bafc22e7d8766e477',''),
('22285','{30393}>{$ICMP_LOSS_WARN} and {30393}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','cf4a28f174764d20953c4dcbca1576b6',''),
('22286','{30394}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','5ab1684fe5f34e3faa06192f47562b86',''),
('22287','{30395}<>{30396} and length({30397})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','a67b112302804d90931ea112d7412aa7',''),
('22288','({32294}>0 and {32294}<10m) or ({32294}=0 and {32295}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','6ca7b6f5acfb499b8ffbf5988a95616c',''),
('22289','{30399}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','f0686a8c2a6e42de980d6bca8ce4a0da',''),
('22294','{30415}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','ad75e791ea804015af4f056851d065e5',''),
('22295','{30416}>{$ICMP_LOSS_WARN} and {30416}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','53146df6198e4aa8a08ee2f5148b9273',''),
('22296','{30417}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','d30292aa239f4b08866dd626bea719d4',''),
('22297','{30418}<>{30419} and length({30420})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','31d043884c104f02aabfc12edc7cca38',''),
('22298','({32296}>0 and {32296}<10m) or ({32296}=0 and {32297}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','d721994d11d04783af8d3a474de35b1c',''),
('22299','{30422}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','5a3c6162200746f2b5fc1df3120dcc40',''),
('22304','{30438}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','9eba3716ff704612a9c498a7b5a72a15',''),
('22305','{30439}>{$ICMP_LOSS_WARN} and {30439}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','c0069ca77aa140d3ad4559979ad0973d',''),
('22306','{30440}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','9b01547e80e84f16b017901233e1fddd',''),
('22307','{30441}<>{30442} and length({30443})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','146922ff45f24d7ea7d3b7b5f0631f77',''),
('22308','({32298}>0 and {32298}<10m) or ({32298}=0 and {32299}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','06c5437331284cf1ae61668b8fd285b5',''),
('22309','{30445}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d51c0c2689a14b41aed889d67ec596df',''),
('22314','{30461}=0','MikroTik: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','dc51a869c302440ba48d352545782e6e',''),
('22315','{30462}>{$ICMP_LOSS_WARN} and {30462}<100','MikroTik: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','83fa0a00b298491a967e052ec0c3bafe',''),
('22316','{30463}>{$ICMP_RESPONSE_TIME_WARN}','MikroTik: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','7c027442ed3c44a0a26b4f35458a37f9',''),
('22317','{30464}<>{30465} and length({30466})>0','MikroTik: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MikroTik: System name has changed (new name: {ITEM.VALUE})','0172b76bc48d4dcead140c4880499777',''),
('22318','({32300}>0 and {32300}<10m) or ({32300}=0 and {32301}<10m)','MikroTik: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MikroTik: {HOST.NAME} has been restarted (uptime < 10m)','53e737a095a840df9abfcfd9c26007bf',''),
('22319','{30468}=0','MikroTik: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','2cc6310f1a824d40903f497f155a7834',''),
('22324','{30484}=0','Netgear Fastpath: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','424d07aafe9f4e8c8f647db6a43363d0',''),
('22325','{30485}>{$ICMP_LOSS_WARN} and {30485}<100','Netgear Fastpath: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','9d2efd0614ba4e16b3479ed515d3a9a2',''),
('22326','{30486}>{$ICMP_RESPONSE_TIME_WARN}','Netgear Fastpath: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','99888c77fc084d43b742a1f156d87832',''),
('22327','{30487}<>{30488} and length({30489})>0','Netgear Fastpath: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Netgear Fastpath: System name has changed (new name: {ITEM.VALUE})','61e82ab169374a51a1ebd876cc7813a8',''),
('22328','({32316}>0 and {32316}<10m) or ({32316}=0 and {32317}<10m)','Netgear Fastpath: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Netgear Fastpath: {HOST.NAME} has been restarted (uptime < 10m)','d68e4595fd4c4e5a9307b268cfe06b3e',''),
('22329','{30491}=0','Netgear Fastpath: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','cc91cb171901433bbb35752127e54ad0',''),
('22334','{30507}=0','QTech QSW: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','fd05f449cbc64dcba10029c246594568',''),
('22335','{30508}>{$ICMP_LOSS_WARN} and {30508}<100','QTech QSW: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','4b2e2d168a0b4da3b5999263f52f3c36',''),
('22336','{30509}>{$ICMP_RESPONSE_TIME_WARN}','QTech QSW: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','18f41db36192463eabaa3797034e578a',''),
('22337','{30510}<>{30511} and length({30512})>0','QTech QSW: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','QTech QSW: System name has changed (new name: {ITEM.VALUE})','27fa16e646224f88ad3b35ce7a71a18a',''),
('22338','({32318}>0 and {32318}<10m) or ({32318}=0 and {32319}<10m)','QTech QSW: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','QTech QSW: {HOST.NAME} has been restarted (uptime < 10m)','44d6c66a6a1641f8816031c0d5bf4040',''),
('22339','{30514}=0','QTech QSW: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','7a7c0c7501ca484491394fe82c75b401',''),
('22345','{30531}=0','TP-LINK: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','5b86c558f99d4ff5a8abca830df6e86e',''),
('22346','{30532}>{$ICMP_LOSS_WARN} and {30532}<100','TP-LINK: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','421d12d2c2a0405ba31c869c4d481b70',''),
('22347','{30533}>{$ICMP_RESPONSE_TIME_WARN}','TP-LINK: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','4d1df00b9476483fa77e6064708abf58',''),
('22348','{30534}<>{30535} and length({30536})>0','TP-LINK: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','TP-LINK: System name has changed (new name: {ITEM.VALUE})','367bce2d38fe4ecbbe23c34bc7ec6226',''),
('22349','({32320}>0 and {32320}<10m) or ({32320}=0 and {32321}<10m)','TP-LINK: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','TP-LINK: {HOST.NAME} has been restarted (uptime < 10m)','63b45803131d4391abfa313a222339e5',''),
('22350','{30538}=0','TP-LINK: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','7b533ce3df8c4405a04f90dd1e850a32',''),
('22355','{30554}=0','Ubiquiti AirOS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','2a6711992f354095b056b628be78022c',''),
('22356','{30555}>{$ICMP_LOSS_WARN} and {30555}<100','Ubiquiti AirOS: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','8e66ba0787b54af2897dd348e5453f10',''),
('22357','{30556}>{$ICMP_RESPONSE_TIME_WARN}','Ubiquiti AirOS: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','4ae253aa403a42ad8cd4721e2ffdfbca',''),
('22358','{30557}<>{30558} and length({30559})>0','Ubiquiti AirOS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Ubiquiti AirOS: System name has changed (new name: {ITEM.VALUE})','15523bce03a24cd6a4818ab655d1d2ad',''),
('22359','({32322}>0 and {32322}<10m) or ({32322}=0 and {32323}<10m)','Ubiquiti AirOS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Ubiquiti AirOS: {HOST.NAME} has been restarted (uptime < 10m)','2d9ed5a3b714461bbcdc4c530f955e5b',''),
('22360','{30561}=0','Ubiquiti AirOS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','7735f20ab7fd40b8b34cead6cb306b30',''),
('22365','{30577}=0','AIX: Zabbix agent is not available','','0','3','For passive checks only. The availability of the agent(s) and a host is used with `{$AGENT.TIMEOUT}` as the time threshold.',NULL,'0','0','0','','0','','1','','0','AIX: Zabbix agent is not available (for {$AGENT.TIMEOUT})','f0b9ecafede8476b94fd8dcab74cea87',''),
('22366','{30578}=0','FreeBSD: Zabbix agent is not available','','0','3','For passive checks only. The availability of the agent(s) and a host is used with `{$AGENT.TIMEOUT}` as the time threshold.',NULL,'0','0','0','','0','','1','','0','FreeBSD: Zabbix agent is not available (for {$AGENT.TIMEOUT})','fd9d36aaedff45f59017b1e714a5db69',''),
('22367','{30579}=0','HP-UX: Zabbix agent is not available','','0','3','For passive checks only; the availability of the agent(s) and a host is used with `{$AGENT.TIMEOUT}` as the time threshold.',NULL,'0','0','0','','0','','1','','0','HP-UX: Zabbix agent is not available (for {$AGENT.TIMEOUT})','ce008290ad6341b98386adf9ea5c315b',''),
('22368','{30580}<{$KERNEL.MAXFILES.MIN}','Linux: Configured max number of open filedescriptors is too low','','0','1','',NULL,'0','0','0','','0','','0','','0','Linux: Configured max number of open filedescriptors is too low (< {$KERNEL.MAXFILES.MIN})','b9bdcf42f54a409a9a9a616dbd0eaed2',''),
('22369','{30581}<{$KERNEL.MAXPROC.MIN}','Linux: Configured max number of processes is too low','','0','1','',NULL,'0','0','0','','0','','0','','0','Linux: Configured max number of processes is too low (< {$KERNEL.MAXPROC.MIN})','8cf253ca3eea4109a90443f9cb76fc5c',''),
('22370','{30582}>{$CPU.UTIL.CRIT}','Linux: High CPU utilization','','0','2','CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Linux: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','b4e904559b694df0ad45bcce7930c3a6',''),
('22371','{32779} and length({32780})>0','Linux: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Linux: System name has changed (new name: {ITEM.VALUE})','371a12f95a26438d8da659c84364631b',''),
('22372','{33945}=0','Linux: System time is out of sync','','0','2','The host''s system time is different from Zabbix server time.',NULL,'0','0','1','{33946}=1','0','','1','','0','Linux: System time is out of sync (diff with Zabbix server > {$SYSTEM.FUZZYTIME.MAX})','fb77b6ac381c4b5289584bd91e7da7d5',''),
('22373','{32781} and length({32782})>0','Linux: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','b1998f98c06b49dd8d71e1c6df409371',''),
('22374','{30590}<10m','Linux: {HOST.NAME} has been restarted','','0','2','The host uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Linux: {HOST.NAME} has been restarted (uptime < 10m)','1dbab80d7b6847e5b5a676cffba0fd1d',''),
('22375','{30591}<>{30592}','Linux: /etc/passwd has been changed','','0','1','',NULL,'0','0','0','','0','','1','','0','','3a764881727b4e7eb01e137ccfc968a2',''),
('22376','{30593}>{$MEMORY.UTIL.MAX}','Linux: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Linux: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','cfd395b1cde74ef18a5e5f840bd5142a',''),
('22377','{30594}=0','Linux: Zabbix agent is not available','','0','3','For passive agents only, host availability is used with `{$AGENT.TIMEOUT}` as a time threshold.',NULL,'0','0','0','','0','','1','','0','Linux: Zabbix agent is not available (for {$AGENT.TIMEOUT})','93594214371b4dc88b41663cad8537f0',''),
('22378','{30595}/{30596}*100>80','Linux: Getting closer to process limit','','0','2','',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1} active, {ITEM.LASTVALUE2} limit.','0','Linux: Getting closer to process limit (over 80% used)','ae5269e17d434927bfd6edc09a9a1f4d',''),
('22379','{30947}<{$SWAP.PFREE.MIN.WARN} and {30948}>0','Linux: High swap space usage','','0','2','If there is no swap configured, this trigger is ignored.',NULL,'0','0','0','','0','','0','Free: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Linux: High swap space usage (less than {$SWAP.PFREE.MIN.WARN}% free)','f49fc01c5ac945d59455563bdbcc6469',''),
('22380','{30951}<{$MEMORY.AVAILABLE.MIN} and {30952}>0','Linux: Lack of available memory','','0','3','The system is running out of memory.',NULL,'0','0','0','','0','','0','Available: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Linux: Lack of available memory (<{$MEMORY.AVAILABLE.MIN} of {ITEM.VALUE2})','686470cef97f48f6b017e9fc7a078afe',''),
('22381','{30601}/{30602}>{$LOAD_AVG_PER_CPU.MAX.WARN}
and {30603}>0
and {30604}>0','Linux: Load average is too high','','0','3','The load average per CPU is too high. The system may be slow to respond.',NULL,'0','0','0','','0','','0','Load averages(1m 5m 15m): ({ITEM.LASTVALUE1} {ITEM.LASTVALUE3} {ITEM.LASTVALUE4}), # of CPUs: {ITEM.LASTVALUE2}','0','Linux: Load average is too high (per CPU load over {$LOAD_AVG_PER_CPU.MAX.WARN} for 5m)','695f0c352377409d95aca3fe76d1cae2',''),
('22412','{30676}=1','Linux: Zabbix agent is not available','','0','3','For active agents, `nodata()` with `agent.ping` is used with `{$AGENT.NODATA_TIMEOUT}` as a time threshold.',NULL,'0','0','0','','0','','1','','0','Linux: Zabbix agent is not available (or nodata for {$AGENT.NODATA_TIMEOUT})','c1b9fdbe6a584d2cb25ff7077c667af1',''),
('22413','{30677}<{$KERNEL.MAXFILES.MIN}','Linux: Configured max number of open filedescriptors is too low','','0','1','',NULL,'0','0','0','','0','','0','','0','Linux: Configured max number of open filedescriptors is too low (< {$KERNEL.MAXFILES.MIN})','a7716b62422243b991a2697752d7cb1f',''),
('22414','{30678}<{$KERNEL.MAXPROC.MIN}','Linux: Configured max number of processes is too low','','0','1','',NULL,'0','0','0','','0','','0','','0','Linux: Configured max number of processes is too low (< {$KERNEL.MAXPROC.MIN})','740ed348fb1d41dca7c410123b668a48',''),
('22415','{30679}>{$CPU.UTIL.CRIT}','Linux: High CPU utilization','','0','2','CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Linux: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','e299778a6fcc4805bd5806f3b2ffe1c2',''),
('22416','{32789} and length({32790})>0','Linux: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Linux: System name has changed (new name: {ITEM.VALUE})','c2fc80044fa94f0d97c72bd1d749b731',''),
('22418','{32791} and length({32792})>0','Linux: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','e27cb7063ca841a2b78aa547ec0d001c',''),
('22419','{30687}<10m','Linux: {HOST.NAME} has been restarted','','0','2','The host uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Linux: {HOST.NAME} has been restarted (uptime < 10m)','64dbab85caf749f59f3da0c374746bc2',''),
('22420','{30688}<>{30689}','Linux: /etc/passwd has been changed','','0','1','',NULL,'0','0','0','','0','','1','','0','','c5a76894508c4f0e9dcc9f70e6f39f49',''),
('22421','{30690}>{$MEMORY.UTIL.MAX}','Linux: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Linux: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','fb368aa704064a44b9a4ed8c129cf3e8',''),
('22422','{30691}/{30692}*100>80','Linux: Getting closer to process limit','','0','2','',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1} active, {ITEM.LASTVALUE2} limit.','0','Linux: Getting closer to process limit (over 80% used)','fa21b02aebe143b192a20cd9403a68d0',''),
('22423','{30959}<{$SWAP.PFREE.MIN.WARN} and {30960}>0','Linux: High swap space usage','','0','2','If there is no swap configured, this trigger is ignored.',NULL,'0','0','0','','0','','0','Free: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Linux: High swap space usage (less than {$SWAP.PFREE.MIN.WARN}% free)','722692e0703e4609852439a9b751826d',''),
('22424','{30963}<{$MEMORY.AVAILABLE.MIN} and {30964}>0','Linux: Lack of available memory','','0','3','The system is running out of memory.',NULL,'0','0','0','','0','','0','Available: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Linux: Lack of available memory (<{$MEMORY.AVAILABLE.MIN} of {ITEM.VALUE2})','b3f51f3c63024d209fd01e17293127a6',''),
('22425','{30697}/{30698}>{$LOAD_AVG_PER_CPU.MAX.WARN}
and {30699}>0
and {30700}>0','Linux: Load average is too high','','0','3','The load average per CPU is too high. The system may be slow to respond.',NULL,'0','0','0','','0','','0','Load averages(1m 5m 15m): ({ITEM.LASTVALUE1} {ITEM.LASTVALUE3} {ITEM.LASTVALUE4}), # of CPUs: {ITEM.LASTVALUE2}','0','Linux: Load average is too high (per CPU load over {$LOAD_AVG_PER_CPU.MAX.WARN} for 5m)','72825a0c706043429ed1ff6656763052',''),
('22434','{30724}=0','Linux: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','28927c3715714a77a259d48943ddb8fe',''),
('22435','{30725}>{$ICMP_LOSS_WARN} and {30725}<100','Linux: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','f6d63c03e6f34888897464102fa369ec',''),
('22436','{30726}>{$ICMP_RESPONSE_TIME_WARN}','Linux: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','1c1b86790d6442e59f50d94f9844c337',''),
('22437','{30727}<>{30728} and length({30729})>0','Linux: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Linux: System name has changed (new name: {ITEM.VALUE})','eeb0355174d74892a4e3a078e6ac7952',''),
('22438','({32352}>0 and {32352}<10m) or ({32352}=0 and {32353}<10m)','Linux: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Linux: {HOST.NAME} has been restarted (uptime < 10m)','e129fb90ec084a83806aec27141cd6eb',''),
('22439','{30731}>{$MEMORY.UTIL.MAX}','Linux: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Linux: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','063b87d246b04e74a439114a05f00fe5',''),
('22440','{30732}=0','Linux: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','63d99e49b3584fb2bf61a7d56725fb3c',''),
('22441','{30973}<{$SWAP.PFREE.MIN.WARN} and {30974}>0','Linux: High swap space usage','','0','2','If there is no swap configured, this trigger is ignored.',NULL,'0','0','0','','0','','0','Free: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Linux: High swap space usage (less than {$SWAP.PFREE.MIN.WARN}% free)','8d66563ff7744cd6847325d473eaacfe',''),
('22442','{30977}<{$MEMORY.AVAILABLE.MIN} and {30978}>0','Linux: Lack of available memory','','0','3','The system is running out of memory.',NULL,'0','0','0','','0','','0','Available: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Linux: Lack of available memory (<{$MEMORY.AVAILABLE.MIN} of {ITEM.VALUE2})','b0a04a6a01854d0eb6f9f225c1108261',''),
('22443','{30737}/{30738}>{$LOAD_AVG_PER_CPU.MAX.WARN}
and {30739}>0
and {30740}>0','Linux: Load average is too high','','0','3','The load average per CPU is too high. The system may be slow to respond.',NULL,'0','0','0','','0','','0','Load averages(1m 5m 15m): ({ITEM.LASTVALUE1} {ITEM.LASTVALUE3} {ITEM.LASTVALUE4}), # of CPUs: {ITEM.LASTVALUE2}','0','Linux: Load average is too high (per CPU load over {$LOAD_AVG_PER_CPU.MAX.WARN} for 5m)','33df3354161047f0b47ad7736b70a302',''),
('22454','{30768}=0','macOS: Zabbix agent is not available','','0','3','For passive checks only; the availability of the agent(s) and a host is used with `{$AGENT.TIMEOUT}` as the time threshold.',NULL,'0','0','0','','0','','1','','0','macOS: Zabbix agent is not available (for {$AGENT.TIMEOUT})','0766e9c2a02f46e7adbb86dbef67556f',''),
('22455','{30769}=0','OpenBSD: Zabbix agent is not available','','0','3','For passive checks only; the availability of the agent(s) and a host is used with `{$AGENT.TIMEOUT}` as the time threshold.',NULL,'0','0','0','','0','','1','','0','OpenBSD: Zabbix agent is not available (for {$AGENT.TIMEOUT})','d046f431e11d4bd7be42e66e14a21663',''),
('22456','{30770}=0','Solaris: Zabbix agent is not available','','0','3','For passive checks only; the availability of the agent(s) and a host is used with `{$AGENT.TIMEOUT}` as the time threshold.',NULL,'0','0','0','','0','','1','','0','Solaris: Zabbix agent is not available (for {$AGENT.TIMEOUT})','4ca39fa4a86c45e19e03eff89edd239b',''),
('22457','{30771}<{$MEM.PAGE_TABLE_CRIT.MIN}','Windows: Number of free system page table entries is too low','','0','2',E'`Memory\\Free System Page Table Entries` has been less than `{$MEM.PAGE_TABLE_CRIT.MIN}` for 5 minutes. If the number is less than 5,000, there may be a memory leak.',NULL,'0','0','0','','0','','0','','0','Windows: Number of free system page table entries is too low (less {$MEM.PAGE_TABLE_CRIT.MIN} for 5m)','e3118e2e6109460f80cc2d56795ed42f',''),
('22458','{30772}>{$MEM.PAGE_SEC.CRIT.MAX}','Windows: The Memory Pages/sec is too high','','0','2','The Memory Pages/sec in the last 5 minutes exceeds `{$MEM.PAGE_SEC.CRIT.MAX}`. If the value is greater than 1,000, as a result of excessive paging, there may be a memory leak.',NULL,'0','0','0','','0','','0','','0','Windows: The Memory Pages/sec is too high (over {$MEM.PAGE_SEC.CRIT.MAX} for 5m)','ab4c9a66d16f42e6a32f6144f4d2a3ca',''),
('22459','{30773}>{$CPU.INTERRUPT.CRIT.MAX}','Windows: CPU interrupt time is too high','','0','2','The CPU Interrupt Time in the last 5 minutes exceeds `{$CPU.INTERRUPT.CRIT.MAX}`%.',NULL,'0','0','0','','0','','0','','0','Windows: CPU interrupt time is too high (over {$CPU.INTERRUPT.CRIT.MAX}% for 5m)','f67bedcb282349b2aac052baf4963480',''),
('22460','{30774}>{$CPU.PRIV.CRIT.MAX}','Windows: CPU privileged time is too high','','0','2','The CPU privileged time in the last 5 minutes exceeds {$CPU.PRIV.CRIT.MAX}%.',NULL,'0','0','0','','0','','0','','0','Windows: CPU privileged time is too high (over {$CPU.PRIV.CRIT.MAX}% for 5m)','4d099256b3ba42f1b90143e2014900dd',''),
('22461','{30775}>{$CPU.UTIL.CRIT}','Windows: High CPU utilization','','0','2','CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Windows: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','806aa232f56640ab98aacc79491fc4d7',''),
('22462','{32794} and length({32795})>0','Windows: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Windows: System name has changed (new name: {ITEM.VALUE})','6b50d36a4e29468a9546e880f3004399',''),
('22463','{33951}=0','Windows: System time is out of sync','','0','2','The host''s system time is different from Zabbix server time.',NULL,'0','0','1','{33952}=1','0','','1','','0','Windows: System time is out of sync (diff with Zabbix server > {$SYSTEM.FUZZYTIME.MAX})','37ca2366c8474cc8a49a605e93377601',''),
('22464','{30780}<10m','Windows: Host has been restarted','','0','2','The device uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Windows: Host has been restarted (uptime < 10m)','d27b9eab4034439f91dff41fe6f043ab',''),
('22465','{30781}>{$MEMORY.UTIL.MAX}','Windows: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Windows: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','b442993bb2a6404a8ebcb7be39d16ce6',''),
('22466','{30782}=0','Windows: Zabbix agent is not available','','0','3','For passive agents only, host availability is used with `{$AGENT.TIMEOUT}` as a time threshold.',NULL,'0','0','0','','0','','1','','0','Windows: Zabbix agent is not available (for {$AGENT.TIMEOUT})','05beb4500cae480892fad0739f99807d',''),
('22467','{30783} - {30784} * 2 > {$CPU.QUEUE.CRIT.MAX}','Windows: CPU queue length is too high','','0','2','The CPU Queue Length in the last 5 minutes exceeds `{$CPU.QUEUE.CRIT.MAX}`. According to actual observations, PQL should not exceed the number of cores * 2. To fine-tune the conditions, use the macro `{$CPU.QUEUE.CRIT.MAX }`.',NULL,'0','0','0','','0','','0','','0','Windows: CPU queue length is too high (over {$CPU.QUEUE.CRIT.MAX} for 5m)','8b1baeb26e154f99aefeaba3ea4fa63b',''),
('22468','{32555}<{$SWAP.PFREE.MIN.WARN} and {32556}>0','Windows: High swap space usage','','0','2','This trigger is ignored, if there is no swap configured',NULL,'0','0','0','','0','','0','Free: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Windows: High swap space usage (less than {$SWAP.PFREE.MIN.WARN}% free)','7c23e03060ce42b094aac2f8aea1a9ad',''),
('22479','{30812}=1','Windows: Zabbix agent is not available','','0','3','For active agents, `nodata()` with `agent.ping` is used with `{$AGENT.NODATA_TIMEOUT}` as a time threshold.',NULL,'0','0','0','','0','','1','','0','Windows: Zabbix agent is not available (or nodata for {$AGENT.NODATA_TIMEOUT})','e77c3b1849b64d45a3078794057a2582',''),
('22480','{30813}<{$MEM.PAGE_TABLE_CRIT.MIN}','Windows: Number of free system page table entries is too low','','0','2',E'`Memory\\Free System Page Table Entries` has been less than `{$MEM.PAGE_TABLE_CRIT.MIN}` for 5 minutes. If the number is less than 5,000, there may be a memory leak.',NULL,'0','0','0','','0','','0','','0','Windows: Number of free system page table entries is too low (less {$MEM.PAGE_TABLE_CRIT.MIN} for 5m)','37d6b965dd184b66b37018d4375d3e56',''),
('22481','{30814}>{$MEM.PAGE_SEC.CRIT.MAX}','Windows: The Memory Pages/sec is too high','','0','2','The Memory Pages/sec in the last 5 minutes exceeds `{$MEM.PAGE_SEC.CRIT.MAX}`. If the value is greater than 1,000, as a result of excessive paging, there may be a memory leak.',NULL,'0','0','0','','0','','0','','0','Windows: The Memory Pages/sec is too high (over {$MEM.PAGE_SEC.CRIT.MAX} for 5m)','05da8b30835e440fb1228fb9a0bc24a4',''),
('22482','{30815}>{$CPU.INTERRUPT.CRIT.MAX}','Windows: CPU interrupt time is too high','','0','2','The CPU Interrupt Time in the last 5 minutes exceeds `{$CPU.INTERRUPT.CRIT.MAX}`%.',NULL,'0','0','0','','0','','0','','0','Windows: CPU interrupt time is too high (over {$CPU.INTERRUPT.CRIT.MAX}% for 5m)','2eb661f6a42f40ce8cc25cef542763a9',''),
('22483','{30816}>{$CPU.PRIV.CRIT.MAX}','Windows: CPU privileged time is too high','','0','2','The CPU privileged time in the last 5 minutes exceeds {$CPU.PRIV.CRIT.MAX}%.',NULL,'0','0','0','','0','','0','','0','Windows: CPU privileged time is too high (over {$CPU.PRIV.CRIT.MAX}% for 5m)','cee69c70da6a415186b922305d0cabdc',''),
('22484','{30817}>{$CPU.UTIL.CRIT}','Windows: High CPU utilization','','0','2','CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Windows: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','ab3cbf18088a4d7a82f6c678ce49ffce',''),
('22485','{32798} and length({32799})>0','Windows: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Windows: System name has changed (new name: {ITEM.VALUE})','3aea75603e584d2f9dc96e7f3cc2b7fa',''),
('22487','{30822}<10m','Windows: Host has been restarted','','0','2','The device uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Windows: Host has been restarted (uptime < 10m)','4114e248a3b347f4a2fefc7816f2e940',''),
('22488','{30823}>{$MEMORY.UTIL.MAX}','Windows: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Windows: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','610a0893be834c11b35a0472dcabab7c',''),
('22489','{30824} - {30825} * 2 > {$CPU.QUEUE.CRIT.MAX}','Windows: CPU queue length is too high','','0','2','The CPU Queue Length in the last 5 minutes exceeds `{$CPU.QUEUE.CRIT.MAX}`. According to actual observations, PQL should not exceed the number of cores * 2. To fine-tune the conditions, use the macro `{$CPU.QUEUE.CRIT.MAX }`.',NULL,'0','0','0','','0','','0','','0','Windows: CPU queue length is too high (over {$CPU.QUEUE.CRIT.MAX} for 5m)','384393bb344e497382ea10e7fce7fcb3',''),
('22490','{32557}<{$SWAP.PFREE.MIN.WARN} and {32558}>0','Windows: High swap space usage','','0','2','This trigger is ignored, if there is no swap configured',NULL,'0','0','0','','0','','0','Free: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Windows: High swap space usage (less than {$SWAP.PFREE.MIN.WARN}% free)','ac93631f79584e2d9909f4bb2f12c866',''),
('22501','{30853}=0','Windows: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','08e22bd77606469d9e03183ec70dc89d',''),
('22502','{30854}>{$ICMP_LOSS_WARN} and {30854}<100','Windows: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','fa81e50132464ec486ea72929d18d778',''),
('22503','{30855}>{$ICMP_RESPONSE_TIME_WARN}','Windows: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','fba819f734de4b469fb7851501e55b21',''),
('22504','{30856}>{$CPU.UTIL.CRIT}','Windows: High CPU utilization','','0','2','CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Windows: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','ad2261f1ab77449cb1279725e8cf02f9',''),
('22505','{30857}<>{30858} and length({30859})>0','Windows: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Windows: System name has changed (new name: {ITEM.VALUE})','e257b5cf5d9949028c690722e4153612',''),
('22506','({32354}>0 and {32354}<10m) or ({32354}=0 and {32355}<10m)','Windows: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Windows: {HOST.NAME} has been restarted (uptime < 10m)','b7a0b390f8844d2aa05ee849d12495f7',''),
('22507','{30861}=0','Windows: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','a20254c09f7a4d4d9793da7b075121f3',''),
('22515','{30886}=0','Huawei OceanStor 5300 V5: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','ef6b5dc40f9a49599aae97c2cf68d3cb',''),
('22516','{30887}>{$ICMP_LOSS_WARN} and {30887}<100','Huawei OceanStor 5300 V5: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','c9765f7f271d46c99ad7dd45efa79849',''),
('22517','{30888}>{$ICMP_RESPONSE_TIME_WARN}','Huawei OceanStor 5300 V5: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','b8815a9e952047e09d1e657cea5d538e',''),
('22518','{30889}<>{30890} and length({30891})>0','Huawei OceanStor 5300 V5: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Huawei OceanStor 5300 V5: System name has changed (new name: {ITEM.VALUE})','72a31faa805b40e795a57649c724da1e',''),
('22519','({32378}>0 and {32378}<10m) or ({32378}=0 and {32379}<10m)','Huawei OceanStor 5300 V5: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Huawei OceanStor 5300 V5: {HOST.NAME} has been restarted (uptime < 10m)','0e3713bdf52e40d692cf256ac2a01988',''),
('22520','{30893}=0','Huawei OceanStor 5300 V5: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','b0c4103eac9447ee9f7f31627baf4eea',''),
('22521','{30894}=0','NetApp FAS3220: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','826eb817329249f59b7989c92ca62d99',''),
('22522','{30895}>{$ICMP_LOSS_WARN} and {30895}<100','NetApp FAS3220: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','4fb4b0022ca3433c8da1402f1d996760',''),
('22523','{30896}>{$ICMP_RESPONSE_TIME_WARN}','NetApp FAS3220: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','bb13f4d369294c0d83f8e6d888cbb062',''),
('22524','{30897}<>{30898} and length({30899})>0','NetApp FAS3220: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','NetApp FAS3220: System name has changed (new name: {ITEM.VALUE})','5266fcf7c9db457885c219385cfd5025',''),
('22525','({32380}>0 and {32380}<10m) or ({32380}=0 and {32381}<10m)','NetApp FAS3220: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','NetApp FAS3220: {HOST.NAME} has been restarted (uptime < 10m)','d33ca3f0d2f14feca01dce7bdf476776',''),
('22526','{30901}=0','NetApp FAS3220: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','e778b1ae80174f7aa82085b4882e1160',''),
('22527','{30902}=0','Cisco UCS: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','301541972752471e86046ce494a2febb',''),
('22528','{30903}>{$ICMP_LOSS_WARN} and {30903}<100','Cisco UCS: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','e051db53cf32406bb0d5ff9cc8d5ce7b',''),
('22529','{30904}>{$ICMP_RESPONSE_TIME_WARN}','Cisco UCS: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','a11942dac3504b64977c2de3e575d2eb',''),
('22530','{30905}<>{30906} and length({30907})>0','Cisco UCS: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco UCS: System name has changed (new name: {ITEM.VALUE})','3544e4ac11b44d14a6161523081c470e',''),
('22531','({32384}>0 and {32384}<10m) or ({32384}=0 and {32385}<10m)','Cisco UCS: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Cisco UCS: {HOST.NAME} has been restarted (uptime < 10m)','a933ba0e5c7f4e908afaba4381f65482',''),
('22532','{30909}=0','Cisco UCS: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','3c487a6b20c746eca9a7efc6058a60d9',''),
('22539','{30918}=0','HP iLO: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','755a4c5e809d418cbb1162102b0d1c26',''),
('22540','{30919}>{$ICMP_LOSS_WARN} and {30919}<100','HP iLO: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','0492380bc6374f24b92b4661b27d8f2c',''),
('22541','{30920}>{$ICMP_RESPONSE_TIME_WARN}','HP iLO: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','a869db9f341c479c80dca50bac0ff309',''),
('22542','{30921}<>{30922} and length({30923})>0','HP iLO: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HP iLO: System name has changed (new name: {ITEM.VALUE})','df3c9e64b0f844ddac8f40f6df956595',''),
('22543','({32404}>0 and {32404}<10m) or ({32404}=0 and {32405}<10m)','HP iLO: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','HP iLO: {HOST.NAME} has been restarted (uptime < 10m)','261749b9936c4a26b48d660f01435fb7',''),
('22544','{30925}=0','HP iLO: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','8870beab300f41ea8d54619fd2bf0371',''),
('22545','{30926}=0','IBM IMM: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','937225d93eea44b3a8328eee03cf66f0',''),
('22546','{30927}>{$ICMP_LOSS_WARN} and {30927}<100','IBM IMM: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','ec37a141b33c46308b8d810069ce9142',''),
('22547','{30928}>{$ICMP_RESPONSE_TIME_WARN}','IBM IMM: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','0541700de60549da8439f9b75cf83e7f',''),
('22548','{30929}<>{30930} and length({30931})>0','IBM IMM: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','IBM IMM: System name has changed (new name: {ITEM.VALUE})','188852025e644d5ab583f9d7a9dea06c',''),
('22549','({32521}>0 and {32521}<10m) or ({32521}=0 and {32522}<10m)','IBM IMM: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','IBM IMM: {HOST.NAME} has been restarted (uptime < 10m)','7dd529ec3f1a4a59846a3a76536a7fa0',''),
('22550','{30933}=0','IBM IMM: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','fbec2f12ac244723bb31dec5efcc6f85',''),
('22551','{30934}=0','Supermicro Aten: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','680c72ab6bb441779553b198081e3bf4',''),
('22552','{30935}>{$ICMP_LOSS_WARN} and {30935}<100','Supermicro Aten: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','e2e4bfca2d0c4f8ebd64bef322d2a368',''),
('22553','{30936}>{$ICMP_RESPONSE_TIME_WARN}','Supermicro Aten: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','b6fb489c6a624b2994c5e50ba75539b2',''),
('22554','{30937}<>{30938} and length({30939})>0','Supermicro Aten: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Supermicro Aten: System name has changed (new name: {ITEM.VALUE})','07b7a49bffea4c03a022eed632754f47',''),
('22555','({32523}>0 and {32523}<10m) or ({32523}=0 and {32524}<10m)','Supermicro Aten: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Supermicro Aten: {HOST.NAME} has been restarted (uptime < 10m)','37aab043ea474548ab1e54e504720bed',''),
('22556','{30941}=0','Supermicro Aten: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','caeb9732846b4ae586ee103ac0c4a65b',''),
('22557','{30943}>{$TIKV.PENDING_COMMANDS.MAX.WARN}','TiDB TiKV: Too many pending commands','','0','3','',NULL,'0','0','0','','0','','0','','0','TiDB TiKV: Too many pending commands (over {$TIKV.PENDING_COMMANDS.MAX.WARN} for 5m)','0f21c02b8e1c45d9bbe0c3313cea1a23',''),
('22566','length({31043})>0','OpenWeatherMap: There are errors in requests to OpenWeatherMap API','','0','3','Zabbix has received errors in requests to OpenWeatherMap API.',NULL,'0','0','0','','0','','1','{ITEM.LASTVALUE1}','0','','8c2c6f81e1e74f97a28538e714eee474',''),
('22569','{31054} <> 200','Proxmox VE: API service not available','','0','4','The API service is not available. Check your network and authorization settings.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','7ef8290fd6e242339d0e56d5e8eedb1a',''),
('22593','{31090}>{$MEMORY.UTIL.MAX}','TrueNAS CORE: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','TrueNAS CORE: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','3ee054e3d944441d9fd174e13b6a59ee',''),
('22595','{31092}<{$SWAP.PFREE.MIN.WARN} and {31093}>0','TrueNAS CORE: High swap space usage','','0','2','If there is no swap configured, this trigger is ignored.',NULL,'0','0','0','','0','','0','Free: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','TrueNAS CORE: High swap space usage (less than {$SWAP.PFREE.MIN.WARN}% free)','6c1708d53693435c87cd27f1568345c1',''),
('22596','{31094}<{$MEMORY.AVAILABLE.MIN} and {31095}>0','TrueNAS CORE: Lack of available memory','','0','3','The system is running out of memory.',NULL,'0','0','0','','0','','0','Available: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','TrueNAS CORE: Lack of available memory (<{$MEMORY.AVAILABLE.MIN} of {ITEM.VALUE2})','0a04cc4789a14f1090232fce196c0e4d',''),
('22597','{31096}/{31097}>{$LOAD_AVG_PER_CPU.MAX.WARN}
and {31098}>0
and {31099}>0','TrueNAS CORE: Load average is too high','','0','3','The load average per CPU is too high. The system may be slow to respond.',NULL,'0','0','0','','0','','0','Load averages(1m 5m 15m): ({ITEM.LASTVALUE1} {ITEM.LASTVALUE3} {ITEM.LASTVALUE4}), # of CPUs: {ITEM.LASTVALUE2}','0','TrueNAS CORE: Load average is too high (per CPU load over {$LOAD_AVG_PER_CPU.MAX.WARN} for 5m)','c923ea2cc04848de911ad9a41defaff6',''),
('22641','({31439} - now()) / 86400 < {$COCKROACHDB.CERT.CA.EXPIRY.WARN}','CockroachDB: CA certificate expires soon','','0','2','CA certificate expires soon.',NULL,'0','0','0','','0','','0','','0','CockroachDB: CA certificate expires soon (less than {$COCKROACHDB.CERT.CA.EXPIRY.WARN} days)','76a2093eb0214185ab8e03986f3f1474',''),
('22642','({31440} - now()) / 86400 < {$COCKROACHDB.CERT.NODE.EXPIRY.WARN}','CockroachDB: Node certificate expires soon','','0','2','Node certificate expires soon.',NULL,'0','0','0','','0','','0','','0','CockroachDB: Node certificate expires soon (less than {$COCKROACHDB.CERT.NODE.EXPIRY.WARN} days)','592152fe1dde4e81abd4bee76c3dae9d',''),
('22643','{31441} > {$COCKROACHDB.CLOCK.OFFSET.MAX.WARN} * 0.001','CockroachDB: Clock offset is too high','','0','2','Cockroach-measured clock offset is nearing limit (by default, servers kill themselves at 400ms from the mean).',NULL,'0','0','0','','0','','0','','0','CockroachDB: Clock offset is too high (over {$COCKROACHDB.CLOCK.OFFSET.MAX.WARN}ms for 5m)','bddc5c6ac7294bb4be9ed8a4f4d4f4a9',''),
('22644','{31442} = 500','CockroachDB: Node is unhealthy','','0','3','Node''s /health endpoint has returned HTTP 500 Internal Server Error which indicates unhealthy mode.',NULL,'0','0','0','','0','','0','','0','','6ccd74acda004a738c3003af4526cd91',''),
('22645','{31443} > {$COCKROACHDB.STATEMENTS.ERRORS.MAX.WARN}','CockroachDB: SQL statements errors rate is too high','','0','2','',NULL,'0','0','0','','0','','0','','0','CockroachDB: SQL statements errors rate is too high (over {$COCKROACHDB.STATEMENTS.ERRORS.MAX.WARN} per second for 5m)','7307fc4f2c29438e99eea0256a8755ce',''),
('22646','{31444} = 1','CockroachDB: Failed to fetch node data','','0','2','Zabbix has not received data for items for the last 5 minutes.',NULL,'0','0','0','','0','','0','','0','CockroachDB: Failed to fetch node data (or no data for 5m)','90f6cccaf3d94a3d853641482ccb5254',''),
('22647','{31445} < 10m','CockroachDB: Node has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','0','','0','CockroachDB: Node has been restarted (uptime < 10m)','83802e38f1414ca9b40e2d2df2d94941',''),
('22648','{31446} <> {31447} and length({31446}) > 0','CockroachDB: Version has changed','','0','1','',NULL,'0','0','0','','0','','0','','0','CockroachDB: Version has changed (new version: {ITEM.VALUE})','620aee1613e841acb44a438b4b9b68c9',''),
('22649','{31448} = 0','CockroachDB: Service is down','','0','3','',NULL,'0','0','0','','0','','0','','0','','d3c0d0a9e1f44c95a2246ab7081f581b',''),
('22650','{31449} / {31450} * 100 > {$COCKROACHDB.OPEN.FDS.MAX.WARN}','CockroachDB: Current number of open files is too high','','0','2','Getting close to open file descriptor limit.',NULL,'0','0','0','','0','','0','','0','CockroachDB: Current number of open files is too high (over {$COCKROACHDB.OPEN.FDS.MAX.WARN}% for 10m)','8c2035ad44ea44b2b690b086d11e8cfc',''),
('22651','{31451} > 0 and {31452} = 0','CockroachDB: Node is not executing SQL','','0','2','Node is not executing SQL despite having connections.',NULL,'0','0','0','','0','','0','','0','','b099e323ec974823bfd84317b152a1fb',''),
('22652','{31453} = 503 and {31454} > 5m','CockroachDB: Node is not ready','','0','3','Node''s /health?ready=1 endpoint has returned HTTP 503 Service Unavailable. Possible reasons:
- node is in the wait phase of the node shutdown sequence;
- node is unable to communicate with a majority of the other nodes in the cluster, likely because the cluster is unavailable due to too many nodes being down.',NULL,'0','0','0','','0','','0','','0','','0d2fa3b6ea434a07867b9f4d6156ea81',''),
('22655','{31459}<{$ENVOY.CERT.MIN}','Envoy Proxy: SSL certificate expires soon','','0','2','Please check certificate. Less than {$ENVOY.CERT.MIN} days left until the next certificate being managed will expire.',NULL,'0','0','0','','0','','0','Expires: {ITEM.VALUE}','0','Envoy Proxy: SSL certificate expires soon (less than {$CERT.EXPIRY.MIN} days)','d025e1c521ee4f53acd896d96609beec',''),
('22656','{31460} > 0','Envoy Proxy: Server state is not live','','0','3','',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','b90a6241e1294fdc8502426b7582c1c2',''),
('22657','{31461}=1','Envoy Proxy: Failed to fetch metrics data','','0','2','Zabbix has not received data for items for the last 10 minutes.',NULL,'0','0','0','','0','','1','','0','Envoy Proxy: Failed to fetch metrics data (or no data for 10m)','173c90200dd1451db10b8ea8b018bc54',''),
('22658','{31462}<10m','Envoy Proxy: Service has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Envoy Proxy: Service has been restarted (uptime < 10m)','01e29535e00143c9a64fe844f637f17e',''),
('22660','{31486}=2','MS Exchange 2016: Active checks are not available','','0','4','Active checks are considered unavailable. Agent is not sending heartbeat for prolonged time.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','8f04c3d6b3224382abf7472e8a4e38ba',''),
('22661','{31488}=2','IIS: Active checks are not available','','0','4','Active checks are considered unavailable. Agent is not sending heartbeat for prolonged time.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','b9d8edc865f54e8eb56e84392817ff5b',''),
('22662','{31490}=2','Linux: Active checks are not available','','0','4','Active checks are considered unavailable. Agent has not sent a heartbeat for a prolonged time.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','a022259fc3cf454f93bc82cca27391f1',''),
('22663','{31491}=2','Windows: Active checks are not available','','0','4','Active checks are considered unavailable. Agent has not sent a heartbeat for a prolonged time.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','bad86dfaf5274927bce35ad314a2d21a',''),
('22664','length({31470})>0','HashiCorp Consul Node: Failed to get local services','','0','2','Failed to get local services. Check debug log for more information.',NULL,'0','0','0','','0','','0','','0','','5cf09b213c044033af1d8e1d8821bc38',''),
('22665','{31471}>{$CONSUL.NODE.HEALTH_SCORE.MAX.HIGH}','HashiCorp Consul Node: Node''s health score is critical','','0','3','This metric ranges from 0 to 8, where 0 indicates "totally healthy".
This health score is used to scale the time between outgoing probes, and higher scores translate into longer probing intervals.
For more details see section IV of the Lifeguard paper: https://arxiv.org/pdf/1707.00788.pdf',NULL,'0','0','0','','0','','0','','0','HashiCorp Consul Node: Node''s health score is over {$CONSUL.NODE.HEALTH_SCORE.MAX.HIGH}','f964a907c55148bf80991352c7f2ae83',''),
('22666','{31472}>{$CONSUL.NODE.HEALTH_SCORE.MAX.WARN}','HashiCorp Consul Node: Node''s health score is warning','','0','2','This metric ranges from 0 to 8, where 0 indicates "totally healthy".
This health score is used to scale the time between outgoing probes, and higher scores translate into longer probing intervals.
For more details see section IV of the Lifeguard paper: https://arxiv.org/pdf/1707.00788.pdf',NULL,'0','0','0','','0','','0','','0','HashiCorp Consul Node: Node''s health score is too high (over {$CONSUL.NODE.HEALTH_SCORE.MAX.WARN} for 3m)','1fedc58f33ed4b9797fb37acfceba192',''),
('22667','{31473}<>{31474} and length({31475})>0','HashiCorp Consul Node: Version has been changed','','0','1','Consul version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HashiCorp Consul Node: Version has changed (new version: {ITEM.VALUE})','fa78d269c01548a083085a3a98e5a59b',''),
('22668','{31476}/{31477}*100>{$CONSUL.OPEN.FDS.MAX.WARN}','HashiCorp Consul Node: Current number of open files is too high','','0','2','"Heavy file descriptor usage (i.e., near the process’s file descriptor limit) indicates a potential file descriptor exhaustion issue."',NULL,'0','0','0','','0','','0','','0','HashiCorp Consul Node: Current number of open files is too high (over {$CONSUL.OPEN.FDS.MAX.WARN}% for 5m)','9e1a0b7f49844d1db525d00d5f1060f0',''),
('22671','{31480}<>{31481} and length({31482})>0','HashiCorp Consul Cluster: Leader has been changed','','0','1','Consul cluster version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','HashiCorp Consul Cluster: Leader has been changed (new value received: {ITEM.VALUE})','8f612c3cfbb74f55a7defed05039e2a5',''),
('22672','{31483}>0','HashiCorp Consul Cluster: One or more nodes in cluster in ''critical'' state','','0','3','One or more agents on current dc with serf health status ''critical''.',NULL,'0','0','0','','0','','0','','0','','8660702ae3674eb083d6dacb81ec3a4d',''),
('22673','{31484}>0','HashiCorp Consul Cluster: One or more nodes in cluster in ''warning'' state','','0','2','One or more agents on current dc with serf health status ''warning''.',NULL,'0','0','0','','0','','0','','0','','92136d6ee73b4bb5b88b9f1da1afe740',''),
('22677','length({31932})>0','HPE MSA 2040 Storage: There are errors in method requests to API','','0','3','There are errors in method requests to API.',NULL,'0','0','0','','0','','0','','0','','7f80562a0b4f4329be454c418de3f517',''),
('22678','{31933}=1','HPE MSA 2040 Storage: System health is in degraded state','','0','2','System health is in degraded state.',NULL,'0','0','0','','0','','0','','0','','ee37a443b22a4161a88014a0c32dfdfa',''),
('22679','{31934}=2','HPE MSA 2040 Storage: System health is in fault state','','0','3','System health is in fault state.',NULL,'0','0','0','','0','','0','','0','','54472b6cdf84418baf10b4a7d5e16e5c',''),
('22680','{31935}=3','HPE MSA 2040 Storage: System health is in unknown state','','0','1','System health is in unknown state.',NULL,'0','0','0','','0','','0','','0','','ccb821dafad1404dbc1873561a69b7cc',''),
('22681','{31936}=0','HPE MSA 2040 Storage: Service is down or unavailable','','0','4','HTTP/HTTPS service is down or unable to establish TCP connection.',NULL,'0','0','0','','0','','0','','0','','b8d07373a0fb4051a0534891b255994a',''),
('22742','length({31997})>0','HPE MSA 2060 Storage: There are errors in method requests to API','','0','3','There are errors in method requests to API.',NULL,'0','0','0','','0','','0','','0','','2133ddf10a3641d78e609948d6842687',''),
('22743','{31998}=1','HPE MSA 2060 Storage: System health is in degraded state','','0','2','System health is in degraded state.',NULL,'0','0','0','','0','','0','','0','','49e8c1d8a14f40b5acb2723e370ccccb',''),
('22744','{31999}=2','HPE MSA 2060 Storage: System health is in fault state','','0','3','System health is in fault state.',NULL,'0','0','0','','0','','0','','0','','2709a971f2ce417d8e269a0e5ebdd964',''),
('22745','{32000}=3','HPE MSA 2060 Storage: System health is in unknown state','','0','1','System health is in unknown state.',NULL,'0','0','0','','0','','0','','0','','fa35428a4f41453984bd0bfa566e0674',''),
('22746','{32001}=0','HPE MSA 2060 Storage: Service is down or unavailable','','0','4','HTTP/HTTPS service is down or unable to establish TCP connection.',NULL,'0','0','0','','0','','0','','0','','9c1bf26f95d946f386bbf613d3d55779',''),
('22807','length({32062})>0','HPE Primera: There are errors in requests to WSAPI','','0','3','Zabbix has received errors in requests to WSAPI.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','570d440e7ec9445585003208eca06e63',''),
('22808','{32063}=0','HPE Primera: Service is unavailable','','0','4','',NULL,'0','0','0','','0','','1','','0','','8e7aa46322c643878e509461dbb9169d',''),
('22825','length({32080})>0','AWS EC2: Failed to get alarms data','','0','2','Failed to get CloudWatch alarms for EC2.',NULL,'0','0','0','','0','','0','','0','','1d017a1213fb4bc9896add10a2b97dd6',''),
('22826','{32081}<{$AWS.EC2.CPU.CREDIT.BALANCE.MIN.WARN}','AWS EC2: Instance CPU Credit balance is too low','','0','2','The number of earned CPU credits has been less than {$AWS.EC2.CPU.CREDIT.BALANCE.MIN.WARN} in the last 5 minutes.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS EC2: Instance CPU Credit balance is too low (less {$AWS.EC2.CPU.CREDIT.BALANCE.MIN.WARN} for 5m)','4e67cac1f58a478fb0e47c52b402fd92',''),
('22827','{32082}>{$AWS.EC2.CPU.CREDIT.SURPLUS.BALANCE.MAX.WARN}','AWS EC2: Instance has spent too many CPU surplus credits','','0','2','The number of spent surplus credits that are not paid down and which thus incur an additional charge is over {$AWS.EC2.CPU.CREDIT.SURPLUS.BALANCE.MAX.WARN}.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS EC2: Instance has spent too many CPU surplus credits (over {$AWS.EC2.CPU.CREDIT.SURPLUS.BALANCE.MAX.WARN} for 15m)''','644ace5510164f329d9af65bd0ed4f34',''),
('22828','{32083}>{$AWS.EC2.CPU.UTIL.WARN.MAX}','AWS EC2: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','AWS EC2: High CPU utilization (over {$AWS.EC2.CPU.UTIL.WARN.MAX}% for 15m)','ea74d00067874b609e4846847033058f',''),
('22829','{32084}<{$AWS.EBS.BYTE.CREDIT.BALANCE.MIN.WARN}','AWS EC2: Byte Credit balance is too low','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS EC2: Byte Credit balance is too low (less {$AWS.EBS.BYTE.CREDIT.BALANCE.MIN.WARN}% for 5m)','27f3b00e295d4aeb9a2d0519e95da4e0',''),
('22830','{32085}<{$AWS.EBS.IO.CREDIT.BALANCE.MIN.WARN}','AWS EC2: I/O Credit balance is too low','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS EC2: I/O Credit balance is too low (less {$AWS.EBS.IO.CREDIT.BALANCE.MIN.WARN}% for 5m)','f4b9c2238b5443eab31255422bc22d7d',''),
('22831','length({32086})>0','AWS EC2: Failed to get metrics data','','0','2','Failed to get CloudWatch metrics for EC2.',NULL,'0','0','0','','0','','0','','0','','c2cf3f875aa14416a108dd05df7b053a',''),
('22832','{32087}=1','AWS EC2: Instance status check failed','','0','3','These checks detect problems that require your involvement to repair.
The following are examples of problems that can cause instance status checks to fail:

Failed system status checks
Incorrect networking or startup configuration
Exhausted memory
Corrupted file system
Incompatible kernel',NULL,'0','0','0','','0','','0','','0','','0fdd6b02eea948d3a6c958af7f195dc3',''),
('22833','{32088}=1','AWS EC2: System status check failed','','0','3','These checks detect underlying problems with your instance that require AWS involvement to repair.
The following are examples of problems that can cause system status checks to fail:

Loss of network connectivity
Loss of system power
Software issues on the physical host
Hardware issues on the physical host that impact network reachability',NULL,'0','0','0','','0','','0','','0','','723a254ffd72404ea0cc2366ff186c1c',''),
('22834','length({32089})>0','AWS EC2: Failed to get volumes info','','0','2','Failed to get CloudWatch volumes for EC2.',NULL,'0','0','0','','0','','0','','0','','844fb22685804fe7894af7c64b420824',''),
('22839','{32095}=0','OPNsense: DHCP server is not running','','0','3','Please check DHCP server settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','fba46d0094bc4f0e98537ceca27dd6bc',''),
('22840','{32096}=0','OPNsense: DNS server is not running','','0','3','Please check DNS server settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','0e2cbbbd999d476a84cb93a9b7ef42d6',''),
('22841','{32097}=0','OPNsense: Web server is not running','','0','3','Please check lighttpd service status.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','7864dec91012436f89b728019bf99fda',''),
('22842','{32098}<>1','OPNsense: Packet filter is not running','','0','4','Please check PF status.',NULL,'0','0','0','','0','','0','Current running state: {ITEM.LASTVALUE1}','0','','42d9a74d984d4ac2bf778be74cd8588f',''),
('22843','{32099}>{$SOURCE.TRACKING.TABLE.UTIL.MAX}','OPNsense: Source tracking table usage is high','','0','2','Please check the number of sticky connections.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','OPNsense: Source tracking table usage more than {$SOURCE.TRACKING.TABLE.UTIL.MAX}.','d1f03d136f30401b8f70cbc3196446ee',''),
('22844','{32100}>{$STATE.TABLE.UTIL.MAX}','OPNsense: State table usage is high','','0','2','Please check the number of connections.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','OPNsense: State table usage more than {$STATE.TABLE.UTIL.MAX}.','f31e301def314e9b81ee0f8a26dc1e37',''),
('22845','{32101}=0','OPNsense: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','f2cb074945624a8184ceb1ab3d3b2f52',''),
('22852','length({32116})>0','AWS RDS: Failed to get alarms data','','0','2','Failed to get CloudWatch alarms for RDS.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','112da2ba956740fda7edcd9bd3a8651c',''),
('22853','{32117}<{$AWS.RDS.BURST.CREDIT.BALANCE.MIN.WARN}','AWS RDS: Burst balance is too low','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS RDS: Burst balance is too low (less {$AWS.RDS.BURST.CREDIT.BALANCE.MIN.WARN}% for 5m)','730337e340cf4b129d4b38f1c7c82cf6',''),
('22854','{32118}<{$AWS.RDS.CPU.CREDIT.BALANCE.MIN.WARN}','AWS RDS: Instance CPU Credit balance is too low','','0','2','The number of earned CPU credits has been less than {$AWS.RDS.CPU.CREDIT.BALANCE.MIN.WARN} in the last 5 minutes.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS RDS: Instance CPU Credit balance is too low (less {$AWS.RDS.CPU.CREDIT.BALANCE.MIN.WARN} for 5m)','32994f2b06b8491b9b13d0b280e09001',''),
('22855','{32119}>{$AWS.RDS.CPU.UTIL.WARN.MAX}','AWS RDS: High CPU utilization','','0','2','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','AWS RDS: High CPU utilization (over {$AWS.RDS.CPU.UTIL.WARN.MAX}% for 15m)','0272980a53e14f22b06db30af49a1233',''),
('22856','{32120}<{$AWS.EBS.BYTE.CREDIT.BALANCE.MIN.WARN}','AWS RDS: Byte Credit balance is too low','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS RDS: Byte Credit balance is too low (less {$AWS.EBS.BYTE.CREDIT.BALANCE.MIN.WARN}% for 5m)','b878ee69a01a47a09677b184f8352668',''),
('22857','{32121}<{$AWS.EBS.IO.CREDIT.BALANCE.MIN.WARN}','AWS RDS: I/O Credit balance is too low','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS RDS: I/O Credit balance is too low (less {$AWS.EBS.IO.CREDIT.BALANCE.MIN.WARN}% for 5m)','556100b7e8414543bf88017e13fb718f',''),
('22858','length({32122})>0','AWS RDS: Failed to get events data','','0','2','Failed to get CloudWatch events for RDS.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','600805420f704d4daca1ac20903f27f5',''),
('22859','length({32123})>0','AWS RDS: Failed to get instance data','','0','2','Failed to get CloudWatch instance info for RDS.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','452195309f1f4211aeb71b43a373f86f',''),
('22860','length({32124})>0','AWS RDS: Failed to get metrics data','','0','2','Failed to get CloudWatch metrics for RDS.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','54c70842bf314ce2a9c95e0cfc57cc21',''),
('22861','{32125}=0','AWS RDS: Read replica in error state','','0','3','The status of a read replica.
False if the instance is in an error state.',NULL,'0','0','0','','0','','0','','0','','1f4767ba167f43b7ae9730ec834152a4',''),
('22864','length({32129})>0','AWS S3: Failed to get alarms data','','0','2','Failed to get CloudWatch alarms for S3 bucket.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','a8f8a7518aad4e32b23a8611afc8f48c',''),
('22865','length({32130})>0','AWS S3: Failed to get metrics data','','0','2','Failed to get CloudWatch metrics for S3 bucket.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','a8a0b4187f5f4e22b868dd038f53a2ba',''),
('22868','length({32134})>0','Azure: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','502cb582546046a29267715763c46bff',''),
('22869','{32135}=1','Azure VM: Virtual machine is degraded','','0','3','The resource is in a degraded state.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','c0170d8a09ae460da923fe773b2b0bd0',''),
('22870','{32136}=3','Azure VM: Virtual machine is in unknown state','','0','2','The resource state is unknown.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','e1b85765b83445ebbf15f02d782b9858',''),
('22871','{32137}=2','Azure VM: Virtual machine is unavailable','','0','4','The resource state is unavailable.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','b3d764ff735e44f8806cc4d29090719e',''),
('22872','{32138}>{$AZURE.VM.CPU.UTIL.CRIT}','Azure VM: High CPU utilization','','0','4','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','Azure VM: CPU utilization is high (over {$AZURE.VM.CPU.UTIL.CRIT}% for last 5m)','9e6d9394570641418b4291befb1e38e5',''),
('22873','length({32139})>0','Azure VM: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','87236c99652643ba800601a461d66d94',''),
('22874','{32140}>0','PostgreSQL: Dbstat: Checksum failures detected','','0','3','Data page checksum failures were detected on that DB instance:
https://www.postgresql.org/docs/current/checksums.html',NULL,'0','0','0','','0','','0','','0','','1d67b13f47134a538708c2a14dcfa6b1',''),
('22876','length({32406})>0','HPE Synergy: There are errors in requests to API','','0','3','Zabbix has received errors from API.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','dba8cff13328403dae2cbda8f106b384',''),
('22877','{32407}=0','HPE Synergy: Service is unavailable','','0','4','',NULL,'0','0','0','','0','','1','','0','','165774c1ffab46899352a36dd32bb574',''),
('22994','{32534}=1','Azure MySQL Flexible: MySQL server is degraded','','0','3','The resource is in a degraded state.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','e822fd2214fb41db9b57cdb8eec0444a',''),
('22995','{32535}=3','Azure MySQL Flexible: MySQL server is in unknown state','','0','2','The resource state is unknown.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','ebb35037a5b646a0bd2c6be44bb1f3c6',''),
('22996','{32536}=2','Azure MySQL Flexible: MySQL server is unavailable','','0','4','The resource state is unavailable.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','240b861c09a94e209036782b6c7496fa',''),
('22997','{32930}>{$AZURE.DB.ABORTED.CONN.MAX.WARN}','Azure MySQL Flexible: Server has aborted connections','','0','3','The number of failed attempts to connect to the MySQL server is more than `{$AZURE.DB.ABORTED.CONN.MAX.WARN}`.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','3346ea2331c14fa18658eb33e461ec7c',''),
('22998','{32538}>{$AZURE.DB.CPU.UTIL.CRIT}','Azure MySQL Flexible: High CPU utilization','','0','4','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','5af82cc95239479c86c7ab3dabcfb592',''),
('22999','length({32539})>0','Azure MySQL Flexible: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','98c1b86b79e9469cac2870fb2ba42949',''),
('23000','{32540}>{$AZURE.DB.STORAGE.PUSED.CRIT}','Azure MySQL Flexible: Storage space is critically low','','0','3','Critical utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','1703edc1553644e5aa25d35928c5eafd',''),
('23001','{32541}>{$AZURE.DB.STORAGE.PUSED.WARN}','Azure MySQL Flexible: Storage space is low','','0','2','High utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','a2ec23a5e77c40aa9e45d214f4e06ca1',''),
('23002','{32542}=1','Azure MySQL Single: MySQL server is degraded','','0','3','The resource is in a degraded state.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','91a32645266547d78df3a70b44c7782b',''),
('23003','{32543}=3','Azure MySQL Single: MySQL server is in unknown state','','0','2','The resource state is unknown.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','852aba88476a40aeb2170b933726b7d8',''),
('23004','{32544}=2','Azure MySQL Single: MySQL server is unavailable','','0','4','The resource state is unavailable.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','5f2d2254dfc24f5481207585bed0d933',''),
('23005','{32931}>{$AZURE.DB.FAILED.CONN.MAX.WARN}','Azure MySQL Single: Server has failed connections','','0','3','The number of failed attempts to connect to the MySQL server is more than `{$AZURE.DB.FAILED.CONN.MAX.WARN}`.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','5b3a09ca04704e6a9972ee4865d358cd',''),
('23006','{32546}>{$AZURE.DB.CPU.UTIL.CRIT}','Azure MySQL Single: High CPU utilization','','0','4','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','7115fb320e2b4cc1ad1739c8a6cee155',''),
('23007','length({32547})>0','Azure MySQL Single: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','df5fa33f8c13413bb9d61ea4470b9b2d',''),
('23008','{32548}>{$AZURE.DB.MEMORY.UTIL.CRIT}','Azure MySQL Single: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','a67b35f1ac674d6692b0b2bcd6f89bd8',''),
('23009','{32549}>{$AZURE.DB.STORAGE.PUSED.CRIT}','Azure MySQL Single: Storage space is critically low','','0','3','Critical utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','3afcb840e8004822a2dada2a89971f69',''),
('23010','{32550}>{$AZURE.DB.STORAGE.PUSED.WARN}','Azure MySQL Single: Storage space is low','','0','2','High utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','2e605f906b284f769e7c880d4e642b43',''),
('23012','{32560}=1','Azure PostgreSQL Flexible: PostgreSQL server is degraded','','0','3','The resource is in a degraded state.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','65b5c39b48e248c4866c511bbba91e1b',''),
('23013','{32561}=3','Azure PostgreSQL Flexible: PostgreSQL server is in unknown state','','0','2','The resource state is unknown.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','d8ce86c853064cba80c9883052ed1403',''),
('23014','{32562}=2','Azure PostgreSQL Flexible: PostgreSQL server is unavailable','','0','4','The resource state is unavailable.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','9572c9e56a6b44368bcf2d8a17a220d8',''),
('23015','{32563}>{$AZURE.DB.CPU.UTIL.CRIT}','Azure PostgreSQL Flexible: High CPU utilization','','0','4','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','f8672e4488b740a9a17395689c3d853c',''),
('23016','length({32564})>0','Azure PostgreSQL Flexible: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','55962f0d8a4c44c9a6b09da705e94c59',''),
('23017','{32565}>{$AZURE.DB.MEMORY.UTIL.CRIT}','Azure PostgreSQL Flexible: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','aac52a89709044ed987a365a1d5af17b',''),
('23018','{32566}>{$AZURE.DB.STORAGE.PUSED.CRIT}','Azure PostgreSQL Flexible: Storage space is critically low','','0','3','Critical utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','de3142bed28340d9abe518cd3967b024',''),
('23019','{32567}>{$AZURE.DB.STORAGE.PUSED.WARN}','Azure PostgreSQL Flexible: Storage space is low','','0','2','High utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','e948600affaa4ff4a0ab4e50f4858c0a',''),
('23020','{32568}=1','Azure PostgreSQL Single: PostgreSQL server is degraded','','0','3','The resource is in a degraded state.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','699ca12c916746b1bf1e121261771cc3',''),
('23021','{32569}=3','Azure PostgreSQL Single: PostgreSQL server is in unknown state','','0','2','The resource state is unknown.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','14e45ba0bc26409a89d92edfda152947',''),
('23022','{32570}=2','Azure PostgreSQL Single: PostgreSQL server is unavailable','','0','4','The resource state is unavailable.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','4dc9113f8a914ac098d8736dba5aed4a',''),
('23023','{32571}>{$AZURE.DB.CPU.UTIL.CRIT}','Azure PostgreSQL Single: High CPU utilization','','0','4','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','33bd2ef88ad3468b9f0b2b1358cc7448',''),
('23024','length({32572})>0','Azure PostgreSQL Single: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','dd3d0be997204f8b9968ef5839fb7a9b',''),
('23025','{32573}>{$AZURE.DB.MEMORY.UTIL.CRIT}','Azure PostgreSQL Single: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','3119f21167a546369c05d31cda2e0147',''),
('23026','{32574}>{$AZURE.DB.STORAGE.PUSED.CRIT}','Azure PostgreSQL Single: Storage space is critically low','','0','3','Critical utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','6538d2c8ed774feb951204308f1458ce',''),
('23027','{32575}>{$AZURE.DB.STORAGE.PUSED.WARN}','Azure PostgreSQL Single: Storage space is low','','0','2','High utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','7f7a004cfc2a492092dd74c475888e8b',''),
('23028','length({32576})>0','Meraki: There are errors in ''Get data'' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','2bf9355f548e4e9b9b8581fb43f175fe',''),
('23029','{32577}<>1','Meraki: Status is not online','','0','2','',NULL,'0','0','0','','0','','0','','0','','00583ac9e9824f7db22a1685421f0be9',''),
('23030','length({32578})>0','Meraki: There are errors in ''Get device data'' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','c8f8af6c92f14dc0bcdf426b124c7344',''),
('23031','length({48137})>3','Meraki: Configuration has been changed','','0','2','',NULL,'0','0','0','','0','','0','','0','','2fc56ad4baef4796a3ad7d097cad918f',''),
('23032','length({32580})>0','Meraki: There are errors in ''Get networks'' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','c149d21e19f3453b8e569c549ed2c78a',''),
('23033','length({32581})>0','Meraki: There are errors in ''Get VPNs'' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','f65ff582e1a84f5a9e9d6a9c0501b013',''),
('23034','{32582}<{$MERAKI.LICENSE.EXPIRE} and {32582}>=0','Meraki: License expires in less than {$MERAKI.LICENSE.EXPIRE} seconds','','0','2','',NULL,'0','0','0','','0','','0','','0','','8694c7fc18904004978a3ce46f06a67e',''),
('23035','{32583}<>1','Meraki: License status is not OK','','0','2','',NULL,'0','0','0','','0','','0','','0','','d4f71dd53bf8495789b53e063db3555b',''),
('23058','{32623}=0','Cisco Nexus 9000: Unavailable by ICMP ping','','0','4','The last three attempts returned a timeout. Check the connectivity of a device.',NULL,'0','0','0','','0','','0','','0','','2b9b678cb9fc407cb485136ddcf5953c',''),
('23059','{32624}>{$ICMP_LOSS_WARN} and {32624}<100','Cisco Nexus 9000: High ICMP ping loss','','0','2','',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','d32cffe7dcef4873ac8bb4d86119ddaa',''),
('23060','{32625}>{$ICMP_RESPONSE_TIME_WARN}','Cisco Nexus 9000: High ICMP ping response time','','0','2','',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','a51dc1f61eec4709b8f52b3df65eae86',''),
('23061','{32626}=1 and length({32627})>0','Cisco Nexus 9000: Device has been replaced','','0','1','The serial number of a device has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Nexus 9000: Device has been replaced (new serial number received)','b813bf6448fe4974911106e36b2d8888',''),
('23062','{32628}=1 and length({32629})>0','Cisco Nexus 9000: System name has changed','','0','1','The system name has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Cisco Nexus 9000: System name has changed (new name: {ITEM.VALUE})','cf98bf1ffe854a758f0006aaeb5096ab',''),
('23063','{32630}=1 and length({32631})>0','Cisco Nexus 9000: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons that system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','2','','0','','1','','0','','749b4c4b8f4e49caa6b239b15953ffb9',''),
('23064','{32632}<10m','Cisco Nexus 9000: Device has been restarted or reinitialized','','0','2','The record of SNMP Boots has changed in less than 10 minutes. The restart of a device also counts.',NULL,'0','0','0','','0','','1','','0','Cisco Nexus 9000: {HOST.NAME} has been restarted or reinitialized (uptime < 10m)','fc80a45e361842f09dfe9b047e1c6b5f',''),
('23065','{32633}=0','Cisco Nexus 9000: No SNMP data collection','','0','2','SNMP is not available for polling. Check the connectivity of a device and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','b60bca40b3b14f2384332103af74bd23',''),
('23095','{32684}="Disconnected"','Control-M: Server disconnected','','0','4','The server is disconnected.',NULL,'0','0','0','','0','','0','Triggered message: {ITEM.VALUE}, Current message: {ITEM.LASTVALUE1}','0','','406307967abf4218bebd9428dd8ecb8b',''),
('23096','{32685}<>"Connected" and
{32685}<>"Disconnected" and
{32685}<>""','Control-M: Server error','','0','4','The server has encountered an error.',NULL,'0','0','0','','0','','0','Triggered message: {ITEM.VALUE}, Current message: {ITEM.LASTVALUE1}','0','','1d7387fe4cd7462c81daa529b58d0e34',''),
('23097','{32686}=0 or
{32686}=10','Control-M: Server is down','','0','4','The server is down.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d9f5b1f636ec477c932159fd1c5baf16',''),
('23098','{32687}<>{32688} and
length({32689})>0','Control-M: Server version has changed','','0','1','The server version has changed. Acknowledge to close the problem manually.',NULL,'0','0','2','','0','','1','Old version: {ITEM.VALUE}, Current version: {ITEM.LASTVALUE1}','0','','14cdf1016ab24e5c8b03626fac5af263',''),
('23107','length({32701})>0','Veeam Backup: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','3487d31a2aa540009f006c6a4eff8c79',''),
('23110','{32704}>{$VEEAM.MANAGER.JOB.MAX.FAIL}','Veeam Backup: Failed job runs is too high','','0','3','',NULL,'0','0','0','','0','','1','','0','Veeam Backup: Failed job runs is too high (over {$VEEAM.MANAGER.JOB.MAX.FAIL})','4885d43f36b541219be87b5e5ea19088',''),
('23111','length({32705})>0','Veeam Backup: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','83316e2168414042aeb9d98857534baa',''),
('23112','{32706}>{$VEEAM.MANAGER.JOB.MAX.WARN}','Veeam Backup: Warning job runs is too high','','0','2','',NULL,'0','0','0','','0','','1','','0','Veeam Backup: Warning job runs is too high (over {$VEEAM.MANAGER.JOB.MAX.WARN})','f65998e99bb24e02a2810b632a4a3f4e',''),
('23113','{32707}=1','Azure MSSQL: Microsoft SQL database is degraded','','0','3','The resource is in a degraded state.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','5156f35b82084fd3b1d1a11c35757993',''),
('23114','{32708}=3','Azure MSSQL: Microsoft SQL database is in unknown state','','0','2','The resource state is unknown.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','0cf3cce995c241838e13df12d5908b61',''),
('23115','{32709}=2','Azure MSSQL: Microsoft SQL database is unavailable','','0','4','The resource state is unavailable.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','2130dc83dee94fdfad87894127c6a578',''),
('23116','{32710}>{$AZURE.DB.CPU.UTIL.CRIT}','Azure MSSQL: High CPU utilization','','0','4','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','506c034e707442519792a4366bc0879d',''),
('23117','length({32711})>0','Azure MSSQL: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','62d08fe430bd45e890c81547860d5c3d',''),
('23118','{32712}>{$AZURE.DB.STORAGE.PUSED.CRIT}','Azure MSSQL: Storage space is critically low','','0','3','Critical utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','a2d6cf9ac67d4d0eb312e9536299b345',''),
('23119','{32713}>{$AZURE.DB.STORAGE.PUSED.WARN}','Azure MSSQL: Storage space is low','','0','2','High utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','6dbf1d3aeb8b44b8bd96a9ca75f5249e',''),
('23120','{32714}=1','Azure MSSQL Serverless: Microsoft SQL database is degraded','','0','3','The resource is in a degraded state.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','37c52a28908a45378266f68acdf5c308',''),
('23121','{32715}=3','Azure MSSQL Serverless: Microsoft SQL database is in unknown state','','0','2','The resource state is unknown.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','20bd79f05f3241a9950a83dcd9e325ba',''),
('23122','{32716}=2','Azure MSSQL Serverless: Microsoft SQL database is unavailable','','0','4','The resource state is unavailable.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','124813388e9844e8aae5ce474a66a774',''),
('23123','{32717}>{$AZURE.DB.CPU.UTIL.CRIT}','Azure MSSQL Serverless: High CPU utilization','','0','4','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','933a04a1455b4a89b1527f9ce7848259',''),
('23124','length({32718})>0','Azure MSSQL Serverless: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','f56b125a8eff49d2aa002609c7df8b34',''),
('23125','{32719}>{$AZURE.DB.STORAGE.PUSED.CRIT}','Azure MSSQL Serverless: Storage space is critically low','','0','3','Critical utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','4638130e599243fba3206abc85a7447f',''),
('23126','{32720}>{$AZURE.DB.STORAGE.PUSED.WARN}','Azure MSSQL Serverless: Storage space is low','','0','2','High utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','4732eab4aabf439fa0b2d80b63e821e5',''),
('23161','{32787}<>0','Linux: Number of installed packages has been changed','','0','2','',NULL,'0','0','0','','0','','1','','0','','b950c306394f4b3c902060a8273cbcde',''),
('23163','{32793}<>0','Linux: Number of installed packages has been changed','','0','2','',NULL,'0','0','0','','0','','1','','0','','bd57d37531ac48f5b96a9f45453f3c35',''),
('23164','{32796} and length({32797})>0','Windows: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','9d5648eb580b41fca95d750113287567',''),
('23165','{32800} and length({32801})>0','Windows: Operating system description has changed','','0','1','The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','01bbea22605947dca9638229cf56e4e1',''),
('23167','{32803}=0','Zabbix agent is not available','','0','3','For passive agents only, host availability is used with `{$AGENT.TIMEOUT}` as a time threshold.',NULL,'0','0','0','','0','','1','','0','Zabbix agent is not available (for {$AGENT.TIMEOUT})','6767f9c764bb42dfa961baacf879f45c',''),
('23168','{32804}=1','Zabbix agent is not available','','0','3','For active agents, `nodata()` with `agent.ping` is used with `{$AGENT.NODATA_TIMEOUT}` as a time threshold.',NULL,'0','0','0','','0','','1','','0','Zabbix agent is not available (or nodata for {$AGENT.NODATA_TIMEOUT})','6bbb74c522d44baea8c6ceb666423da2',''),
('23169','{32805}=2','Active checks are not available','','0','4','Active checks are considered unavailable. Agent has not sent a heartbeat for a prolonged time.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','e91c556b0ff64292b9b9b5709a5d74b3',''),
('23170','{32806}=0','Generic by SNMP: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','085d6f785f1e46faa447d6921036d01d',''),
('23171','{32807}>{$ICMP_LOSS_WARN} and {32807}<100','Generic by SNMP: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','d1bd868814ba4ace9b5034ac4e303259',''),
('23172','{32808}>{$ICMP_RESPONSE_TIME_WARN}','Generic by SNMP: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','ecd74ec29b484a499414293bf671160b',''),
('23173','{32981}<>{32982} and length({32983})>0','Generic by SNMP: System name has changed','','0','1','The name of the system has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Generic by SNMP: System name has changed (new name: {ITEM.VALUE})','072bf35ea9d04c559ada5cb13d4b6802',''),
('23174','{32811}=0','Generic by SNMP: No SNMP data collection','','0','2','SNMP is not available for polling. Please check device connectivity and SNMP settings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d3aba975ec574b258c7f971152c5d4cd',''),
('23175','({32812}>0 and {32812}<10m) or ({32812}=0 and {32813}<10m)','Generic by SNMP: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Generic by SNMP: {HOST.NAME} has been restarted (uptime < 10m)','6f00359af55f45909bdecbad234c7654',''),
('23176','{32814}=0','ICMP Ping: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','b030876299434f3ba43e11c584104a81',''),
('23177','{32815}>{$ICMP_LOSS_WARN} and {32815}<100','ICMP Ping: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','42c4b0310aaf4b9c8cb502542b7dea90',''),
('23178','{32816}>{$ICMP_RESPONSE_TIME_WARN}','ICMP Ping: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','32b4d8f3eba34bd380803410111d4b7f',''),
('23223','{33773}>{$ZABBIX.SERVER.UTIL.MAX:"connector manager"}','Zabbix server: Utilization of connector manager processes is high','','0','3','Indicates potential performance issues with the connector manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33773}<{$ZABBIX.SERVER.UTIL.MIN:"connector manager"}','0','','0','','0','Zabbix server: Utilization of connector manager processes over {$ZABBIX.SERVER.UTIL.MAX:"connector manager"}%','5d72f9b951144e6797e19315b3a2da2b',''),
('23224','{33774}>{$ZABBIX.SERVER.UTIL.MAX:"connector worker"}','Zabbix server: Utilization of connector worker processes is high','','0','3','Indicates potential performance issues with the connector worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33774}<{$ZABBIX.SERVER.UTIL.MIN:"connector worker"}','0','','0','','0','Zabbix server: Utilization of connector worker processes over {$ZABBIX.SERVER.UTIL.MAX:"connector worker"}%','c6322f7a90d847b5a630bc9c64ce3c1b',''),
('23229','{33887}>{$ZABBIX.SERVER.UTIL.MAX:"connector manager"}','Zabbix server: Utilization of connector manager processes is high','','0','3','Indicates potential performance issues with the connector manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33887}<{$ZABBIX.SERVER.UTIL.MIN:"connector manager"}','0','','0','','0','Zabbix server: Utilization of connector manager processes over {$ZABBIX.SERVER.UTIL.MAX:"connector manager"}%','abe4c864b41a4a43b2ce963ed55a3f17',''),
('23230','{33888}>{$ZABBIX.SERVER.UTIL.MAX:"connector worker"}','Zabbix server: Utilization of connector worker processes is high','','0','3','Indicates potential performance issues with the connector worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33888}<{$ZABBIX.SERVER.UTIL.MIN:"connector worker"}','0','','0','','0','Zabbix server: Utilization of connector worker processes over {$ZABBIX.SERVER.UTIL.MAX:"connector worker"}%','ba984299c08f44b2a99c6fee187bcf01',''),
('23232','length({32932})>0','Azure: There are errors in storages requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','253f0835cd134d2591bb2be1b9dc9b29',''),
('23233','length({32933})>0','Azure Cosmos DB: There are errors in requests to API','','0','3','Zabbix has received errors in response to API requests.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','dfd484aa8a4e4b759e4e34c5318c7176',''),
('23234','({32934})<{$AZURE.DB.COSMOS.MONGO.AVAILABILITY}','Azure Cosmos DB: Cosmos DB for MongoDB account: Availability is low','','0','2','',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','c7649cd317f04a3d8fec0eebe3df6766',''),
('23238','length({32938}) > 0','GCP: Authorization has failed','','0','3','GCP: Authorization has failed.
Check the authorization parameters and GCP API availability from a network segment, where Zabbix-server/proxy is located.',NULL,'0','0','0','','0','','0','','0','','74c0e16244314ab4a920e32faca50444',''),
('23239','{32939} >= {$CLOUD_SQL.MSSQL.CPU.UTIL.MAX}','GCP MSSQL: High CPU utilization','','0','3','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','b8280e45fea8470e9f36f7f08e4a77e1',''),
('23240','{32940}=0','GCP MSSQL: Database engine is down','','0','3','Database engine is down.
If an instance experiences unplanned (non-maintenance) downtime, the instance state will still be RUNNING, but the database engine state metric will report 0.',NULL,'0','0','0','','0','','0','','0','','b3c7b8e2e38a42fe9d2ae3c84b637e53',''),
('23241','{32941} >= {$CLOUD_SQL.MSSQL.DISK.UTIL.CRIT}','GCP MSSQL: Disk space is critically low','','0','3','Critical utilization of the disk space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','2cbc7e3008f24197963df4ea920ab5a8',''),
('23242','{32942} >= {$CLOUD_SQL.MSSQL.DISK.UTIL.WARN}','GCP MSSQL: Disk space is low','','0','2','High utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','2569abbb94ca4df38cdd4f9d5a5df9fc',''),
('23243','{32943} = 10','GCP MSSQL: Failed to get the instance state','','0','3','Failed to get the instance state. 
Check access permissions to GCP API or service account.',NULL,'0','0','0','','0','','0','','0','','dff9067ad7de4ab1a4f83c9d482e6b71',''),
('23244','{32944} = 5','GCP MSSQL: Instance is in failed state','','0','3','The instance creation failed, or an operation left the instance in an own bad state.',NULL,'0','0','0','','0','','0','','0','','3d7e054340e94b09b085e508b9b76841',''),
('23245','{32945} = 4','GCP MSSQL: Instance is in maintenance','','0','1','The instance is down for maintenance.',NULL,'0','0','0','','0','','0','','0','','dd395fd3003f4fce847cd72309cdf7ec',''),
('23246','{32946} = 1','GCP MSSQL: Instance is in suspended state','','0','2','The instance is in suspended state. 
It is not available, for example, due to problems with billing.',NULL,'0','0','0','','0','','0','','0','','3c080bba511e44aab1139b66f00451ee',''),
('23247','{32947} = 6','GCP MSSQL: Instance is in unknown state','','0','3','The state of the instance is unknown.',NULL,'0','0','0','','0','','0','','0','','378b4d62582d416db7cb7fd6ed099ac9',''),
('23248','{32948} = 2','GCP MSSQL: Instance is stopped by the owner','','0','1','The instance has been stopped by the owner. 
It is not currently running, but it''s ready to be restarted.',NULL,'0','0','0','','0','','0','','0','','72ecba08f6424573a36b816da9695b89',''),
('23249','{32949} >= {$CLOUD_SQL.MSSQL.RAM.UTIL.MAX}','GCP MSSQL: High memory utilization','','0','4','RAM utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','c5003533f3524b8b868a0c2f86b1fa9b',''),
('23250','{32950} >= {$CLOUD_SQL.MYSQL.CPU.UTIL.MAX}','GCP MySQL: High CPU utilization','','0','3','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','5bf54c01665549c8a05f49db34c86191',''),
('23251','{32951}=0','GCP MySQL: Database engine is down','','0','3','Database engine is down.
If an instance experiences unplanned (non-maintenance) downtime, the instance state will still be RUNNING, but the database engine state metric will report 0.',NULL,'0','0','0','','0','','0','','0','','a3eff8c422f5427e9b1c6abb9854f73c',''),
('23252','{32952} >= {$CLOUD_SQL.MYSQL.DISK.UTIL.CRIT}','GCP MySQL: Disk space is critically low','','0','3','Critical utilization of the disk space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','d5ade16fb0494ca6af61100a2e643702',''),
('23253','{32953} >= {$CLOUD_SQL.MYSQL.DISK.UTIL.WARN}','GCP MySQL: Disk space is low','','0','2','High utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','3b5c84fee47f4376b19d0738b261c01b',''),
('23254','{32954} = 10','GCP MySQL: Failed to get the instance state','','0','3','Failed to get the instance state. 
Check access permissions to GCP API or service account.',NULL,'0','0','0','','0','','0','','0','','3b3adc89e0bb45a79a824121f49d2d02',''),
('23255','{32955} = 5','GCP MySQL: Instance is in failed state','','0','3','The instance creation failed, or an operation left the instance in an own bad state.',NULL,'0','0','0','','0','','0','','0','','65831fed3d19425c86933db4034ed565',''),
('23256','{32956} = 4','GCP MySQL: Instance is in maintenance','','0','1','The instance is down for maintenance.',NULL,'0','0','0','','0','','0','','0','','fae15d1ab46c418ebfdfdd73fb698b51',''),
('23257','{32957} = 1','GCP MySQL: Instance is in suspended state','','0','2','The instance is in suspended state. 
It is not available, for example, due to problems with billing.',NULL,'0','0','0','','0','','0','','0','','347215d307c8465cad41198f12b5ff68',''),
('23258','{32958} = 6','GCP MySQL: Instance is in unknown state','','0','3','The state of the instance is unknown.',NULL,'0','0','0','','0','','0','','0','','1387f9a2ef194d5bb5d1e548fc4eb8d3',''),
('23259','{32959} = 2','GCP MySQL: Instance is stopped by the owner','','0','1','The instance has been stopped by the owner. 
It is not currently running, but it''s ready to be restarted.',NULL,'0','0','0','','0','','0','','0','','9c66317433a24be985559fdb11907c70',''),
('23260','{32960} >= {$CLOUD_SQL.MYSQL.RAM.UTIL.MAX}','GCP MySQL: High memory utilization','','0','4','RAM utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','82e3af43d3104b4ba641e0be56d11662',''),
('23261','{32961} >= {$CLOUD_SQL.PGSQL.CPU.UTIL.MAX}','GCP PostgreSQL: High CPU utilization','','0','3','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','3ca3942121bd41029645a19fd3947416',''),
('23262','{32962}=0','GCP PostgreSQL: Database engine is down','','0','3','Database engine is down.
If an instance experiences unplanned (non-maintenance) downtime, the instance state will still be RUNNING, but the database engine state metric will report 0.',NULL,'0','0','0','','0','','0','','0','','f7b0fc21edcf489ab174eb06dee4fabe',''),
('23263','{32963} >= {$CLOUD_SQL.PGSQL.DISK.UTIL.CRIT}','GCP PostgreSQL: Disk space is critically low','','0','3','Critical utilization of the disk space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','c4fa1d580ffd4546b82605f94da5d2ba',''),
('23264','{32964} >= {$CLOUD_SQL.PGSQL.DISK.UTIL.WARN}','GCP PostgreSQL: Disk space is low','','0','2','High utilization of the storage space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','186a707ca3194c32a894ae809177a7e2',''),
('23265','{32965} = 10','GCP PostgreSQL: Failed to get the instance state','','0','3','Failed to get the instance state. 
Check access permissions to GCP API or service account.',NULL,'0','0','0','','0','','0','','0','','596020e32d0c4193a6626c960b4b5be8',''),
('23266','{32966} = 5','GCP PostgreSQL: Instance is in failed state','','0','3','The instance creation failed, or an operation left the instance in an own bad state.',NULL,'0','0','0','','0','','0','','0','','1a2efb6f755444c0bab85d2778018eb1',''),
('23267','{32967} = 4','GCP PostgreSQL: Instance is in maintenance','','0','1','The instance is down for maintenance.',NULL,'0','0','0','','0','','0','','0','','aad6fb2d86c84e33868aacbf160c3d65',''),
('23268','{32968} = 1','GCP PostgreSQL: Instance is in suspended state','','0','2','The instance is in suspended state. 
It is not available, for example, due to problems with billing.',NULL,'0','0','0','','0','','0','','0','','959072ed00c4461196bef71618799b82',''),
('23269','{32969} = 6','GCP PostgreSQL: Instance is in unknown state','','0','3','The state of the instance is unknown.',NULL,'0','0','0','','0','','0','','0','','5f1084f744b444f3b803110baf703973',''),
('23270','{32970} = 2','GCP PostgreSQL: Instance is stopped by the owner','','0','1','The instance has been stopped by the owner. 
It is not currently running, but it''s ready to be restarted.',NULL,'0','0','0','','0','','0','','0','','fb0df2eb001649febb6fc6513e056fcc',''),
('23271','{32971} >= {$CLOUD_SQL.PGSQL.RAM.UTIL.MAX}','GCP PostgreSQL: High memory utilization','','0','4','RAM utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','','bbbdbd9c3c5b407491b359f98e4e3fa9',''),
('23272','{32972} >= {$GCE.CPU.UTIL.MAX}','GCP Compute Engine Instance: High CPU utilization','','0','3','The CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','1','','0','GCP Compute Engine Instance: High CPU utilization (over {$GCE.CPU.UTIL.MAX}% for 15m)','fb8e28649b4947e9a11d891e3126a3a1',''),
('23273','{32973} = 10','GCP Compute Engine Instance: Failed to get the instance state','','0','3','Failed to get the instance state.
Check access permissions to GCP API or service account.',NULL,'0','0','0','','0','','1','','0','','96abd48a3e684e1b9b95fdd96d095188',''),
('23274','{32974} = 7','GCP Compute Engine Instance: Instance is in suspended state','','0','1','The VM is in a suspended state. You can resume the VM or delete it.',NULL,'0','0','0','','0','','1','','0','','1223f00a5e4b4bc8aa9e8ec08253c4cc',''),
('23275','{32975} = 4','GCP Compute Engine Instance: The instance is in repairing state','','0','2','The VM is being repaired.
Repairing occurs when the VM encounters an internal error or the underlying machine is unavailable due to maintenance.
During this time, the VM is unusable.',NULL,'0','0','0','','0','','1','','0','','d2144e2277ec458c80d2b948364f1924',''),
('23276','{32976} = 5','GCP Compute Engine Instance: The instance is in terminated state','','0','3','The VM is stopped. You stopped the VM, or the VM encountered a failure.',NULL,'0','0','0','','0','','1','','0','','4a010c2b1e6f4ec88dbbe97255b9bac4',''),
('23282','{33009}>{$ZABBIX.PROXY.UTIL.MAX:"discovery manager"}','Zabbix proxy: Utilization of discovery manager processes is high','','0','3','Indicates potential performance issues with the discovery manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33009}<{$ZABBIX.PROXY.UTIL.MIN:"discovery manager"}','0','','0','','0','Zabbix proxy: Utilization of discovery manager processes over {$ZABBIX.PROXY.UTIL.MAX:"discovery manager"}%','e1dd2821756d489cb5443c924e57c356',''),
('23283','{33010}>{$ZABBIX.PROXY.UTIL.MAX:"discovery worker"}','Zabbix proxy: Utilization of discovery worker processes is high','','0','3','Indicates potential performance issues with the discovery worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33010}<{$ZABBIX.PROXY.UTIL.MIN:"discovery worker"}','0','','0','','0','Zabbix proxy: Utilization of discovery worker processes over {$ZABBIX.PROXY.UTIL.MAX:"discovery worker"}%','ff023c3fce664dff9fdcb3f8724f4832',''),
('23284','{33011}>{$ZABBIX.PROXY.UTIL.MAX:"discovery manager"}','Zabbix proxy: Utilization of discovery manager processes is high','','0','3','Indicates potential performance issues with the discovery manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33011}<{$ZABBIX.PROXY.UTIL.MIN:"discovery manager"}','0','','0','','0','Zabbix proxy: Utilization of discovery manager processes over {$ZABBIX.PROXY.UTIL.MAX:"discovery manager"}%','8d0651ac99ba4c28b9525885e04ecb98',''),
('23285','{33012}>{$ZABBIX.PROXY.UTIL.MAX:"discovery worker"}','Zabbix proxy: Utilization of discovery worker processes is high','','0','3','Indicates potential performance issues with the discovery worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33012}<{$ZABBIX.PROXY.UTIL.MIN:"discovery worker"}','0','','0','','0','Zabbix proxy: Utilization of discovery worker processes over {$ZABBIX.PROXY.UTIL.MAX:"discovery worker"}%','63c45f37a5cd41c091ba3af451325220',''),
('23286','{33775}>{$ZABBIX.SERVER.UTIL.MAX:"discovery manager"}','Zabbix server: Utilization of discovery manager processes is high','','0','3','Indicates potential performance issues with the discovery manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33775}<{$ZABBIX.SERVER.UTIL.MIN:"discovery manager"}','0','','0','','0','Zabbix server: Utilization of discovery manager processes over {$ZABBIX.SERVER.UTIL.MAX:"discovery manager"}%','5af0558db3264b43981aafa8969ce433',''),
('23287','{33776}>{$ZABBIX.SERVER.UTIL.MAX:"discovery worker"}','Zabbix server: Utilization of discovery worker processes is high','','0','3','Indicates potential performance issues with the discovery worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33776}<{$ZABBIX.SERVER.UTIL.MIN:"discovery worker"}','0','','0','','0','Zabbix server: Utilization of discovery worker processes over {$ZABBIX.SERVER.UTIL.MAX:"discovery worker"}%','8dc524466ce04c0e97b613305fee0153',''),
('23290','{33889}>{$ZABBIX.SERVER.UTIL.MAX:"discovery manager"}','Zabbix server: Utilization of discovery manager processes is high','','0','3','Indicates potential performance issues with the discovery manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33889}<{$ZABBIX.SERVER.UTIL.MIN:"discovery manager"}','0','','0','','0','Zabbix server: Utilization of discovery manager processes over {$ZABBIX.SERVER.UTIL.MAX:"discovery manager"}%','96418e054e834497baffbd9ed0a4f6bf',''),
('23291','{33890}>{$ZABBIX.SERVER.UTIL.MAX:"discovery worker"}','Zabbix server: Utilization of discovery worker processes is high','','0','3','Indicates potential performance issues with the discovery worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33890}<{$ZABBIX.SERVER.UTIL.MIN:"discovery worker"}','0','','0','','0','Zabbix server: Utilization of discovery worker processes over {$ZABBIX.SERVER.UTIL.MAX:"discovery worker"}%','fd92a81e2c614aa8826f7ff92fad801a',''),
('23292','{33023}>{$ZABBIX.PROXY.UTIL.MAX:"agent poller"}','Zabbix proxy: Utilization of agent poller processes is high','','0','3','Indicates potential performance issues with the agent poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33023}<{$ZABBIX.PROXY.UTIL.MIN:"agent poller"}','0','','0','','0','Zabbix proxy: Utilization of agent poller processes over {$ZABBIX.PROXY.UTIL.MAX:"agent poller"}%','5abbe55bf614492d982e4af0f11b01e2',''),
('23293','{33024}>{$ZABBIX.PROXY.UTIL.MAX:"http agent poller"}','Zabbix proxy: Utilization of http agent poller processes is high','','0','3','Indicates potential performance issues with the http agent poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33024}<{$ZABBIX.PROXY.UTIL.MIN:"http agent poller"}','0','','0','','0','Zabbix proxy: Utilization of http agent poller processes over {$ZABBIX.PROXY.UTIL.MAX:"http agent poller"}%','a5d7a54efea843c495795d14bbff166b',''),
('23294','{33025}>{$ZABBIX.PROXY.UTIL.MAX:"agent poller"}','Zabbix proxy: Utilization of agent poller processes is high','','0','3','Indicates potential performance issues with the agent poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33025}<{$ZABBIX.PROXY.UTIL.MIN:"agent poller"}','0','','0','','0','Zabbix proxy: Utilization of agent poller processes over {$ZABBIX.PROXY.UTIL.MAX:"agent poller"}%','c35b8290fb2840e9bb403f54ad0e7b97',''),
('23295','{33026}>{$ZABBIX.PROXY.UTIL.MAX:"http agent poller"}','Zabbix proxy: Utilization of http agent poller processes is high','','0','3','Indicates potential performance issues with the http agent poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33026}<{$ZABBIX.PROXY.UTIL.MIN:"http agent poller"}','0','','0','','0','Zabbix proxy: Utilization of http agent poller processes over {$ZABBIX.PROXY.UTIL.MAX:"http agent poller"}%','460ddec16c564c6dbc706b21747aa622',''),
