('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}\r\nand {30603}>0\r\nand {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}\r\nand {30699}>0\r\nand {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}\r\nand {30739}>0\r\nand {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','`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','`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}\r\nand {31098}>0\r\nand {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:\r\n- node is in the wait phase of the node shutdown sequence;\r\n- 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".\r\nThis health score is used to scale the time between outgoing probes, and higher scores translate into longer probing intervals.\r\nFor 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".\r\nThis health score is used to scale the time between outgoing probes, and higher scores translate into longer probing intervals.\r\nFor 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.\r\nThe following are examples of problems that can cause instance status checks to fail:\r\n\r\nFailed system status checks\r\nIncorrect networking or startup configuration\r\nExhausted memory\r\nCorrupted file system\r\nIncompatible 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.\r\nThe following are examples of problems that can cause system status checks to fail:\r\n\r\nLoss of network connectivity\r\nLoss of system power\r\nSoftware issues on the physical host\r\nHardware 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.\r\nFalse 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:\r\nhttps://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\r\n{32685}<>"Disconnected" and\r\n{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\r\n{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\r\nlength({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.\r\nCheck 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.\r\nIf 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. \r\nCheck 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. \r\nIt 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. \r\nIt 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.\r\nIf 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. \r\nCheck 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. \r\nIt 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. \r\nIt 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.\r\nIf 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. \r\nCheck 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. \r\nIt 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. \r\nIt 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.\r\nCheck 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.\r\nRepairing occurs when the VM encounters an internal error or the underlying machine is unavailable due to maintenance.\r\nDuring 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',''),
('23296','{33027}=1','Zabbix proxy: Failed to fetch stats data','','0','2','Zabbix has not received statistics data for `{$ZABBIX.PROXY.NODATA_TIMEOUT}`.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: Failed to fetch stats data (or no data for {$ZABBIX.PROXY.NODATA_TIMEOUT})','2f314a33e06444d88fd99b5442b10a9e',''),
('23297','{33767}>{$ZABBIX.SERVER.UTIL.MAX:"agent poller"}','Zabbix server: 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','{33767}<{$ZABBIX.SERVER.UTIL.MIN:"agent poller"}','0','','0','','0','Zabbix server: Utilization of agent poller processes over {$ZABBIX.SERVER.UTIL.MAX:"agent poller"}%','01c490b526144241930b908b64c92c97',''),
('23298','{33781}>{$ZABBIX.SERVER.UTIL.MAX:"http agent poller"}','Zabbix server: 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','{33781}<{$ZABBIX.SERVER.UTIL.MIN:"http agent poller"}','0','','0','','0','Zabbix server: Utilization of http agent poller processes over {$ZABBIX.SERVER.UTIL.MAX:"http agent poller"}%','3ba6561155df4cebb1111a6f229c483a',''),
('23301','{33881}>{$ZABBIX.SERVER.UTIL.MAX:"agent poller"}','Zabbix server: 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','{33881}<{$ZABBIX.SERVER.UTIL.MIN:"agent poller"}','0','','0','','0','Zabbix server: Utilization of agent poller processes over {$ZABBIX.SERVER.UTIL.MAX:"agent poller"}%','f47c5db67da54295950939e7f18ed062',''),
('23302','{33895}>{$ZABBIX.SERVER.UTIL.MAX:"http agent poller"}','Zabbix server: 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','{33895}<{$ZABBIX.SERVER.UTIL.MIN:"http agent poller"}','0','','0','','0','Zabbix server: Utilization of http agent poller processes over {$ZABBIX.SERVER.UTIL.MAX:"http agent poller"}%','79604a0e6fe040b391f00d97ad11f56c',''),
('23303','{33034}=1','Zabbix server: Failed to fetch stats data','','0','2','Zabbix has not received statistics data for `{$ZABBIX.SERVER.NODATA_TIMEOUT}`.',NULL,'0','0','0','','0','','0','','0','Zabbix server: Failed to fetch stats data (or no data for {$ZABBIX.SERVER.NODATA_TIMEOUT})','07fbcbe743f84727838c982a51d36441',''),
('23304','length({33035})>0','AWS ECS Cluster: Failed to get alarms data','','0','2','Failed to get CloudWatch alarms for ECS Cluster.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','f8ff542b35a345e490910323d5dee19c',''),
('23305','{33036}>{$AWS.ECS.CLUSTER.CPU.UTIL.WARN}','AWS ECS Cluster: 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 ECS Cluster: High CPU utilization (over {$AWS.ECS.CLUSTER.CPU.UTIL.WARN}% for 15m)','5395c1d6d27c495a8972d2ea8ca8b02a',''),
('23306','{33037}>{$AWS.ECS.CLUSTER.MEMORY.UTIL.WARN}','AWS ECS Cluster: High memory utilization','','0','2','The system is running out of free memory.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','AWS ECS Cluster: High memory utilization (over {$AWS.ECS.CLUSTER.MEMORY.UTIL.WARN}% for 15m)','a7df755466704f339e5479aeeca3fe30',''),
('23307','length({33038})>0','AWS ECS Cluster: Failed to get metrics data','','0','2','Failed to get CloudWatch metrics for ECS Cluster.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','b475c468dbe0477f92b40122321235b0',''),
('23312','length({33044})>0','AWS ECS Serverless: Failed to get alarms data','','0','2','Failed to get CloudWatch alarms for ECS Cluster.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','76b9777749a041049faaa469daf82c4e',''),
('23313','{33045}>{$AWS.ECS.CLUSTER.CPU.UTIL.WARN}','AWS ECS Serverless: 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 ECS Serverless: High CPU utilization (over {$AWS.ECS.CLUSTER.CPU.UTIL.WARN}% for 15m)','d8b5d12b4c6b4b2386fe2540dc387fa7',''),
('23314','{33046}>{$AWS.ECS.CLUSTER.MEMORY.UTIL.WARN}','AWS ECS Serverless: High memory utilization','','0','2','The system is running out of free memory.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','AWS ECS Serverless: High memory utilization (over {$AWS.ECS.CLUSTER.MEMORY.UTIL.WARN}% for 15m)','2f0d82467a754fada1ab4f38ce2c2c5b',''),
('23315','length({33047})>0','AWS ECS Serverless: Failed to get metrics data','','0','2','Failed to get CloudWatch metrics for ECS Cluster.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','91ce423ddff44f0b8364e6d6470b15c5',''),
('23320','{33053} >= {$GCE.RAM.UTIL.MAX}','GCP Compute Engine Instance: High memory utilization','','0','3','RAM utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','','0','GCP Compute Engine Instance: High memory utilization (over {$GCE.RAM.UTIL.MAX}% for 15m)','fa918889bcb84d3886254f00f0df288c',''),
('23321','{33054} >= ({$OPENSTACK.NOVA.INSTANCES.UTIL.WARN} / 100 * {33055})','OpenStack Nova: Current instances count is high','','0','2','Current instances count has exceeded {$OPENSTACK.NOVA.INSTANCES.UTIL.WARN}% of the max available instances count.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}, MAX: {ITEM.LASTVALUE2}','0','OpenStack Nova: Current instances count is high (used >= {$OPENSTACK.NOVA.INSTANCES.UTIL.WARN}%)','3dbae725014d4f289e20f002f2674dc7',''),
('23322','{33056} >= ({$OPENSTACK.NOVA.INSTANCES.UTIL.HIGH} / 100 * {33057})','OpenStack Nova: Current instances count is too high','','0','4','Current instances count has exceeded {$OPENSTACK.NOVA.INSTANCES.UTIL.HIGH}% of the max available instances count.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}, MAX: {ITEM.LASTVALUE2}','0','OpenStack Nova: Current instances count is too high (used >= {$OPENSTACK.NOVA.INSTANCES.UTIL.HIGH}%)','22592fabc09d416598fb4fb806048040',''),
('23323','{33058} >= ({$OPENSTACK.NOVA.RAM.UTIL.WARN} / 100 * {33059})','OpenStack Nova: Current RAM usage is high','','0','2','Current RAM usage has exceeded {$OPENSTACK.NOVA.RAM.UTIL.WARN}% of the max available RAM usage.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}, MAX: {ITEM.LASTVALUE2}','0','OpenStack Nova: Current RAM usage is high (used >= {$OPENSTACK.NOVA.RAM.UTIL.WARN}%)','c9d9eca4b3e540f491210b5c2312e1ba',''),
('23324','{33060} >= ({$OPENSTACK.NOVA.RAM.UTIL.HIGH} / 100 * {33061})','OpenStack Nova: Current RAM usage is too high','','0','4','Current RAM usage has exceeded {$OPENSTACK.NOVA.RAM.UTIL.HIGH}% of the max available RAM usage.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}, MAX: {ITEM.LASTVALUE2}','0','OpenStack Nova: Current RAM usage is too high (used >= {$OPENSTACK.NOVA.RAM.UTIL.HIGH}%)','9dfd643fb555419c9c3200a07cc7647e',''),
('23325','{33062} >= ({$OPENSTACK.NOVA.CPU.UTIL.WARN} / 100 * {33063})','OpenStack Nova: Current vCPU usage is high','','0','2','Current vCPU usage has exceeded {$OPENSTACK.NOVA.CPU.UTIL.WARN}% of the max available vCPU usage.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}, MAX: {ITEM.LASTVALUE2}','0','OpenStack Nova: Current vCPU usage is high (used >= {$OPENSTACK.NOVA.CPU.UTIL.WARN}%)','85b1a132602344e39a50ef10b29fca15',''),
('23326','{33064} >= ({$OPENSTACK.NOVA.CPU.UTIL.HIGH} / 100 * {33065})','OpenStack Nova: Current vCPU usage is too high','','0','4','Current vCPU usage has exceeded {$OPENSTACK.NOVA.CPU.UTIL.HIGH}% of the max available vCPU usage.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}, MAX: {ITEM.LASTVALUE2}','0','OpenStack Nova: Current vCPU usage is too high (used >= {$OPENSTACK.NOVA.CPU.UTIL.HIGH}%)','e62a7fb598b34a0cb5bee6bc0370f7dd',''),
('23335','{33078} > 18000000','PostgreSQL: Oldest xid is too big','','0','3','',NULL,'0','0','0','','0','','0','','0','','4d32971898d441fb94d5f029649dddfa',''),
('23336','{33079}=0','PostgreSQL: Service is down','','0','4','Last test of a connection was unsuccessful.',NULL,'0','0','0','','0','','0','','0','','758e569b51954fcf82c7cb3fa391c882',''),
('23337','{33080} < 10m','PostgreSQL: Service has been restarted','','0','3','PostgreSQL uptime is less than 10 minutes.',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Service has been restarted (uptime < 10m)','22077f0b0ee54becb43ef9ab808c3e43',''),
('23338','{33081} > {$PG.CONN_TOTAL_PCT.MAX.WARN}','PostgreSQL: Total number of connections is too high','','0','3','Total number of current connections exceeds the limit of {$PG.CONN_TOTAL_PCT.MAX.WARN}% out of the maximum number of concurrent connections to the database server (the "max_connections" setting).',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Total number of connections is too high (over {$PG.CONN_TOTAL_PCT.MAX.WARN}% in 5m)','3b6662191c3b46ac930af02797a7162b',''),
('23342','length({33085})>0','Cisco SD-WAN: Authentication has failed','','0','3','',NULL,'0','0','0','','0','','0','','0','','9f98b660a10a4891910b0e3b42f90403',''),
('23343','length({33086})>0','Cisco SD-WAN: There are errors in the \'Get devices\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','9cfcfbb6b6264c19a831a71cc47483a9',''),
('23344','{33087}=1','Cisco SD-WAN: Device certificate is invalid','','0','2','',NULL,'0','0','0','','0','','0','','0','','8a35b69998bd4819b3f9677fd4367d59',''),
('23345','{33088}>{$SDWAN.CPU.UTIL.CRIT}','Cisco SD-WAN: 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','Cisco SD-WAN: High CPU utilization (over {$SDWAN.CPU.UTIL.CRIT}% for 5m)','58cedf1e3f2e42a8a58d270ca0c385a8',''),
('23346','{33089}<>{33090} and length({33091})>0','Cisco SD-WAN: System name has changed','','0','1','System name has changed. Ack to close.',NULL,'0','0','0','','0','','1','','0','Cisco SD-WAN: System name has changed (new name: {ITEM.VALUE})','8658639567ed4eb5964b4543c5b3debe',''),
('23347','{33092}>{$SDWAN.MEMORY.UTIL.MAX}','Cisco SD-WAN: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Cisco SD-WAN: High memory utilization (>{$SDWAN.MEMORY.UTIL.MAX}% for 5m)','0f30b8dc5ebc44ea98a860b159501f99',''),
('23348','{33093}<>{33094} and length({33095})>0','Cisco SD-WAN: Operating system description has changed','','0','1','Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.',NULL,'0','0','0','','0','','1','','0','','b2c78cb56f7f40cfa8844f3f51293538',''),
('23349','{33096}<>0','Cisco SD-WAN: Device is not reachable','','0','2','Device is not reachable to the vManager and/or the entire network.',NULL,'0','0','0','','0','','0','Current status: {ITEM.LASTVALUE1}','0','','d35babbd678f44c3a570fc9a896c58dc',''),
('23350','{33097}<>{33098} and length({33099})>0','Cisco SD-WAN: 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 SD-WAN: Device has been replaced (new serial number received)','a6ad77fe04684d1fa90fac2164519b31',''),
('23351','{33100}<10m','Cisco SD-WAN: Device has been restarted','','0','1','The host uptime is less than 10 minutes',NULL,'0','0','0','','0','','1','','0','Cisco SD-WAN: {HOST.NAME} has been restarted (uptime < 10m)','08ac00695a6c4e2a80dc9cb16d85de43',''),
('23352','length({33101})>0','Cisco SD-WAN: There are errors in the \'Get device data\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','7e9b6cee9ddd47428d01d1a8cadb28fc',''),
('23353','length({33102})>0','Cisco SD-WAN: There are errors in the \'Get interfaces data\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','03772a571b5c417297b11a612b48cb81',''),
('23354','length({33103})>0','Cisco SD-WAN: There are errors in the \'Get routes data\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','edb75d50551643c999da9e93efd0ff1b',''),
('23355','{33104}<>0 and length({33105})>0','Cisco SD-WAN: Device state is not green','','0','3','The device current state is not green.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}, Reason: {ITEM.LASTVALUE2}','0','','fe3886ed10b94fd6b7cd99cba20809a4',''),
('23356','{33106}<{$SDWAN.MEMORY.AVAILABLE.MIN} and {33107}>0','Cisco SD-WAN: Lack of available memory','','0','3','',NULL,'0','0','0','','0','','0','Available: {ITEM.LASTVALUE1}, total: {ITEM.LASTVALUE2}','0','Cisco SD-WAN: Lack of available memory (<{$SDWAN.MEMORY.AVAILABLE.MIN} of {ITEM.VALUE2})','9e558d5397e34468bd845f3e3f0442ec',''),
('23357','{33108}/{33109}>{$SDWAN.LA.PER.CPU.MAX.WARN}\r\nand {33110}>0\r\nand {33111}>0','Cisco SD-WAN: Load average is too high','','0','3','The load average per CPU is too high. The system might 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','Cisco SD-WAN: Load average is too high (per CPU load over {$SDWAN.LA.PER.CPU.MAX.WARN} for 5m)','f37b627ac23c411d935d08c1f6dafde9',''),
('23364','{33132}=0','HashiCorp Nomad: Client nodes API connection has failed','','0','3','Client nodes API connection has failed.\r\nEnsure that Nomad API URL and the necessary permissions have been defined correctly, check the service state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad: Client nodes API connection has failed. HTTP response code: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+(\\d{3})", \\1")}. Response message: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+\\d{3}\\s+(.*)", \\1")}','f2e1cbbf808946ca902c1f378747e936',''),
('23365','{33133}=0','HashiCorp Nomad: Server-related API connection has failed','','0','3','Server-related API connection has failed.\r\nEnsure that Nomad API URL and the necessary permissions have been defined correctly, check the service state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad: Server-related API connection has failed. HTTP response code: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+(\\d{3})", \\1")}. Response message: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+\\d{3}\\s+(.*)", \\1")}','1560c32cb7de4fc8a58cf537c7958205',''),
('23366','{33134} = 0','HashiCorp Nomad Client: Service [rpc] is down','','0','3','Cannot establish the connection to [rpc] service port {$NOMAD.CLIENT.RPC.PORT}.\r\nCheck the Nomad state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','Service: rpc, Port: {$NOMAD.CLIENT.RPC.PORT}, State: {ITEM.LASTVALUE}','0','','f368ff4de45e4620963135836eb54092',''),
('23367','{33135} = 0','HashiCorp Nomad Client: Service [serf] is down','','0','3','Cannot establish the connection to [serf] service port {$NOMAD.CLIENT.SERF.PORT}.\r\nCheck the Nomad state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','Service: serf, Port: {$NOMAD.CLIENT.SERF.PORT}, State: {ITEM.LASTVALUE}','0','','0108c9f85b48433c8b9864e41458994f',''),
('23368','{33136} > 0','HashiCorp Nomad Client: OOM killed allocations found','','0','2','OOM killed allocations found.',NULL,'0','0','0','','0','','1','OOM killed: {ITEM.LASTVALUE}','0','','747de32c46cb4d95851cee8a30c576b0',''),
('23369','{33137} >= {$NOMAD.CPU.UTIL.MIN}','HashiCorp Nomad Client: High CPU utilization','','0','3','CPU utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','HashiCorp Nomad Client: High CPU utilization: (over >= {$NOMAD.CPU.UTIL.MIN}% over last 10m)','59db4f1d22cb48fab0ced8ad9ec39a25',''),
('23370','{33138}=0','HashiCorp Nomad Client: Monitoring API connection has failed','','0','3','Monitoring API connection has failed.\r\nEnsure that Nomad API URL and the necessary permissions have been defined correctly, check the service state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad Client: Monitoring API connection has failed. HTTP response code: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+(\\d{3})", \\1")}. Response message: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+\\d{3}\\s+(.*)", \\1")}','676e1535cde2424cbda78f18cd9084bf',''),
('23371','{33139}=0','HashiCorp Nomad Client: Allocations API connection has failed','','0','3','Allocations API connection has failed.\r\nEnsure that Nomad API URL and the necessary permissions have been defined correctly, check the service state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad Client: Allocations API connection has failed. HTTP response code: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+(\\d{3})", \\1")}. Response message: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+\\d{3}\\s+(.*)", \\1")}','300f5fba0f45465aa6868a3f1d16633d',''),
('23372','{33140}=0','HashiCorp Nomad Client: Nodes API connection has failed','','0','3','Nodes API connection has failed.\r\nEnsure that Nomad API URL and the necessary permissions have been defined correctly, check the service state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad Client: Nodes API connection has failed. HTTP response code: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+(\\d{3})", \\1")}. Response message: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+\\d{3}\\s+(.*)", \\1")}','3ea14e12d6154492a4505c4b51003ed3',''),
('23373','{33141} < 10m','HashiCorp Nomad Client: The host has been restarted','','0','2','The host uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad Client: The host has been restarted: (uptime < 10m)','74fe77871e8c4161b5944f30dd4d1c84',''),
('23374','{33142}<>0','HashiCorp Nomad Client: Nomad client version has changed','','0','1','Nomad client version has changed.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad Client: Nomad client version has changed to {ITEM.LASTVALUE}','afac97bced6f49bc994ae633b662722c',''),
('23375','{33143} = 0','HashiCorp Nomad Server: Service [rpc] is down','','0','3','Cannot establish the connection to [rpc] service port {$NOMAD.SERVER.RPC.PORT}.\r\nCheck the Nomad state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','Service: rpc, Port: {$NOMAD.SERVER.RPC.PORT}, State: {ITEM.LASTVALUE}','0','','0b534fa4c6cd4e89bd0a44ca8e810fa2',''),
('23376','{33144} = 0','HashiCorp Nomad Server: Service [serf] is down','','0','3','Cannot establish the connection to [serf] service port {$NOMAD.SERVER.SERF.PORT}.\r\nCheck the Nomad state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','Service: serf, Port: {$NOMAD.SERVER.SERF.PORT}, State: {ITEM.LASTVALUE}','0','','00799e8927b547308fc9caab4ba2d24d',''),
('23377','{33145} < {$NOMAD.REDUNDANCY.MIN} and {33146} = 0','HashiCorp Nomad Server: Autopilot redundancy is low','','0','2','The autopilot redundancy is low.\r\nCluster crash risk is high due to one more server failure.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad Server: Autopilot redundancy is low (less than {$NOMAD.REDUNDANCY.MIN})','fbb6d007481a4aab8d107a1d25a8c7ad',''),
('23378','{33147} = 0 and {33148} = 0','HashiCorp Nomad Server: Autopilot is unhealthy','','0','3','The autopilot is in unhealthy state. The successful failover probability is extremely low.',NULL,'0','0','0','','0','','1','','0','','73c14eec055e47c6af6d8728ba0fb416',''),
('23379','{33149}=0','HashiCorp Nomad Server: Monitoring API connection has failed','','0','3','Monitoring API connection has failed.\r\nEnsure that Nomad API URL and the necessary permissions have been defined correctly, check the service state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad Server: Monitoring API connection has failed. HTTP response code: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+(\\d{3})", \\1")}. Response message: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+\\d{3}\\s+(.*)", \\1")}','9dc8cd0bcbad4ee7a2afe45e33db53a7',''),
('23380','{33150} > 0 and {33151} = 0','HashiCorp Nomad Server: Dead jobs found','','0','2','Jobs with the `Dead` state discovered.\r\nCheck the {$NOMAD.SERVER.API.SCHEME}://{HOST.IP}:{$NOMAD.SERVER.API.PORT}/v1/jobs URL for the details.',NULL,'0','0','0','','0','','1','Current amount: {ITEM.LASTVALUE}','0','','44dcd52ebf54404e871501a4c4825424',''),
('23381','{33152} <> 0','HashiCorp Nomad Server: Cluster role has changed','','0','1','Cluster role has changed.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad Server: Cluster role has changed to {ITEM.LASTVALUE}','1bc6ee807acd4532a58b4527f8865c1c',''),
('23382','{33153} >= {$NOMAD.SERVER.LEADER.LATENCY} and {33154} = 0','HashiCorp Nomad Server: Leader last contact timeout exceeded','','0','2','The nomad.raft.leader.lastContact metric is a general indicator of Raft latency which can be used to observe how Raft timing is performing and guide infrastructure provisioning.\r\nIf this number trends upwards, look at CPU, disk IOPs, and network latency. nomad.raft.leader.lastContact should not get too close to the leader lease timeout of 500ms.',NULL,'0','0','0','','0','','0','','0','HashiCorp Nomad Server: Leader last contact timeout exceeded: over {$NOMAD.SERVER.LEADER.LATENCY} for the last 5 minutes','65c69469e9354e81a632485a74bc711d',''),
('23383','{33155}=0','HashiCorp Nomad Server: Internal stats API connection has failed','','0','3','Internal stats API connection has failed.\r\nEnsure that Nomad API URL and the necessary permissions have been defined correctly, check the service state and network connectivity between Nomad and Zabbix.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad Server: Internal stats API connection has failed. HTTP response code: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+(\\d{3})", \\1")}. Response message: {{ITEM.VALUE}.regsub("HTTP\\/[\\d.]+\\s+\\d{3}\\s+(.*)", \\1")}','b60dd78bd2d24c22afec63a8b420bcd6',''),
('23384','{33156}<>0','HashiCorp Nomad Server: Nomad server version has changed','','0','1','Nomad server version has changed.',NULL,'0','0','0','','0','','1','','0','HashiCorp Nomad Server: Nomad server version has changed to {ITEM.LASTVALUE}','3c7dfd5ec21144b6b58c603d60142200',''),
('23385','({33157} / {33158})*100 <= {$NOMAD.RAM.AVAIL.MIN}','HashiCorp Nomad Client: High memory utilization','','0','3','RAM utilization is too high. The system might be slow to respond.',NULL,'0','0','0','','0','','0','RAM available: {ITEM.LASTVALUE1}, RAM total: {ITEM.LASTVALUE2}','0','HashiCorp Nomad Client: High memory utilization: (available < {$NOMAD.RAM.AVAIL.MIN}% over last 10m)','d41ae1c102d84eab9629565bcc9b51df',''),
('23386','{33159}/{33160}*100>{$NOMAD.OPEN.FDS.MAX}','HashiCorp Nomad Server: Current number of open files is too high','','0','2','Heavy file descriptor usage (i.e., near the process file descriptor limit) indicates a potential file descriptor exhaustion issue.',NULL,'0','0','0','','0','','0','','0','HashiCorp Nomad Server: Current number of open files is too high (over {$NOMAD.OPEN.FDS.MAX}% for 5m)','9b6d779864144e4e9e5e9924658d763e',''),
('23393','{33168}>{$ZABBIX.PROXY.UTIL.MAX:"snmp poller"}','Zabbix proxy: Utilization of snmp poller processes is high','','0','3','Indicates potential performance issues with the snmp poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33168}<{$ZABBIX.PROXY.UTIL.MIN:"snmp poller"}','0','','0','','0','Zabbix proxy: Utilization of snmp poller processes over {$ZABBIX.PROXY.UTIL.MAX:"snmp poller"}%','811e08cb2382482db4054a4665e328d7',''),
('23394','{33169}>{$ZABBIX.PROXY.UTIL.MAX:"snmp poller"}','Zabbix proxy: Utilization of snmp poller processes is high','','0','3','Indicates potential performance issues with the snmp poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33169}<{$ZABBIX.PROXY.UTIL.MIN:"snmp poller"}','0','','0','','0','Zabbix proxy: Utilization of snmp poller processes over {$ZABBIX.PROXY.UTIL.MAX:"snmp poller"}%','e9c89574068443f89c369df8618506e6',''),
('23395','{33798}>{$ZABBIX.SERVER.UTIL.MAX:"snmp poller"}','Zabbix server: Utilization of snmp poller processes is high','','0','3','Indicates potential performance issues with the snmp poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33798}<{$ZABBIX.SERVER.UTIL.MIN:"snmp poller"}','0','','0','','0','Zabbix server: Utilization of snmp poller processes over {$ZABBIX.SERVER.UTIL.MAX:"snmp poller"}%','3fab1765b54b4036a03ca1fb69763e81',''),
('23397','{33912}>{$ZABBIX.SERVER.UTIL.MAX:"snmp poller"}','Zabbix server: Utilization of snmp poller processes is high','','0','3','Indicates potential performance issues with the snmp poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33912}<{$ZABBIX.SERVER.UTIL.MIN:"snmp poller"}','0','','0','','0','Zabbix server: Utilization of snmp poller processes over {$ZABBIX.SERVER.UTIL.MAX:"snmp poller"}%','18407657b6a647e292a3625180ccb313',''),
('23414','{33195}<>0','Nextcloud: Number of installed apps has been changed','','0','1','Applications have been installed or removed.',NULL,'0','0','0','','0','','1','','0','','b0375ab303e74e7cadd911a4a2e98725',''),
('23415','{33196}<>0','Nextcloud: Application updates are available','','0','2','Updates are available for some of the installed applications.',NULL,'0','0','0','','0','','1','','0','','180c82d98b694f27bc44d1fc20ccd06e',''),
('23416','{33197} > {$NEXTCLOUD.CPU.LOAD.MAX}','Nextcloud: CPU load is too high','','0','3','High CPU load.',NULL,'0','0','0','','0','','0','','0','Nextcloud: CPU load is too high (over {$NEXTCLOUD.CPU.LOAD.MAX} for 5m)','481edcbc45174b35a2d44003aa101817',''),
('23417','{33198}=1 and length({33199})>0','Nextcloud: Database version has changed','','0','1','The Database version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Nextcloud: Database version has changed (new version: {ITEM.VALUE})','d59f8e583cc34c578946607433d254ca',''),
('23418','{33200}<{$NEXTCLOUD.STORAGE.FREE.MIN}','Nextcloud: Disk space is low','','0','3','Condition should be the following:\r\n- the disk free space is less than `{$NEXTCLOUD.STORAGE.FREE.MIN}`;',NULL,'0','0','0','','0','','1','','0','Nextcloud: Disk space is low (free < {$NEXTCLOUD.STORAGE.FREE.MIN})','6d9d52db83e34d83891cc3bb449d59b2',''),
('23419','{33201} > {$NEXTCLOUD.MEM.PUSED.MAX}','Nextcloud: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Nextcloud: High memory utilization (>{$NEXTCLOUD.MEM.PUSED.MAX}% for 5m)','b1f8786b975c443bac5daf351c29cde5',''),
('23420','{33202} > {$NEXTCLOUD.PHP.MEM.PUSED.MAX}','Nextcloud: High PHP memory utilization','','0','3','The PHP is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Nextcloud: High PHP memory utilization (>{$NEXTCLOUD.PHP.MEM.PUSED.MAX}% for 5m)','ee778919cf91495da4445974afa039e9',''),
('23421','{33203}=1 and length({33204})>0','Nextcloud: PHP version has changed','','0','1','The PHP version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Nextcloud: PHP version has changed (new version: {ITEM.VALUE})','ff6e12cb84bb494a9ffc692b28862a25',''),
('23422','{33205}<>"OK"','Nextcloud: Server information unavailable','','0','4','Failed to get server information.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE}','0','','b44c435b48264626ae2ec5cb610edac9',''),
('23423','{33206} > {$NEXTCLOUD.SWAP.PUSED.MAX}','Nextcloud: High swap utilization','','0','3','The system is running out of free swap.',NULL,'0','0','0','','0','','0','','0','Nextcloud: High swap utilization (>{$NEXTCLOUD.SWAP.PUSED.MAX}% for 5m)','da09c1862385450196651573aec00178',''),
('23424','{33207}=1 and length({33208})>0','Nextcloud: Version has changed','','0','1','Nextcloud version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Nextcloud: Version has changed (new version: {ITEM.VALUE})','e66591237ce643b0971e69b18a88a7cc',''),
('23429','{33213}<>{33214} and length({33215})>0','PostgreSQL: Version has changed','','0','1','',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Version has changed (new version value received: {ITEM.VALUE})','6b3ac2a19e114e1390e6e0793728f576',''),
('23430','{33216}<>{33217} and length({33218})>0','PostgreSQL: Version has changed','','0','1','',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Version has changed (new version value received: {ITEM.VALUE})','fd409b64f83943edaf43845a12bf8ace',''),
('23431','{33219}=0','FortiGate: Unexpected response from API','','0','3','Received an unexpected response from API. It may be unavailable.',NULL,'0','0','0','','0','','0','','0','','8b8c03f1497f4f18a417d103267d2947',''),
('23432','{33220}>{$CPU.UTIL.WARN}','FortiGate: CPU utilization is high','','0','2','The CPU utilization is high.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','FortiGate: High CPU utilization (over {$CPU.UTIL.WARN}% for 5m)','4698d35fa5e242ef828ac4e3dba5bc09',''),
('23433','{33221}>{$CPU.UTIL.CRIT}','FortiGate: CPU utilization is too high','','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','FortiGate: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','170087cd8ebf4fc29093e5c1dbd86fea',''),
('23434','{$FIRMWARE.UPDATES.CONTROL}=1 and {33222}>0','FortiGate: New available firmware found','','0','1','New available firmware versions found to download.\r\n\r\nThis trigger expression works as follows:\r\n1. It can be triggered if there are one or more available firmware versions.\r\n2. `{$FIRMWARE.UPDATES.CONTROL}=1` - a user can redefine context macro to value - 0. That marks this notification as not important. No new trigger will be fired if new firmware is found.',NULL,'0','0','0','','0','','1','','0','','da4a8352ffb94c15a62523a0b97460c4',''),
('23435','{33223}<>{33224} and\r\nlength({33225})>0','FortiGate: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','FortiGate: Device has been replaced (new serial number received)','1426177b905e442fb2cdd963e8e8bba1',''),
('23436','length({33226})>0 and length({33227})>0 and {33228}=0','FortiGate: There are errors in the \'Get firmware info\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','c4ab39fa9c104eaa8f9c5da529e416d8',''),
('23437','(100-{33229})<{$DISK.FREE.WARN}','FortiGate: Free disk space is low','','0','2','Left disk space is not enough.',NULL,'0','0','0','','0','','0','','0','FortiGate: Free disk space is less than {$DISK.FREE.WARN}%','649a5e3ba39e4e799835cdba8bba8d34',''),
('23438','(100-{33230})<{$DISK.FREE.CRIT}','FortiGate: Free disk space is too low','','0','4','Left disk space is too low.',NULL,'0','0','0','','0','','0','','0','FortiGate: Free disk space is less than {$DISK.FREE.CRIT}%','33c78beb669142baa66befba2456d810',''),
('23439','length({33231})>0 and length({33232})>0 and {33233}=0','FortiGate: There are errors in the \'Get firewall policies data\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','a6f52f84c66c4d9b9831be03afc725b5',''),
('23440','{33234}>{$MEMORY.UTIL.WARN}','FortiGate: Memory utilization is high','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','FortiGate: High memory utilization (>{$MEMORY.UTIL.WARN}% for 5m)','0f0b467715bb420a80cae7a7df50177d',''),
('23441','{33235}>{$MEMORY.UTIL.CRIT}','FortiGate: Memory utilization is too high','','0','4','Free memory size is too low.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','FortiGate: High memory utilization (>{$MEMORY.UTIL.CRIT}% for 5m)','4cd6cb4e21154f8489de2ba73f32e62d',''),
('23442','{33236}<>{33237} and length({33238})>0','FortiGate: 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','FortiGate: System name has changed (new name: {ITEM.VALUE})','a522d2cdd55947fabf1c152f6f6dd374',''),
('23443','length({33239})>0 and length({33240})>0 and {33241}=0','FortiGate: There are errors in the \'Get interfaces data\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','20b8b33c1a36452ca280da95b8247409',''),
('23444','length({33242})>0 and length({33243})>0 and {33244}=0','FortiGate: There are errors in the \'Get resources data\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','e6ed25293ca64de1ae01e2ab6c92f5c7',''),
('23445','length({33245})>0 and length({33246})>0 and {33247}=0','FortiGate: There are errors in the \'Get SD-WAN data\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','b2ec3a4cf468449388a33f76688dc259',''),
('23446','length({33248})>0 and length({33249})>0 and {33250}=0','FortiGate: There are errors in the \'Get service licenses\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','eeb819b2813f488ea3792a029f25a08d',''),
('23447','length({33251})>0 and length({33252})>0 and {33253}=0','FortiGate: There are errors in the \'Get system info\' metric','','0','2','',NULL,'0','0','0','','0','','0','','0','','3d1dbc0964db401fa9c10c1b126349e4',''),
('23448','{33254}<10m','FortiGate: Device has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','FortiGate: {HOST.NAME} has been restarted (uptime < 10m)','183385fa495442bcbd3eb28636ca5bb9',''),
('23449','{33255}=0','FortiGate: Port {$FGATE.API.PORT} is unavailable','','0','3','',NULL,'0','0','0','','0','','1','','0','','26abf8698af247d09c325ab1cb3e9903',''),
('23460','{33280}=0','FortiGate: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','a25a713c59ec44689831c2c636757603',''),
('23461','{33281}>{$ICMP_LOSS_WARN} and {33281}<100','FortiGate: High ICMP ping loss','','0','2','ICMP ping loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','d1106ac3337548bda97fb89ce36c5ee5',''),
('23462','{33282}>{$ICMP_RESPONSE_TIME_WARN}','FortiGate: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','e04a8517551740d8b47a5dfc88dfe779',''),
('23463','{33283}>{$CPU.UTIL.CRIT}','FortiGate: 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','FortiGate: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','86f157c9a85448cbac41ab5f8ee3d668',''),
('23464','{33284}<>{33285} and\r\nlength({33286})>0','FortiGate: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','FortiGate: Device has been replaced (new serial number received)','0aa10f525bbb4bcd91debdb2f8b3afea',''),
('23465','{33287}<>{33288} and length({33289})>0','FortiGate: 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','FortiGate: System name has changed (new name: {ITEM.VALUE})','9db3ed37da594694a560e8a85a3f7aae',''),
('23466','{33290}<10m','FortiGate: Device has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','FortiGate: {HOST.NAME} has been restarted (uptime < 10m)','5c16d6334cea466386455a7c5d071d18',''),
('23467','{33586}<{$DISK.FREE.CRIT}','FortiGate: Free disk space is too low','','0','4','Available disk space is too low.',NULL,'0','0','0','','0','','0','','0','FortiGate: Free disk space is less than {$DISK.FREE.CRIT}%','a323a6c7a5a54ad1bf0db0ec9441bf83',''),
('23468','{33292}>{$MEMORY.UTIL.MAX}','FortiGate: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','FortiGate: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','1ee0af9b389d4e5fafc5c08f46c9cc09',''),
('23469','{33293}=0','FortiGate: 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','','e8dfc8ddd1a145ea92ab6446514a0ed5',''),
('23476','{33753}>{$ZABBIX.PROXY.UTIL.MAX:"proxy buffer"}','Zabbix proxy: Excessive proxy memory buffer usage','','0','3','Consider increasing ProxyMemoryBufferSize in the zabbix_proxy.conf configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"proxy buffer"}% used in the proxy memory buffer','9b6cb370c00f4ebda91cdf247adc4780',''),
('23477','{33760}>{$ZABBIX.PROXY.UTIL.MAX:"proxy buffer"}','Zabbix proxy: Excessive proxy memory buffer usage','','0','3','Consider increasing ProxyMemoryBufferSize in the zabbix_proxy.conf configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"proxy buffer"}% used in the proxy memory buffer','4c04e5a21a91485e9562ef951877a5f3',''),
('23482','length({33318})>0','HPE iLO: Failed to get data from API','','0','4','Failed to get data from API. Check the debug log for more information.',NULL,'0','0','0','','0','','0','','0','','b3327a76234b4ac6b049dec49bdd6a78',''),
('23527','length({33398})>0','AWS ELB ALB: Failed to get alarms data','','0','2','Failed to get CloudWatch alarms for Application Load Balancer.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS ELB ALB: Failed to get CloudWatch alarms for Application Load Balancer','3fd832d1a2cc4cff955554cbd8c4b3c7',''),
('23528','{33399}>{$AWS.HTTP.4XX.FAIL.MAX.WARN}','AWS ELB ALB: Too many HTTP 4XX error codes','','0','2','Too many requests failed with HTTP 4XX code.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS ELB ALB: Too many HTTP 4XX error codes (over {$AWS.HTTP.4XX.FAIL.MAX.WARN} for 5m)','922bd3ab505b420984c93dfdfc417a56',''),
('23529','{33400}>{$AWS.HTTP.5XX.FAIL.MAX.WARN}','AWS ELB ALB: Too many HTTP 5XX error codes','','0','2','Too many requests failed with HTTP 5XX code.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS ELB ALB: Too many HTTP 5XX error codes (over {$AWS.HTTP.5XX.FAIL.MAX.WARN} for 5m)','883fc396e7da4806943cd70688c057a3',''),
('23530','length({33401})>0','AWS ELB ALB: Failed to get metrics data','','0','2','Failed to get CloudWatch metrics for Application Load Balancer.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS ELB ALB: Failed to get CloudWatch metrics for Application Load Balancer','70282eb6c0c442f9a4f4c49b10f54a4d',''),
('23533','{33405}>{$MSSQL.AVERAGE_WAIT_TIME.MAX}','MSSQL: Total average wait time for locks is high','','0','2','An average wait time longer than 500 ms may indicate excessive blocking. This value should generally correlate to "Lock Waits/sec" and move up or down with it accordingly.',NULL,'0','0','0','','0','','0','','0','MSSQL: Total average wait time for locks is high (over {$MSSQL.AVERAGE_WAIT_TIME.MAX}ms for 5m)','7d284dc23d4649c79bf67e13f1edc83b',''),
('23534','{33406}<{$MSSQL.BUFFER_CACHE_RATIO.MIN.CRIT}','MSSQL: Percentage of the buffer cache efficiency is low','','0','4','Too low buffer cache hit ratio.',NULL,'0','0','0','','0','','0','','0','MSSQL: Percentage of the buffer cache efficiency is low (below {$MSSQL.BUFFER_CACHE_RATIO.MIN.CRIT}% for 5m)','9ee2397e2560447eb01d4d50cde5fa9d',''),
('23535','{33407}<{$MSSQL.BUFFER_CACHE_RATIO.MIN.WARN}','MSSQL: Percentage of the buffer cache efficiency is low','','0','2','Low buffer cache hit ratio.',NULL,'0','0','0','','0','','0','','0','MSSQL: Percentage of the buffer cache efficiency is low (below {$MSSQL.BUFFER_CACHE_RATIO.MIN.WARN}% for 5m)','c22ac1cbc5224eb98fde9f87c52a3724',''),
('23536','{33408}>{$MSSQL.FREE_LIST_STALLS.MAX}','MSSQL: Number of rps waiting for a free page is high','','0','2','Some requests have to wait for a free page.',NULL,'0','0','0','','0','','0','','0','MSSQL: Number of rps waiting for a free page is high (over {$MSSQL.FREE_LIST_STALLS.MAX} for 5m)','5cf3182a47694569b9d75822404b77f7',''),
('23537','{33409}>{$MSSQL.LAZY_WRITES.MAX}','MSSQL: Number of buffers written per second by the lazy writer is high','','0','2','The number of buffers written per second by the buffer manager\'s lazy writer exceeds the threshold.',NULL,'0','0','0','','0','','0','','0','MSSQL: Number of buffers written per second by the lazy writer is high (over {$MSSQL.LAZY_WRITES.MAX} for 5m)','96698537fee846199197a25beecaafca',''),
('23538','{33410}>{$MSSQL.LOCK_REQUESTS.MAX}','MSSQL: Total number of locks per second is high','','0','2','Number of new locks and lock conversions per second requested from the lock manager is high.',NULL,'0','0','0','','0','','0','','0','MSSQL: Total number of locks per second is high (over {$MSSQL.LOCK_REQUESTS.MAX} for 5m)','19137e1b06fe4f1eaf5e76c5ae47d29d',''),
('23539','{33411}>{$MSSQL.LOCK_TIMEOUTS.MAX}','MSSQL: Total lock requests per second that timed out is high','','0','2','The total number of timed out lock requests per second, including requests for NOWAIT locks, is high.',NULL,'0','0','0','','0','','0','','0','MSSQL: Total lock requests per second that timed out is high (over {$MSSQL.LOCK_TIMEOUTS.MAX} for 5m)','a7313fad35804feeaddf544acb2a0d26',''),
('23540','{33412}>0','MSSQL: Some blocking is occurring for 5m','','0','3','Values greater than zero indicate at least some blocking is occurring, while a value of zero can quickly eliminate blocking as a potential root-cause problem.',NULL,'0','0','0','','0','','0','','0','','c4fb968a66784746a11feee64a8f98e8',''),
('23541','{33413}>{$MSSQL.DEADLOCKS.MAX}','MSSQL: Number of deadlocks is high','','0','3','Too many deadlocks are occurring currently.',NULL,'0','0','0','','0','','0','','0','MSSQL: Number of deadlocks is high (over {$MSSQL.DEADLOCKS.MAX} for 5m)','f0b039f08b694db1bbafe6b3d8d4e9ab',''),
('23542','{33414}<{$MSSQL.PAGE_LIFE_EXPECTANCY.MIN}','MSSQL: Page life expectancy is low','','0','4','The page stays in the buffer pool without references for less time than the threshold value.',NULL,'0','0','0','','0','','0','','0','MSSQL: Page life expectancy is low (less {$MSSQL.PAGE_LIFE_EXPECTANCY.MIN}min for 15m)','e47d0eeac246490cbeedb8ba1cf77e94',''),
('23543','{33415}>{$MSSQL.PAGE_READS.MAX}','MSSQL: Number of physical database page reads per second is high','','0','2','The physical database page reads are issued too frequently.',NULL,'0','0','0','','0','','0','','0','MSSQL: Number of physical database page reads per second is high (over {$MSSQL.PAGE_READS.MAX} for 5m)','5050b7c4e5a4445d9c4aae031b01115b',''),
('23544','{33416}>{$MSSQL.PAGE_WRITES.MAX}','MSSQL: Number of physical database page writes per second is high','','0','2','The physical database page writes are issued too frequently.',NULL,'0','0','0','','0','','0','','0','MSSQL: Number of physical database page writes per second is high (over {$MSSQL.PAGE_WRITES.MAX} for 5m)','48e32bec13d34ad88db7c9cc98d86a3b',''),
('23545','{33417} > {$MSSQL.PERCENT_COMPILATIONS.MAX}','MSSQL: Percent of ad hoc queries running is high','','0','2','The lower this value is, the better. High values often indicate excessive ad hoc querying and should be as low as possible. If excessive ad hoc querying is happening, try rewriting the queries as procedures or invoke the queries using `sp_executeSQL`. When rewriting isn\'t possible, consider using a plan guide or setting the database to parameterization forced mode.',NULL,'0','0','0','','0','','0','','0','MSSQL: Percent of ad hoc queries running is over {$MSSQL.PERCENT_COMPILATIONS.MAX}% for 15m','cf0649863fe5421aa1dc279d1ca7e360',''),
('23546','{33418} > {$MSSQL.PERCENT_RECOMPILATIONS.MAX}','MSSQL: Percent of times statement recompiles is high','','0','2','This number should be at or near zero, since recompiles can cause deadlocks and exclusive compile locks. This counter\'s value should follow in proportion to "Batch Requests/sec" and "SQL Compilations/sec".',NULL,'0','0','0','','0','','0','','0','MSSQL: Percent of times statement recompiles is over {$MSSQL.PERCENT_RECOMPILATIONS.MAX}% for 15m','1218fe12f4d542d99d997ede6cc30813',''),
('23547','{33419} > 0.001','MSSQL: Number of index and table scans exceeds index searches in the last 15m','','0','2','Index searches are preferable to index and table scans. For OLTP applications, optimize for more index searches and less scans (preferably, 1 full scan for every 1000 index searches). Index and table scans are expensive I/O operations.',NULL,'0','0','0','','0','','0','','0','','378cdaf994ea4167b7727996357d7564',''),
('23548','{33420}=1','MSSQL: Failed to fetch info data','','0','1','Zabbix has not received any data for items for the last 30 minutes.',NULL,'0','0','0','','0','','0','','0','MSSQL: Failed to fetch info data (or no data for 30m)','b64d08b9212645cd8bab9e35a8e29942',''),
('23549','{33421}<10m','MSSQL: Service has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','MSSQL: Service has been restarted (uptime < 10m)','4ab35137c34845c495bc3837ac1f6f9f',''),
('23550','{33422}<>{33423} and length({33424})>0','MSSQL: Version has changed','','0','1','MSSQL version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MSSQL: Version has changed (new version value received: {ITEM.VALUE})','12643eb3af884023ab61802559cde946',''),
('23551','{33425}>{$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)','6d25ee02edc14d7497b339627cc0c680',''),
('23552','{33426}>{$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)','4cd0c8e7089144aeaeb10c4866e89b06',''),
('23553','{33427}<{$MSSQL.WORKTABLES_FROM_CACHE_RATIO.MIN.CRIT}','MSSQL: Percentage of work tables available from the work table cache is low','','0','4','A value less than 90% may indicate insufficient memory, since execution plans are being dropped, or, on 32-bit systems, may indicate the need for an upgrade to a 64-bit system.',NULL,'0','0','0','','0','','0','','0','MSSQL: Percentage of work tables available from the work table cache is low (below {$MSSQL.WORKTABLES_FROM_CACHE_RATIO.MIN.CRIT}% for 5m)','cb3dd51615d447379a3abda929faf881',''),
('23554','{33428}=0','MSSQL: Service is unavailable','','0','5','The TCP port of the MSSQL Server service is currently unavailable.',NULL,'0','0','0','','0','','0','','0','','2ea9eaf463144defbd85340a824f7986',''),
('23555','{33429} * 100 > 10 * {33430}','MSSQL: Too frequently using pointers','','0','2','Rows with VARCHAR columns can experience expansion when VARCHAR values are updated with a longer string. In the case where the row cannot fit in the existing page, the row migrates, and access to the row will traverse a pointer. This only happens on heaps (tables without clustered indexes). In cases where clustered indexes cannot be used, drop non-clustered indexes, build a clustered index to reorg pages and rows, drop the clustered index, then recreate non-clustered indexes.',NULL,'0','0','0','','0','','0','','0','','366fa3cfcba94e038ad77c2f5a2649a2',''),
('23556','{33431} > {$MSSQL.PERCENT_READAHEAD.MAX} / 100 * {33432}','MSSQL: Too many physical reads occurring','','0','2','If this value makes up even a sizeable minority of the total "Page Reads/sec" (say, greater than 20% of the total page reads), you may have too many physical reads occurring.',NULL,'0','0','0','','0','','0','','0','','274773f4bb9d4af798e8922b5054226b',''),
('23589','length({33472}) > 0','YugabyteDB: Failed to fetch data','','0','2','Failed to fetch data about cluster.',NULL,'0','0','0','','0','','0','','0','','add4067f699f401887d259ee35b4d654',''),
('23590','{33473} > {$YUGABYTEDB.CONNECTION.UTILIZATION.WARN}','YugabyteDB Cluster: Average utilization of connections is high','','0','2','YugabyteDB Cluster uses more than {$YUGABYTEDB.CONNECTION.UTILIZATION.WARN}% of the connection limit.',NULL,'0','0','0','','0','','0','Current connections utilization: {ITEM.LASTVALUE1}','0','YugabyteDB Cluster: Average utilization of connections is high (over {$YUGABYTEDB.CONNECTION.UTILIZATION.WARN}% for 5m)','5caf42a5309a4f0f834b6058f4741a44',''),
('23591','{33474} > {$YUGABYTEDB.CONNECTION.UTILIZATION.CRIT}','YugabyteDB Cluster: Average utilization of connections is too high','','0','4','YugabyteDB Cluster uses more than {$YUGABYTEDB.CONNECTION.UTILIZATION.CRIT}% of the connection limit.',NULL,'0','0','0','','0','','0','Current connections utilization: {ITEM.LASTVALUE1}','0','YugabyteDB Cluster: Average utilization of connections is too high (over {$YUGABYTEDB.CONNECTION.UTILIZATION.CRIT}% for 5m)','68d2710963394afe8218178c98e88c62',''),
('23592','{33475} > {$YUGABYTEDB.CPU.UTILIZATION.WARN}','YugabyteDB Cluster: CPU utilization is high','','0','2','YugabyteDB Cluster CPU utilization is more than {$YUGABYTEDB.CPU.UTILIZATION.WARN}%. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','YugabyteDB Cluster: CPU utilization is high (over {$YUGABYTEDB.CPU.UTILIZATION.WARN}% for 5m)','22340ce9ea2e457fa4270498bfc53666',''),
('23593','{33476} > {$YUGABYTEDB.CPU.UTILIZATION.CRIT}','YugabyteDB Cluster: CPU utilization is too high','','0','4','YugabyteDB Cluster CPU utilization is more than {$YUGABYTEDB.CPU.UTILIZATION.CRIT}%. The system might be slow to respond.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','YugabyteDB Cluster: CPU utilization is too high (over {$YUGABYTEDB.CPU.UTILIZATION.CRIT}% for 5m)','ed88478e0a784c8dbbe95c20b08c167e',''),
('23594','{33477} > {$YUGABYTEDB.DISK.UTILIZATION.CRIT}','YugabyteDB Cluster: Storage space is critically low','','0','4','YugabyteDB Cluster uses more than {$YUGABYTEDB.DISK.UTILIZATION.CRIT}% of disk space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','3571704c29e040b198a6e72d7526c98a',''),
('23595','{33478} > {$YUGABYTEDB.DISK.UTILIZATION.WARN}','YugabyteDB Cluster: Storage space is low','','0','2','YugabyteDB Cluster uses more than {$YUGABYTEDB.DISK.UTILIZATION.WARN}% of disk space.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','','21623809368a43b0bdfb127f2fdea22c',''),
('23596','{33479} <> 0','YugabyteDB Cluster: Cluster is not healthy','','0','3','YugabyteDB Cluster is not healthy.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','e111a563fb9947eda48a56ad5ef59891',''),
('23597','{33480} > {$YUGABYTEDB.MEMORY.CLUSTER.UTILIZATION.WARN}','YugabyteDB Cluster: Memory utilization is high','','0','2','YugabyteDB Cluster uses more than {$YUGABYTEDB.MEMORY.CLUSTER.UTILIZATION.WARN}% of memory.',NULL,'0','0','0','','0','','0','Current memory utilization: {ITEM.LASTVALUE1}','0','YugabyteDB Cluster: Memory utilization is high (>{$YUGABYTEDB.MEMORY.CLUSTER.UTILIZATION.WARN} for 5m)','5614204dbeca4b799989a13717824f07',''),
('23598','{33481} > {$YUGABYTEDB.MEMORY.CLUSTER.UTILIZATION.CRIT}','YugabyteDB Cluster: Memory utilization is too high','','0','4','YugabyteDB Cluster uses more than {$YUGABYTEDB.MEMORY.CLUSTER.UTILIZATION.CRIT}% of memory.',NULL,'0','0','0','','0','','0','Current memory utilization: {ITEM.LASTVALUE1}','0','YugabyteDB Cluster: Memory utilization is too high (>{$YUGABYTEDB.MEMORY.CLUSTER.UTILIZATION.CRIT} for 5m)','27a8c6b07e474581be53f5d896387f45',''),
('23599','{33482} <> {33483} and length({33484}) > 0','YugabyteDB Cluster: Cluster software version has changed','','0','1','YugabyteDB Cluster software version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current version: {ITEM.LASTVALUE1}','0','YugabyteDB Cluster: Cluster software version has changed (new version: {ITEM.VALUE})','27fdbe72229343029ede51c7705c28c4',''),
('23600','{33485} <> {33486} and length({33487}) > 0','YugabyteDB Cluster: YB controller version has changed','','0','1','YugabyteDB Cluster YB controller version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current version: {ITEM.LASTVALUE1}','0','YugabyteDB Cluster: YB controller version has changed (new version: {ITEM.VALUE})','d927b0d668fc413db697a2360ac806a6',''),
('23601','length({33488}) > 0 or length({33489}) > 0 or length({33490}) > 0','YugabyteDB Cluster: Failed to fetch data','','0','2','Failed to fetch data from the YugabyteDB API.',NULL,'0','0','0','','0','','0','','0','','12afa59565304d648e7a0165ea367a2a',''),
('23602','length({33491}) > 0 or length({33492}) > 0','YugabyteDB Cluster: Failed to fetch metric data','','0','2','Failed to fetch cluster metrics or cluster statistics.',NULL,'0','0','0','','0','','0','','0','','93ea4576b31f44ca8ceef6db0ff12e2d',''),
('23606','{33496}=0','Check Point: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','b1d8e86983234d998ed7819d176dc406',''),
('23607','{33497}>{$ICMP_LOSS_WARN} and {33497}<100','Check Point: High ICMP ping loss','','0','2','ICMP packet loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','7fc82682e0c345e8aefd0c9a261f6890',''),
('23608','{33498}>{$ICMP_RESPONSE_TIME_WARN}','Check Point: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','95c6128f0ab84518af233627fe6f3e2b',''),
('23609','{33499}>{$CPU.UTIL.CRIT}','Check Point: 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','Check Point: High CPU utilization (over {$CPU.UTIL.CRIT}% for 5m)','b9df7717d21145dc86954380422671a9',''),
('23610','{33500}<>{33501} and\r\nlength({33502})>0','Check Point: 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','Check Point: Device has been replaced (new serial number received)','13644b6f980d409c865fab446296791b',''),
('23611','{33503}<>{33504} and length({33505})>0','Check Point: 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','Check Point: System name has changed (new name: {ITEM.VALUE})','d6891f768d354bd09adf47ea313a4ec8',''),
('23612','{33506}<10m','Check Point: Device has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Check Point: {HOST.NAME} has been restarted (uptime < 10m)','9c5b6ef7d033486189e045ad62d13991',''),
('23613','{33507}>{$MEMORY.UTIL.MAX}','Check Point: High memory utilization','','0','3','The system is running out of free memory.',NULL,'0','0','0','','0','','0','','0','Check Point: High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)','e641a3b2e5ce41dabffed001b26c6075',''),
('23614','{33508}=0','Check Point: 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','','5d450a6a6d1f483da57164e6a32d1828',''),
('23615','{33509}/{33510}>{$LOAD_AVG_PER_CPU.MAX.WARN}\r\nand {33511}>0\r\nand {33512}>0','Check Point: 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','Check Point: Load average is too high (per CPU load over {$LOAD_AVG_PER_CPU.MAX.WARN} for 5m)','dc26681b9d8244799f28c6bda3dded3c',''),
('23635','{33553} = 0','OCI Autonomous DB: Database is not available','','0','4','Autonomous database is not available.',NULL,'0','0','0','','0','','0','','0','','21b1a5c7d7754eb6be30098b2df99a22',''),
('23636','{33554} >= {$OCI.AUTONOMOUS.DB.CPU.UTIL.WARN}','OCI Autonomous DB: Current CPU utilization is high','','0','2','Current CPU utilization has exceeded `{$OCI.AUTONOMOUS.DB.CPU.UTIL.WARN}`% of the max available value.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}','0','OCI Autonomous DB: Current CPU utilization is high (util >= {$OCI.AUTONOMOUS.DB.CPU.UTIL.WARN}%)','59fd2d0eff9f4f5493cd0de94ba57572',''),
('23637','{33555} >= {$OCI.AUTONOMOUS.DB.CPU.UTIL.HIGH}','OCI Autonomous DB: Current CPU utilization is too high','','0','4','Current CPU utilization has exceeded `{$OCI.AUTONOMOUS.DB.CPU.UTIL.HIGH}`% of the max available value.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}','0','OCI Autonomous DB: Current CPU utilization is too high (util >= {$OCI.AUTONOMOUS.DB.CPU.UTIL.HIGH}%)','f8a53ef11d2140649bc701660183c33d',''),
('23638','{33556} = 12','OCI Autonomous DB: Available, needs attention','','0','2','Autonomous database is available, but needs attention.',NULL,'0','0','0','','0','','0','','0','','bb790262359f4e35af895b1a69ad511c',''),
('23639','{33557} = 19 or {33557} = 20','OCI Autonomous DB: Database is not available or accessible','','0','4','Autonomous database is not available or accessible.',NULL,'0','0','0','','0','','0','','0','','18594a88549843c498d0e037f51afc59',''),
('23640','{33558} = 9','OCI Autonomous DB: Restore has failed','','0','2','Autonomous database restore has failed.',NULL,'0','0','0','','0','','0','','0','','4ee1a96f29ef461c8830667e19637911',''),
('23641','{33559}<>{33560}','OCI Autonomous DB: State has changed','','0','1','Autonomous database state has changed.',NULL,'0','0','0','','0','','1','Current state: {ITEM.LASTVALUE}','0','OCI Autonomous DB: State has changed (new state: {ITEM.VALUE})','783550ed705944259190fb10dae3f5a8',''),
('23642','{33561} = 0','OCI Autonomous DB: State unknown','','0','2','Autonomous database state is unknown.',NULL,'0','0','0','','0','','0','','0','','2bc79a5a19a544d39c6de861b94564af',''),
('23643','{33562} >= {$OCI.AUTONOMOUS.DB.STORAGE.UTIL.WARN}','OCI Autonomous DB: Current storage utilization is high','','0','2','Current storage utilization has exceeded `{$OCI.AUTONOMOUS.DB.STORAGE.UTIL.WARN}`% of the max available value.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}','0','OCI Autonomous DB: Current storage utilization is high (util >= {$OCI.AUTONOMOUS.DB.STORAGE.UTIL.WARN}%)','37bb41d830424ba2871e768957225add',''),
('23644','{33563} >= {$OCI.AUTONOMOUS.DB.STORAGE.UTIL.HIGH}','OCI Autonomous DB: Current storage utilization is too high','','0','4','Current storage utilization has exceeded `{$OCI.AUTONOMOUS.DB.STORAGE.UTIL.HIGH}`% of the max available value.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}','0','OCI Autonomous DB: Current storage utilization is too high (util >= {$OCI.AUTONOMOUS.DB.STORAGE.UTIL.HIGH}%)','8e16451106094713abaa624967026dc3',''),
('23645','{33564} = 0','OCI Block Volume: Block volume state unknown','','0','2','Block volume state is unknown.',NULL,'0','0','0','','0','','0','','0','','4ea859d86e29455aa4bdd2f3667894f6',''),
('23646','{33565} >= 4','OCI Block Volume: Block volume terminated or faulty','','0','4','Block volume state is "terminated"/"terminating" or "faulty".',NULL,'0','0','0','','0','','0','','0','','b8d9491d762f40c58fb1094fa0468d9e',''),
('23647','{33566} = 0','OCI Boot Volume: Boot volume state unknown','','0','2','Boot volume state is unknown.',NULL,'0','0','0','','0','','0','','0','','b31f698c5b164afc85a14acc813f463d',''),
('23648','{33567} >= 4','OCI Boot Volume: Boot volume terminated or faulty','','0','4','Boot volume state is "terminated"/"terminating" or "faulty".',NULL,'0','0','0','','0','','0','','0','','6525eef6dd6c4cb0a22a6442773c3cfa',''),
('23649','{33568} = 1','OCI Compute: Compute instance is not available','','0','4','Current instance availability.',NULL,'0','0','0','','0','','0','','0','','dbaee26c1de544d08fa6dd76ddc4c06a',''),
('23650','{33569} >= {$OCI.COMPUTE.CPU.UTIL.WARN}','OCI Compute: Current CPU utilization is high','','0','2','Current CPU utilization has exceeded `{$OCI.COMPUTE.CPU.UTIL.WARN}`% of the max available value.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}','0','OCI Compute: Current CPU utilization is high (util >= {$OCI.COMPUTE.CPU.UTIL.WARN}%)','38987527713b404f842e26ad12ce3015',''),
('23651','{33570} >= {$OCI.COMPUTE.CPU.UTIL.HIGH}','OCI Compute: Current CPU utilization is too high','','0','4','Current CPU utilization has exceeded `{$OCI.COMPUTE.CPU.UTIL.HIGH}`% of the max available value.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}','0','OCI Compute: Current CPU utilization is too high (util >= {$OCI.COMPUTE.CPU.UTIL.HIGH}%)','082ba105bf614996a68054ad8c7d7101',''),
('23652','{33571} >= {$OCI.COMPUTE.MEM.UTIL.WARN}','OCI Compute: Current memory utilization is high','','0','2','Current memory utilization has exceeded `{$OCI.COMPUTE.MEM.UTIL.WARN}`% of the max available value.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}','0','OCI Compute: Current memory utilization is high (util >= {$OCI.COMPUTE.MEM.UTIL.WARN}%)','9baaacf70a4446a7ae816afdc4db0ae8',''),
('23653','{33572} >= {$OCI.COMPUTE.MEM.UTIL.HIGH}','OCI Compute: Current memory utilization is too high','','0','4','Current memory utilization has exceeded `{$OCI.COMPUTE.MEM.UTIL.HIGH}`% of the max available value.',NULL,'0','0','0','','0','','0','Current: {ITEM.LASTVALUE1}','0','OCI Compute: Current memory utilization is too high (util >= {$OCI.COMPUTE.MEM.UTIL.HIGH}%)','3b894aa250f04ebdb63fb8a914fbd72a',''),
('23654','{33573}<>{33574}','OCI Compute: State has changed','','0','1','Compute instance state has changed.',NULL,'0','0','0','','0','','1','Current state: {ITEM.LASTVALUE}','0','OCI Compute: State has changed (new state: {ITEM.VALUE})','2bce7c23998f4331a5eca3507fc671d9',''),
('23655','{33575} = 3 or {33575} = 4','OCI VCN: VCN state terminated','','0','4','Virtual cloud network state is "terminated" or "terminating".',NULL,'0','0','0','','0','','0','','0','','8a5a94ea28db43df93e85d26703f9e7c',''),
('23656','{33576} = 0','OCI VCN: VCN state unknown','','0','2','Virtual cloud network state is unknown.',NULL,'0','0','0','','0','','0','','0','','80c3f4d6696c40a78ddb2c00378eeae1',''),
('23657','{33577}<>{33578} and length({33579})>0','OCI Object Storage: Object lifecycle management policy has changed','','0','1','The object lifecycle management policy configuration has changed.',NULL,'0','0','0','','0','','0','','0','','5d9652a8736247c2bcac15cf02012824',''),
('23664','{33587}<{$DISK.FREE.WARN}','FortiGate: Free disk space is low','','0','2','Available disk space is not enough.',NULL,'0','0','0','','0','','0','','0','FortiGate: Free disk space is less than {$DISK.FREE.WARN}%','424ab075f1ff46e1b64f9416dee4f3f7',''),
('23676','length({33619})>0','AWS ELB NLB: Failed to get alarms data','','0','2','Failed to get CloudWatch alarms for Network Load Balancer.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS ELB NLB: Failed to get CloudWatch alarms for Network Load Balancer','4319dc0d484b456a9343535db3c079f4',''),
('23677','length({33620})>0','AWS ELB NLB: Failed to get metrics data','','0','2','Failed to get CloudWatch metrics for Network Load Balancer.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS ELB NLB: Failed to get CloudWatch metrics for Network Load Balancer','c2ba26fed3324a2bb9b90493a99db088',''),
('23701','length({33676})>0','Website by Browser: Failed to get metrics data','','0','4','Failed to get JSON with performance counters of the requested website \'{$WEBSITE.DOMAIN}\'.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Website by Browser: Failed to get JSON of the requested website \'{$WEBSITE.DOMAIN}\'','56970ddca5b94afdb2186741edd85362',''),
('23702','{33677}>{$WEBSITE.NAVIGATION.LOAD.MAX.WARN}','Website by Browser: Website navigation load event time is too slow','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Website by Browser: Website {$WEBSITE.DOMAIN} navigation load event time > {$WEBSITE.NAVIGATION.LOAD.MAX.WARN}','a2d63bfe681848fdb984f3b579262086',''),
('23703','{33678}>{$WEBSITE.RESOURCE.LOAD.MAX.WARN}','Website by Browser: Website resource load event time is too slow','','0','2','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','Website by Browser: Website {$WEBSITE.DOMAIN} resource load event time > \'{$WEBSITE.RESOURCE.LOAD.MAX.WARN}\'','1f7fbe56f5bf49468fb597a2ff986cd7',''),
('23704','{33679}>{33680}','GitHub: The total number of issues has increased','','0','2','The total number of issues has increased which means that either a new issue (or multiple) has been opened.',NULL,'1','0','0','','0','','0','','0','','9a146a900ced45b09a09b402daae6f94',''),
('23705','{33681}>{33682}','GitHub: The total number of PRs has increased','','0','1','The total number of pull requests has increased which means that either a new pull request (or multiple) has been opened.',NULL,'1','0','0','','0','','0','','0','','7d834276726941cf9952c820e478ccf0',''),
('23706','length({33683})>0','GitHub: There are errors in requests to API','','0','3','Errors have been received in response to API requests. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','fea49679a888491c96516b421703131b',''),
('23707','{33684}>{$GITHUB.REQUESTS.UTIL.WARN}','GitHub: API request limit utilization is high','','0','2','The API request limit utilization is high. It can be lowered by increasing the update intervals for script items (by setting up higher values in corresponding context macros).\r\n\r\nThe trigger will be resolved automatically if the limit usage drops 5% below the trigger threshold.\r\n\r\nInformation about request limits in GitHub REST API documentation:\r\nhttps://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28',NULL,'0','0','1','{33684}>{$GITHUB.REQUESTS.UTIL.WARN}-5','0','','0','','0','GitHub: API request limit utilization is high (usage is > {$GITHUB.REQUESTS.UTIL.WARN})','621ef82bf8f74f09a8c30b8a38085e9d',''),
('23708','{33685}>{$GITHUB.REQUESTS.UTIL.HIGH}','GitHub: API request limit utilization is very high','','0','3','The API request limit utilization is very high. It can be lowered by increasing the update intervals for script items (by setting up higher values in corresponding context macros).\r\n\r\nThe trigger will be resolved automatically if the limit usage drops 5% below the trigger threshold.\r\n\r\nInformation about request limits in GitHub REST API documentation:\r\nhttps://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28',NULL,'0','0','1','{33685}>{$GITHUB.REQUESTS.UTIL.HIGH}-5','0','','0','','0','GitHub: API request limit utilization is very high (usage is > {$GITHUB.REQUESTS.UTIL.HIGH})','9783018b6c394397aa093b4f8a1a4067',''),
('23709','{33686}=1','GitHub: No access to repository self-hosted runners','','0','3','Admin access to the repository is required to use this endpoint:\r\nhttps://docs.github.com/en/rest/actions/self-hosted-runners?apiVersion=2022-11-28#list-self-hosted-runners-for-a-repository',NULL,'0','0','0','','0','','0','','0','','30877fea1bd14e22b8b5c4a040001bb5',''),
('23714','{33694}<=0','Jira Data Center: DB: Pool: Out of idle connections','','0','2','Fires when out of idle connections in database pool for 5 minutes.',NULL,'0','0','0','','0','','1','Idle connections: {ITEM.LASTVALUE1}','0','','5fd9800d1c3641c584e32106ea61e33d',''),
('23715','{33695}=0','Jira Data Center: DB: Connection lost','','0','3','Database connection lost',NULL,'0','0','0','','0','','1','Connection state: {ITEM.LASTVALUE1}','0','','524b7cb0ac9940ad80e11f1c93f1d7df',''),
('23716','{33696}<=0','Jira Data Center: HTTP: Pool: Out of idle connections','','0','2','All available connections are utilized. It can cause outages for users as the system is unable to serve their requests.',NULL,'0','0','0','','0','','1','active {ITEM.LASTVALUE1} from {ITEM.LASTVALUE2}','0','','7f0fde38527c4bb2930a1e57343c4422',''),
('23717','{33697}>0','Jira Data Center: Mail: Error queue contains one or more items','','0','2','A mail queue attempts to resend items up to 10 times. If the operation fails for the 11th time, the items are put into an error mail queue.\r\nYou can remove items from the error mail queue in one of the following ways:\r\n  - Manually clear the whole error queue.\r\n  - Manually resend all items from the error queue to a mail queue.\r\nYou should pay attention to the cases where an error mail queue item gets back to an error mail queue after you resend the items manually. These cases might indicate permanent performance issues.',NULL,'0','0','0','','0','','1','','0','','f0940aecb8f24e788dae0e62c81a0c65',''),
('23718','{33698}>0','Jira Data Center: Mail: Queue: Doesn’t empty over an extended period','','0','2','Might indicate SMTP performance or connection problems.',NULL,'0','0','0','','0','','1','','0','','6fc20e23f96f4bf8a856d1c86679cbd5',''),
('23719','{33699}={33700}','Jira Data Center: DB: Connection limit reached','','0','2','',NULL,'0','0','0','','0','','1','active {ITEM.LASTVALUE1} from {ITEM.LASTVALUE2}','0','','a91e17e5f510499eb6d0848703cf3df1',''),
('23720','100*{33701}/{33702}>{$JIRA_DC.DB.CONNECTION.USAGE.WARN}','Jira Data Center: DB: Connection usage is near the limit','','0','2','',NULL,'0','0','0','','0','','1','active {ITEM.LASTVALUE1} from {ITEM.LASTVALUE2}','0','Jira Data Center: DB: Connection usage is near the limit (above {$JIRA_DC.DB.CONNECTION.USAGE.WARN}%)','8de58465caad4a188a1a84140ec9ebcf',''),
('23721','{33703}=0 and {33704}>0','Jira Data Center: Mail: Queue job is not running','','0','3','It should be running when its queue is not empty.\r\nMight indicate SMTP server connection problems.',NULL,'0','0','0','','0','','1','','0','','7fc17e55907041c2a907310bd45f14be',''),
('23728','length({33722})>0','Microsoft 365: Apps: 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','','eab5ac8df92f43398ad62a2dacb53e98',''),
('23729','length({33723})>0','Microsoft 365: OneDrive: 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','','b526cc91e49041a1ba4fac76b8f464c2',''),
('23730','length({33724})>0','Microsoft 365: Outlook: 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','','79d0d9d9622347e2a7c937b7831ac01b',''),
('23731','length({33725})>0','Microsoft 365: Services: 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','','54c11aad4113433a866272988a64c2bf',''),
('23732','length({33726})>0','Microsoft 365: SharePoint: 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','','af3d4e3b2ca84ad39780d6d5e13afdee',''),
('23733','length({33727})>0','Microsoft 365: Teams: 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','','18c8af3eea6f49b1ba795b476e218ab9',''),
('23736','length({33733})>0','VMware: Failed to get Overall Health VC State','','0','2','Failed to get data. Check debug log for more information.',NULL,'0','0','0','','0','','0','Current error: {ITEM.LASTVALUE}','0','','a11ed3829afb48fb99b9feb2dab4a45d',''),
('23737','{33734}>0 and {33734}<>6','VMware: Overall Health VC State is not Green','','0','3','One or more components in the appliance might be in an unusable status and the appliance might soon become unresponsive.',NULL,'0','0','0','','0','','0','Current Overall Health VC State: {ITEM.LASTVALUE}','0','','4058114acbc743e087f5b10e22c997d1',''),
('23738','{33735}=0','VMware Guest: Snapshot consolidation needed','','0','3','Snapshot consolidation needed.',NULL,'0','0','0','','0','','1','','0','','28627af63fe64e79b08ad752dee5205e',''),
('23739','{33736}=1 and {$VMWARE.HYPERVISOR.MAINTENANCE}=1','VMware Guest: Hypervisor is in the maintenance mode','','0','1','Hypervisor is in the maintenance mode. All other problem on the host will be suppressed.',NULL,'0','0','0','','0','','0','','0','VMware Guest: Hypervisor is in the maintenance mode','05c2982de3f94647808a523a91af554c',''),
('23740','{33737} <> 2','VMware Guest: VM is not running','','0','3','VMware virtual machine is not running.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','6ebb2a2de81e4bacbb32d1b767c3cb04',''),
('23741','{33738} = 1','VMware Guest: VMware Tools is not running','','0','2','VMware Tools is not running on the VM.',NULL,'0','0','0','','0','','0','','0','','132d6e490fea42e390de64ce389ad538',''),
('23749','length({33748})>0','VMware FQDN: Failed to get Overall Health VC State','','0','2','Failed to get data. Check debug log for more information.',NULL,'0','0','0','','0','','0','Current error: {ITEM.LASTVALUE}','0','','7fe1b44b0e7549d8af9030a1c58b2aa3',''),
('23750','{33749}>0 and {33749}<>6','VMware FQDN: Overall Health VC State is not Green','','0','3','One or more components in the appliance might be in an unusable status and the appliance might soon become unresponsive.',NULL,'0','0','0','','0','','0','Current Overall Health VC State: {ITEM.LASTVALUE}','0','','426ea642132848b8b77d42d2235c244c',''),
('23754','{33758}>{$ZABBIX.PROXY.UTIL.MAX:"browser poller"}','Zabbix proxy: Utilization of browser poller processes is high','','0','3','Indicates potential performance issues with the browser poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33758}<{$ZABBIX.PROXY.UTIL.MIN:"browser poller"}','0','','0','','0','Zabbix proxy: Utilization of browser poller processes over {$ZABBIX.PROXY.UTIL.MAX:"browser poller"}%','5cdced4b0c064f62802c360fa84408db',''),
('23755','{33759}>{$ZABBIX.PROXY.UTIL.MAX:"internal poller"}','Zabbix proxy: Utilization of internal poller processes is high','','0','3','Indicates potential performance issues with the internal poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33759}<{$ZABBIX.PROXY.UTIL.MIN:"internal poller"}','0','','0','','0','Zabbix proxy: Utilization of internal poller processes over {$ZABBIX.PROXY.UTIL.MAX:"internal poller"}%','3bc0e6ab1a9e470682d049840df4ce5a',''),
('23756','{33765}>{$ZABBIX.PROXY.UTIL.MAX:"browser poller"}','Zabbix proxy: Utilization of browser poller processes is high','','0','3','Indicates potential performance issues with the browser poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33765}<{$ZABBIX.PROXY.UTIL.MIN:"browser poller"}','0','','0','','0','Zabbix proxy: Utilization of browser poller processes over {$ZABBIX.PROXY.UTIL.MAX:"browser poller"}%','8458680e160d4f2ba1d1d2c20453dfe4',''),
('23757','{33766}>{$ZABBIX.PROXY.UTIL.MAX:"internal poller"}','Zabbix proxy: Utilization of internal poller processes is high','','0','3','Indicates potential performance issues with the internal poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33766}<{$ZABBIX.PROXY.UTIL.MIN:"internal poller"}','0','','0','','0','Zabbix proxy: Utilization of internal poller processes over {$ZABBIX.PROXY.UTIL.MAX:"internal poller"}%','5bea08baaad04d4e8d15540e931e0336',''),
('23758','{33857}>{$ZABBIX.SERVER.UTIL.MAX:"browser poller"}','Zabbix server: Utilization of browser poller processes is high','','0','3','Indicates potential performance issues with the browser poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33857}<{$ZABBIX.SERVER.UTIL.MIN:"browser poller"}','0','','0','','0','Zabbix server: Utilization of browser poller processes over {$ZABBIX.SERVER.UTIL.MAX:"browser poller"}%','c260a09bb64c438bb4d3b720ecf51bc6',''),
('23759','{33858}>{$ZABBIX.SERVER.UTIL.MAX:"configuration syncer worker"}','Zabbix server: Utilization of configuration syncer worker processes is high','','0','3','Indicates potential performance issues with the configuration syncer worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33858}<{$ZABBIX.SERVER.UTIL.MIN:"configuration syncer worker"}','0','','0','','0','Zabbix server: Utilization of configuration syncer worker processes over {$ZABBIX.SERVER.UTIL.MAX:"configuration syncer worker"}%','c5fe6915d3a34e13b7a2fd1326e3781a',''),
('23760','{33859}>{$ZABBIX.SERVER.UTIL.MAX:"internal poller"}','Zabbix server: Utilization of internal poller processes is high','','0','3','Indicates potential performance issues with the internal poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33859}<{$ZABBIX.SERVER.UTIL.MIN:"internal poller"}','0','','0','','0','Zabbix server: Utilization of internal poller processes over {$ZABBIX.SERVER.UTIL.MAX:"internal poller"}%','9bf9a345764740b79eb7e36398992593',''),
('23761','{33860}>{$ZABBIX.SERVER.UTIL.MAX:"proxy group manager"}','Zabbix server: Utilization of proxy group manager processes is high','','0','3','Indicates potential performance issues with the proxy group manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33860}<{$ZABBIX.SERVER.UTIL.MIN:"proxy group manager"}','0','','0','','0','Zabbix server: Utilization of proxy group manager processes over {$ZABBIX.SERVER.UTIL.MAX:"proxy group manager"}%','67db7f858e0348feb7cfe26f2afa1bd6',''),
('23778','{33926}>{$ZABBIX.SERVER.UTIL.MAX:"browser poller"}','Zabbix server: Utilization of browser poller processes is high','','0','3','Indicates potential performance issues with the browser poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33926}<{$ZABBIX.SERVER.UTIL.MIN:"browser poller"}','0','','0','','0','Zabbix server: Utilization of browser poller processes over {$ZABBIX.SERVER.UTIL.MAX:"browser poller"}%','5c41e353d4a4442d992240214443ee4d',''),
('23779','{33927}>{$ZABBIX.SERVER.UTIL.MAX:"configuration syncer worker"}','Zabbix server: Utilization of configuration syncer worker processes is high','','0','3','Indicates potential performance issues with the configuration syncer worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33927}<{$ZABBIX.SERVER.UTIL.MIN:"configuration syncer worker"}','0','','0','','0','Zabbix server: Utilization of configuration syncer worker processes over {$ZABBIX.SERVER.UTIL.MAX:"configuration syncer worker"}%','4b33128b800f4d1384127b61a7dd7492',''),
('23780','{33928}>{$ZABBIX.SERVER.UTIL.MAX:"internal poller"}','Zabbix server: Utilization of internal poller processes is high','','0','3','Indicates potential performance issues with the internal poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33928}<{$ZABBIX.SERVER.UTIL.MIN:"internal poller"}','0','','0','','0','Zabbix server: Utilization of internal poller processes over {$ZABBIX.SERVER.UTIL.MAX:"internal poller"}%','a84501d9e5b74b4990a896f8719b980d',''),
('23781','{33929}>{$ZABBIX.SERVER.UTIL.MAX:"proxy group manager"}','Zabbix server: Utilization of proxy group manager processes is high','','0','3','Indicates potential performance issues with the proxy group manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{33929}<{$ZABBIX.SERVER.UTIL.MIN:"proxy group manager"}','0','','0','','0','Zabbix server: Utilization of proxy group manager processes over {$ZABBIX.SERVER.UTIL.MAX:"proxy group manager"}%','06bdef8b23c3459c99e180afdb1a8b2c',''),
('23782','length({33930})>0','AWS Lambda: Failed to get alarms data','','0','2','Failed to get CloudWatch alarms for the Lambda function.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS Lambda: Failed to get CloudWatch alarms for the Lambda function','77f2bf7f1086488289b1cf1931e8fd90',''),
('23783','length({33931})>0','AWS Lambda: Failed to get metrics data','','0','2','Failed to get CloudWatch metrics for the Lambda function.',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','AWS Lambda: Failed to get CloudWatch metrics for the Lambda function','95ed5e8c560f4c6e89ed9d1a754ed032',''),
('23786','{33935}=1','Azure VM Scale: Virtual machine scale set is degraded','','0','3','The resource is in a degraded state.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','a1aadc807a6d40bd8dd2049c0ead6e38',''),
('23787','{33936}=3','Azure VM Scale: Virtual machine scale set is in unknown state','','0','2','The resource state is unknown.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','c09bb8da8bb54c45b6d424a63ec892ae',''),
('23788','{33937}=2','Azure VM Scale: Virtual machine scale set is unavailable','','0','4','The resource state is unavailable.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','eff890c95f574ad09af82ad79803e733',''),
('23789','{33938}>{$AZURE.SCALESET.CPU.UTIL.CRIT}','Azure VM Scale: 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 Scale: CPU utilization is high (over {$AZURE.SCALESET.CPU.UTIL.CRIT}% for last 5m)','a3706a6c3349429b89b6915a6b0fb5c1',''),
('23790','length({33939})>0','Azure VM Scale: 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','','1d114800a6534498b52a2dd25e93d719',''),
('23791','{33940}>{$AZURE.SCALESET.VM.COUNT.CRIT}','Azure VM Scale: High amount of VMs in the scale set','','0','4','High amount of VMs in the scale set.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','Azure VM Scale: Number of VMs is high (over {$AZURE.SCALESET.VM.COUNT.CRIT} for last 5m)','cd77906ed04a42f28bb702bc513504a0',''),
('23793','{33953}<>{33954} and length({33955})>0','Huawei Dorado: Storage version has changed','','0','1','',NULL,'0','0','0','','0','','1','','0','Huawei Dorado: Version has changed (new version: {ITEM.VALUE})','eb140be38e9c4f51b105347ddffa6997',''),
('23794','{33956}=0','Huawei Dorado: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','914602a8433444a18ac0672f776b836e',''),
('23795','{33957}>{$ICMP_LOSS_WARN} and {33957}<100','Huawei Dorado: High ICMP ping loss','','0','2','ICMP packets loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','','60f0ddb37f534c5baf4a7ad254d57ea7',''),
('23796','{33958}>{$ICMP_RESPONSE_TIME_WARN}','Huawei Dorado: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','','9af7c5ff0d974d0abb51cd483e46e537',''),
('23797','{33959}<>{33960} and length({33961})>0','Huawei Dorado: 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 Dorado: System name has changed (new name: {ITEM.VALUE})','6beeaf5594eb46e183db9e725277e0b6',''),
('23798','{33962}=0','Huawei Dorado: 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','','4c9c747fc91c493b9b35db7d1dcc1461',''),
('23799','({33963}>0 and {33963}<10m) or ({33963}=0 and {33964}<10m)','Huawei Dorado: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Huawei Dorado: {HOST.NAME} has been restarted (uptime < 10m)','41d6237c6623468ba232930318f7a335',''),
('23820','{33986}<10m','Apache: Service has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Apache: Service has been restarted (uptime < 10m)','2f9e1d5e188f4f6190088986f6fc3f70',''),
('23821','{33987}<>{33988} and length({33989})>0','Apache: Version has changed','','0','1','Apache version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Apache: Version has changed (new version: {ITEM.VALUE})','80d8c27a060347a4a852c3f6481244c3',''),
('23829','{34001}<>{34002} and length({34003})>0','Nginx: Version has changed','','0','1','The Nginx version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Nginx: Version has changed (new version: {ITEM.VALUE})','bc987aa081b543b2becd7c0863553f27',''),
('23835','length({34014})>0','Nutanix: Failed to get alert data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','741e1271a7454b9ab0214ae39b04f9cb',''),
('23836','length({34015})>0','Nutanix: Failed to get metric data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','5ac8ddec162b4668b1df1493216792d6',''),
('23837','length({34016})>0','Nutanix: Failed to get alert data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','6dbb467d463e47dca35970591ef1446f',''),
('23838','length({34017})>0','Nutanix: Failed to get disk data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','a105b91b5d48438b93abc257b238e2c9',''),
('23839','{34018}=1','Nutanix: Host is in degraded status','','0','4','Host is in a degraded status. The host may soon become unavailable.',NULL,'0','0','0','','0','','0','','0','','f10f4b560bd140cabb3beb4ee1dbbf78',''),
('23840','length({34019})>0','Nutanix: Failed to get metric data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','f23095d512e845ae846a2b774b97de51',''),
('23841','length({34020})>0','Nutanix: Failed to get cluster data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','baf3ae722bd44a09a628f9c81c541259',''),
('23842','length({34021})>0','Nutanix: Failed to get host data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','56e915c86d4640c3b073cb8309bf1d6e',''),
('23843','length({34022})>0','Nutanix: Failed to get storage container data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','f46c6213084c4afe88065beb6cdcef33',''),
('23844','{34023}<>{34024}','Nutanix: Redundancy factor mismatched','','0','4','Current redundancy factor does not match the desired redundancy factor.',NULL,'0','0','0','','0','','0','','0','','95d69032f7d7426d8073524ecd72fcd4',''),
('23845','{34025} > {$PHP_FPM.QUEUE.WARN.MAX}','PHP-FPM: Queue utilization is high','','0','2','The queue for this pool has reached `{$PHP_FPM.QUEUE.WARN.MAX}%` of its maximum capacity. \r\nItems in the queue represent the current number of connections that have been initiated on this pool but not yet accepted.',NULL,'0','0','0','','0','','0','','0','PHP-FPM: Queue utilization is high (over {$PHP_FPM.QUEUE.WARN.MAX}% for 15m)','ffe46ce6fa4545ac8b2f035488c1b7ba',''),
('23846','{34026}<>{34027}','PHP-FPM: Manager changed','','0','1','The PHP-FPM manager has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','PHP-FPM: Manager changed (new value received: {ITEM.VALUE})','380943ae41cd48e5b903f433216f3cd1',''),
('23847','{34028}>0','PHP-FPM: Detected slow requests','','0','2','The PHP-FPM has detected a slow request. \r\nThe slow request means that it took more time to execute than expected (defined in the configuration of your pool).',NULL,'0','0','0','','0','','0','','0','','4a25c3fecad74df7ba59be94dd1df7cf',''),
('23848','{34029}<10m','PHP-FPM: Pool has been restarted','','0','1','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','PHP-FPM: Pool has been restarted (uptime < 10m)','77e61db3d40d4bd1ba518d27dfd05491',''),
('23849','{34030}<>{34031} and length({34032})>0','PHP-FPM: Version has changed','','0','1','The PHP-FPM version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','PHP-FPM: Version has changed (new version: {ITEM.VALUE})','27684ff67232429dad79e0eae323945d',''),
('23854','{34041}>{$MYSQL.ABORTED_CONN.MAX.WARN}','MySQL: Server has aborted connections','','0','3','The number of failed attempts to connect to the MySQL server is more than `{$MYSQL.ABORTED_CONN.MAX.WARN}` in the last 5 minutes.',NULL,'0','0','0','','0','','0','','0','MySQL: Server has aborted connections (over {$MYSQL.ABORTED_CONN.MAX.WARN} for 5m)','a8dbc39812ea4ce488dab64ee230c38c',''),
('23855','{34042}<{$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)','69e652db80c145e4bf7a4d4e99e0cb35',''),
('23856','{34043}>0','MySQL: Refused connections','','0','3','Number of refused connections due to the `max_connections` limit being reached.',NULL,'0','0','0','','0','','0','','0','MySQL: Refused connections (max_connections limit reached)','4f4cdc4d19624598aaa68d18e13a45e4',''),
('23857','{34044}>{$MYSQL.CREATED_TMP_DISK_TABLES.MAX.WARN}','MySQL: Number of on-disk temporary tables created per second is high','','0','2','The application using the database may be in need of query optimization.',NULL,'0','0','0','','0','','0','','0','MySQL: Number of on-disk temporary tables created per second is high (over {$MYSQL.CREATED_TMP_DISK_TABLES.MAX.WARN} for 5m)','cc8af7c9017a4873a037b5a0a8f7ac5f',''),
('23858','{34045}>{$MYSQL.CREATED_TMP_FILES.MAX.WARN}','MySQL: Number of temporary files created per second is high','','0','2','The application using the database may be in need of query optimization.',NULL,'0','0','0','','0','','0','','0','MySQL: Number of temporary files created per second is high (over {$MYSQL.CREATED_TMP_FILES.MAX.WARN} for 5m)','92ef67f27f384dd899ddb2865e00273a',''),
('23859','{34046}>{$MYSQL.CREATED_TMP_TABLES.MAX.WARN}','MySQL: Number of internal temporary tables created per second is high','','0','2','The application using the database may be in need of query optimization.',NULL,'0','0','0','','0','','0','','0','MySQL: Number of internal temporary tables created per second is high (over {$MYSQL.CREATED_TMP_TABLES.MAX.WARN} for 5m)','1d927f1cbb3b4105accbaef3f0994f81',''),
('23860','{34047}=0','MySQL: Service is down','','0','4','MySQL is down.',NULL,'0','0','0','','0','','0','','0','','6fed4cabb4b349cd9a0f7e82e7706139',''),
('23861','{34048}>{$MYSQL.SLOW_QUERIES.MAX.WARN}','MySQL: Server has slow queries','','0','2','The number of slow queries is more than `{$MYSQL.SLOW_QUERIES.MAX.WARN}` in the last 5 minutes.',NULL,'0','0','0','','0','','0','','0','MySQL: Server has slow queries (over {$MYSQL.SLOW_QUERIES.MAX.WARN} for 5m)','28b12490a27641ce828ec4d2e80f81b6',''),
('23862','{34049}=1','MySQL: Failed to fetch info data','','0','1','Zabbix has not received any data for items for the last 30 minutes.',NULL,'0','0','0','','0','','0','','0','MySQL: Failed to fetch info data (or no data for 30m)','3449a131f65d44c487a3346529713dd2',''),
('23863','{34050}<10m','MySQL: Service has been restarted','','0','1','MySQL uptime is less than 10 minutes.',NULL,'0','0','0','','0','','0','','0','MySQL: Service has been restarted (uptime < 10m)','f92226addbf14463aea5aedc4f7bf7d8',''),
('23864','{34051}<>{34052} and length({34053})>0','MySQL: Version has changed','','0','1','The MySQL version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MySQL: Version has changed (new version value received: {ITEM.VALUE})','36ce1008736b4a109a060e1150fec15f',''),
('23869','{34058}>{$MYSQL.ABORTED_CONN.MAX.WARN}','MySQL: Server has aborted connections','','0','3','The number of failed attempts to connect to the MySQL server is more than `{$MYSQL.ABORTED_CONN.MAX.WARN}` in the last 5 minutes.',NULL,'0','0','0','','0','','0','','0','MySQL: Server has aborted connections (over {$MYSQL.ABORTED_CONN.MAX.WARN} for 5m)','f49998d4098348378c661927155cd6bf',''),
('23870','{34059}<{$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)','254756ed1bcb4ae3b342d34b86e1b6fc',''),
('23871','{34060}>0','MySQL: Refused connections','','0','3','Number of refused connections due to the `max_connections` limit being reached.',NULL,'0','0','0','','0','','0','','0','MySQL: Refused connections (max_connections limit reached)','8ce8e2bd4713435e83ccd036e84e1120',''),
('23872','{34061}>{$MYSQL.CREATED_TMP_DISK_TABLES.MAX.WARN}','MySQL: Number of on-disk temporary tables created per second is high','','0','2','The application using the database may be in need of query optimization.',NULL,'0','0','0','','0','','0','','0','MySQL: Number of on-disk temporary tables created per second is high (over {$MYSQL.CREATED_TMP_DISK_TABLES.MAX.WARN} for 5m)','5b6d0d6c7fee4fefb1ed58017818f223',''),
('23873','{34062}>{$MYSQL.CREATED_TMP_FILES.MAX.WARN}','MySQL: Number of temporary files created per second is high','','0','2','The application using the database may be in need of query optimization.',NULL,'0','0','0','','0','','0','','0','MySQL: Number of temporary files created per second is high (over {$MYSQL.CREATED_TMP_FILES.MAX.WARN} for 5m)','3c49bcc1e3e34d1ca6f1d1b5eeeeba9e',''),
('23874','{34063}>{$MYSQL.CREATED_TMP_TABLES.MAX.WARN}','MySQL: Number of internal temporary tables created per second is high','','0','2','The application using the database may be in need of query optimization.',NULL,'0','0','0','','0','','0','','0','MySQL: Number of internal temporary tables created per second is high (over {$MYSQL.CREATED_TMP_TABLES.MAX.WARN} for 5m)','ef985e5db11a49139b0022aaf80cb2d5',''),
('23875','{34064}=0','MySQL: Service is down','','0','4','MySQL is down.',NULL,'0','0','0','','0','','0','','0','','fd1b0391ac694aa89950426d75ed3646',''),
('23876','{34065}>{$MYSQL.SLOW_QUERIES.MAX.WARN}','MySQL: Server has slow queries','','0','2','The number of slow queries is more than `{$MYSQL.SLOW_QUERIES.MAX.WARN}` in the last 5 minutes.',NULL,'0','0','0','','0','','0','','0','MySQL: Server has slow queries (over {$MYSQL.SLOW_QUERIES.MAX.WARN} for 5m)','72cbaa89dfc7447aad99ac7a9ae78a17',''),
('23877','{34066}=1','MySQL: Failed to fetch info data','','0','1','Zabbix has not received any data for items for the last 30 minutes.',NULL,'0','0','0','','0','','0','','0','MySQL: Failed to fetch info data (or no data for 30m)','4e9e4b036c224c6a8f39a41e8ca2f225',''),
('23878','{34067}<10m','MySQL: Service has been restarted','','0','1','MySQL uptime is less than 10 minutes.',NULL,'0','0','0','','0','','0','','0','MySQL: Service has been restarted (uptime < 10m)','05c74a05d68445f38f4c5af591f0fbf8',''),
('23879','{34068}<>{34069} and length({34070})>0','MySQL: Version has changed','','0','1','The MySQL version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','MySQL: Version has changed (new version value received: {ITEM.VALUE})','87b33acf66644972b2a9c7daa4376634',''),
('23884','{34075} > {$PG.CONN_TOTAL_PCT.MAX.WARN}','PostgreSQL: Total number of connections is too high','','0','3','Total number of current connections exceeds the limit of {$PG.CONN_TOTAL_PCT.MAX.WARN}% out of the maximum number of concurrent connections to the database server (the "max_connections" setting).',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Total number of connections is too high (over {$PG.CONN_TOTAL_PCT.MAX.WARN} in 5m)','f07fbe410afa48e6a08da06f4af504c5',''),
('23885','{34076}>0','PostgreSQL: Dbstat: Checksum failures detected','','0','3','Data page checksum failures were detected on that DB instance:\r\nhttps://www.postgresql.org/docs/current/checksums.html',NULL,'0','0','0','','0','','0','','0','','15357041a8774ae19a6cfa64154a4395',''),
('23886','{34077} > 18000000','PostgreSQL: Oldest xid is too big','','0','3','',NULL,'0','0','0','','0','','0','','0','','233757fda5784d9fb264bd0d4a7765ac',''),
('23887','{34078}=0','PostgreSQL: Service is down','','0','4','Last test of a connection was unsuccessful.',NULL,'0','0','0','','0','','0','','0','','ab52bca5bae940cdad5b7eead56f2ff9',''),
('23888','{34079} < 10m','PostgreSQL: Service has been restarted','','0','3','PostgreSQL uptime is less than 10 minutes.',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Service has been restarted (uptime < 10m)','ec3d8fb289234e84b300b83ce169137f',''),
('23889','{34080}<>{34081} and length({34082})>0','PostgreSQL: Version has changed','','0','1','',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Version has changed (new version value received: {ITEM.VALUE})','0d8c3bf10b4e42f796f72136768ce6ab',''),
('23894','{34087} > {$PG.CHECKPOINTS_REQ.MAX.WARN}','PostgreSQL: Required checkpoints occur too frequently','','0','3','Checkpoints are points in the sequence of transactions at which it is guaranteed that the heap and index data files have been updated with all information written before that checkpoint. At checkpoint time, all dirty data pages are flushed to disk and a special checkpoint record is written to the log file.\r\nhttps://www.postgresql.org/docs/current/wal-configuration.html',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Required checkpoints occur too frequently (over {$PG.CHECKPOINTS_REQ.MAX.WARN})','62699d1627fe4141ac59291b138b4f7e',''),
('23895','{34088} = 1','PostgreSQL: Failed to get items','','0','2','Zabbix has not received any data for items for the last 30 minutes.',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Failed to get items (no data for 30m)','33ad0c74e4a34656bd911ebc2920e70a',''),
('23896','{34089} < {$PG.CACHE_HITRATIO.MIN.WARN}','PostgreSQL: Cache hit ratio too low','','0','2','Cache hit ratio is lower than {$PG.CACHE_HITRATIO.MIN.WARN} for 5m.',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Cache hit ratio too low (under {$PG.CACHE_HITRATIO.MIN.WARN} in 5m)','bd2fd99b03b54916963dd661c959dd2f',''),
('23897','{34090}<>{34091} and length({34092})>0','PostgreSQL: Configuration has changed','','0','1','PostgreSQL configuration has changed.',NULL,'0','0','0','','0','','0','','0','','483c370fa82f4c18ac9dbe7b07a4d7ff',''),
('23898','{34093} > {$PG.CONN_TOTAL_PCT.MAX.WARN}','PostgreSQL: Total number of connections is too high','','0','3','Total number of current connections exceeds the limit of {$PG.CONN_TOTAL_PCT.MAX.WARN}% out of the maximum number of concurrent connections to the database server (the "max_connections" setting).',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Total number of connections is too high (over {$PG.CONN_TOTAL_PCT.MAX.WARN} in 5m)','b4673d7606514a6cb5b3ef61b5b05ce1',''),
('23899','{34094} > {$PG.PING_TIME.MAX.WARN}','PostgreSQL: Response too long','','0','3','Response is taking too long (over {$PG.PING_TIME.MAX.WARN} for 5m).',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Response too long (over {$PG.PING_TIME.MAX.WARN})','0b54c409159f494c969c040d295b5cfb',''),
('23900','{34095} = 0','PostgreSQL: Service is down','','0','4','Last test of a connection was unsuccessful.',NULL,'0','0','0','','0','','0','','0','','32a43d55902d46b09f602dc89e3a2586',''),
('23901','{34096} > {$PG.REPL_LAG.MAX.WARN}','PostgreSQL: Streaming lag with master is too high','','0','3','Replication lag with master is higher than {$PG.REPL_LAG.MAX.WARN} for 5m.',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Streaming lag with master is too high (over {$PG.REPL_LAG.MAX.WARN} in 5m)','99adc9f76c0b42a08c22271b9206ce18',''),
('23902','{34097}=0','PostgreSQL: Replication is down','','0','3','Replication is enabled and data streaming was down for 5m.',NULL,'0','0','0','','0','','0','','0','','63b498ebd0484bc59f701e4179ed4fb2',''),
('23903','{34098} < 10m','PostgreSQL: Service has been restarted','','0','3','PostgreSQL uptime is less than 10 minutes.',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Service has been restarted (uptime < 10m)','a7c05ccff4c342018777471d1f3a17b7',''),
('23904','{34099}<>{34100} and length({34101})>0','PostgreSQL: Version has changed','','0','1','',NULL,'0','0','0','','0','','0','','0','PostgreSQL: Version has changed (new version value received: {ITEM.VALUE})','e06391b8cfe74fb5ad3b3bb2718b5e58',''),
('23910','{34107} <> 0','Nvidia: Number of devices has changed','','0','2','Number of devices has changed. Check if this was intentional.',NULL,'0','0','0','','0','','1','current value: {ITEM.LASTVALUE1}','0','Nvidia: Number of devices on {HOST.HOST} has changed.','adf85e5ea2404ef4841208a41ca3bb45',''),
('23911','{34108} <> 0','Nvidia: Driver version has changed','','0','1','Driver version has changed.\r\nCheck the Nvidia website for the specific driver version: https://www.nvidia.com/en-us/drivers/',NULL,'0','0','0','','0','','1','current value: {ITEM.LASTVALUE1}','0','Nvidia: Driver version on {HOST.HOST} has changed.','bd2e26231d1a4ae29538c573e69fce34',''),
('23912','{34109} <> 0','Nvidia: NVML library has changed','','0','1','NVML library version has changed.\r\nCheck the changelog for details: https://docs.nvidia.com/deploy/nvml-api/change-log.html',NULL,'0','0','0','','0','','1','current value: {ITEM.LASTVALUE1}','0','Nvidia: NVML library on {HOST.HOST} has changed.','8db25f54f23f48c4ae2ead4ca3e52c34',''),
('23935','{34135} <> 0','Nvidia: Number of devices has changed','','0','2','Number of devices has changed. Check if this was intentional.',NULL,'0','0','0','','0','','1','current value: {ITEM.LASTVALUE1}','0','Nvidia: Number of devices on {HOST.HOST} has changed.','92b64a9d2e87418a99cd2ca814a2deac',''),
('23936','{34136} <> 0','Nvidia: Driver version has changed','','0','1','Driver version has changed.\r\nCheck the Nvidia website for the specific driver version: https://www.nvidia.com/en-us/drivers/',NULL,'0','0','0','','0','','1','current value: {ITEM.LASTVALUE1}','0','Nvidia: Driver version on {HOST.HOST} has changed.','da8538e357a044ee8ebea1d6d4077ffd',''),
('23937','{34137} <> 0','Nvidia: NVML library has changed','','0','1','NVML library version has changed.\r\nCheck the changelog for details: https://docs.nvidia.com/deploy/nvml-api/change-log.html',NULL,'0','0','0','','0','','1','current value: {ITEM.LASTVALUE1}','0','Nvidia: NVML library on {HOST.HOST} has changed.','1f04a31c99954172a69f2c8529b429ff',''),
('23960','{34163}=1','Azure SQL instance: Azure SQL managed instance is degraded','','0','3','The resource is in a degraded state.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','68d6f9d594f64579a7c6be464e126629',''),
('23961','{34164}=3','Azure SQL instance: Azure SQL managed instance is in unknown state','','0','2','The resource state is unknown.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','9a7ebcccf4684fad8523866fb489e06b',''),
('23962','{34165}=2','Azure SQL instance: Azure SQL managed instance is unavailable','','0','4','The resource state is unavailable.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','4a08e72f744e4a0faee2d2e29714d8b8',''),
('23963','{34166}=1','Azure SQL instance: Instance collation has changed','','0','3','Azure SQL managed instance collation has changed.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','5c8068386b0a47438713d2b4bd54954a',''),
('23964','{34167}>={$AZURE.SQL.INST.CPU.CRIT}','Azure SQL instance: Critically high CPU utilization','','0','3','CPU utilization is critically high.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','Azure SQL instance: Critically high CPU utilization: (over >= {$AZURE.SQL.INST.CPU.CRIT}% over last 10m)','553333ffdbf142539799e7a7b6e8af2b',''),
('23965','{34168}>={$AZURE.SQL.INST.CPU.WARN}','Azure SQL instance: High CPU utilization','','0','2','CPU utilization is too high.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE}','0','Azure SQL instance: High CPU utilization: (over >= {$AZURE.SQL.INST.CPU.WARN}% over last 10m)','7c5876872c644f8598a1fd275d4763d2',''),
('23966','length({34169})>0','Azure SQL instance: 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','','35ec346076ca4c979897e91389d23eb7',''),
('23967','{35812}<>0','Azure SQL instance: Instance provisioning state has changed','','0','2','Azure SQL managed instance provisioning state has changed.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','08a59eccbb854b6db1711c9141231e94',''),
('23968','{34171}=1','Azure SQL instance: Instance state has changed','','0','2','Azure SQL managed instance state has changed.',NULL,'0','0','0','','0','','0','{ITEM.LASTVALUE1}','0','','9a51e2286f354820b89cd0d35586b99a',''),
('23969','{34172}>{$AZURE.SQL.INST.SPACE.CRIT}','Azure SQL instance: Storage free space is critically low','','0','3','The free storage space has been less than `{$AZURE.SQL.INST.SPACE.CRIT}`% for 5m.',NULL,'0','0','0','','0','','1','Space free: {ITEM.LASTVALUE}','0','Azure SQL instance: The free storage space is critically low (below {$AZURE.SQL.INST.SPACE.CRIT}% for 5m)','ed8c37e4f62b471385402e0bcf6cc47e',''),
('23970','{34173}>{$AZURE.SQL.INST.SPACE.WARN}','Azure SQL instance: Storage free space is low','','0','2','The free storage space has been less than `{$AZURE.SQL.INST.SPACE.WARN}`% for 5m.',NULL,'0','0','0','','0','','1','Space free: {ITEM.LASTVALUE}','0','Azure SQL instance: The free storage space is low (below {$AZURE.SQL.INST.SPACE.WARN}% for 5m)','bf8c527a0566490d829ae7654057a1ec',''),
('23971','{34174}=0','Juniper MX: Unavailable by ICMP ping','','0','4','Last three attempts returned timeout. Please check device connectivity.',NULL,'0','0','0','','0','','0','','0','','07752b9c9851403a9ce753fcd122f808',''),
('23972','{34175}>{$JUNIPER.MX.ICMP_LOSS_WARN} and {34175}<100','Juniper MX: High ICMP ping loss','','0','2','ICMP packet loss detected.',NULL,'0','0','0','','0','','0','Loss: {ITEM.LASTVALUE1}','0','Juniper MX: High ICMP ping loss (over {$JUNIPER.MX.ICMP_LOSS_WARN}% for 5m)','e4cc0c30ff1544d68adfe9f3863e0f19',''),
('23973','{34176}>{$JUNIPER.MX.ICMP_RESPONSE_TIME_WARN}','Juniper MX: High ICMP ping response time','','0','2','Average ICMP response time is too high.',NULL,'0','0','0','','0','','0','Value: {ITEM.LASTVALUE1}','0','Juniper MX: High ICMP ping response time (over {$JUNIPER.MX.ICMP_RESPONSE_TIME_WARN}s for 5m)','d573e7a77408476e854de2e556480acc',''),
('23974','{34177}<>{34178} and length({34179})>0','Juniper MX: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Juniper MX: Device has been replaced (new serial number received)','317bc72900e24f4991798775b48bc641',''),
('23975','{34180}<>{34181} and length({34182})>0','Juniper MX: 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 MX: System name has changed (new name: {ITEM.VALUE})','faec7813bfc14e5da59bfaf7ad639461',''),
('23976','{34183}<>{34184} and length({34185})>0','Juniper MX: Operating system description has changed','','0','1','Operating system description has changed. Possible reasons - system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','007d3cb1343144cc9ee01d24df45082d',''),
('23977','{34186}=0','Juniper MX: 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','','a30f49e7b715409abec697f303ccc46c',''),
('23978','({34187}>0 and {34187}<10m) or ({34187}=0 and {34188}<10m)','Juniper MX: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Juniper MX: {HOST.NAME} has been restarted (uptime < 10m)','4882bb9496ac40bc97c3c5278c0181c8',''),
('24006','length({34233})>0','PA-440: Failed to get device certificate data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','44ab6b7c72bd4ccbbab3daed1f229417',''),
('24007','length({34234})>0','PA-440: Failed to get certificate data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','a323a25e3808440ab38b412b62e14300',''),
('24008','length({34235})>0','PA-440: Failed to get environmental data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','c9ba92783cb74e64817790ff25e710d4',''),
('24009','length({34236})>0','PA-440: Failed to get HA data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','ed84f048159a47dc8b839d00c339cfc3',''),
('24010','length({34237})>0','PA-440: Failed to get license data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','475e2a36b81840cd9f4c4eb1f9d12109',''),
('24011','length({34238})>0','PA-440: Failed to get OSPF neighbor data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','b828df38af09484c8ed6c9fd726f8757',''),
('24012','length({34239})>0','PA-440: Failed to get OSPFv3 neighbor data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','c879700d2fc84426907962068eae225f',''),
('24013','length({34240})>0','PA-440: Failed to get session info data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','d7577936d64a4e7b9e62868dacce625d',''),
('24014','length({34241})>0','PA-440: Failed to get system info data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','38cd1ff8e5494e93a40662b9306c0807',''),
('24015','length({34242})>0','PA-440: Failed to get system state data from the API','','0','4','Failed to get data from the API. Check the latest values for details.',NULL,'0','0','0','','0','','0','','0','','920dc027510941a38648816064d8bf18',''),
('24037','{34275}<>{34276} and length({34277})>0','Dell R660: Firmware has changed','','0','1','The firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','e6688a178fab46d59cc685a223767a12',''),
('24038','{34278}<>{34279} and length({34280})>0','Dell R660: 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','Dell R660: Device has been replaced (new serial number received)','62ece039dea440c7999f0b93bc32c40a',''),
('24039','{34281}=3','Dell R660: Server is in a critical state','','0','3','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','2ccd53402fea446283e24ebfe5b32bdd',''),
('24040','{34282}=2','Dell R660: Server is in a warning state','','0','2','Please check the device for warnings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d9c93ee01d284b319cdc1acc6919b834',''),
('24041','{34283}>={$DELL.HTTP.CPU.UTIL.WARN}','Dell R660: CPU utilization is high','','0','2','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R660: Current CPU utilization is high (util >= {$DELL.HTTP.CPU.UTIL.WARN}%)','d342f09969114891ae47b50e6e03aa80',''),
('24042','{34284}>={$DELL.HTTP.CPU.UTIL.HIGH}','Dell R660: CPU utilization is too high','','0','4','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R660: Current CPU utilization is too high (util >= {$DELL.HTTP.CPU.UTIL.HIGH}%)','7e5960ded30e450a89a153ef1612b03e',''),
('24043','{34285}>={$DELL.HTTP.IO.UTIL.WARN}','Dell R660: IO utilization is high','','0','2','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R660: Current IO utilization is high (util >= {$DELL.HTTP.IO.UTIL.WARN}%)','1fe2219883964e9d9db2fbc83a62f854',''),
('24044','{34286}>={$DELL.HTTP.IO.UTIL.HIGH}','Dell R660: IO utilization is too high','','0','4','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R660: Current IO utilization is too high (util >= {$DELL.HTTP.IO.UTIL.HIGH}%)','eab83e0592ec4de7b219ae8a7e9eb54c',''),
('24045','{34287}>={$DELL.HTTP.MEM.UTIL.WARN}','Dell R660: Memory utilization is high','','0','2','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R660: Current memory utilization is high (util >= {$DELL.HTTP.MEM.UTIL.WARN}%)','9f3501907030474580f28cbd602eb951',''),
('24046','{34288}>={$DELL.HTTP.MEM.UTIL.HIGH}','Dell R660: Memory utilization is too high','','0','4','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R660: Current memory utilization is too high (util >= {$DELL.HTTP.MEM.UTIL.HIGH}%)','886fcdda4b7847fb9364d6c2f807641e',''),
('24047','{34289}>={$DELL.HTTP.SYS.UTIL.WARN}','Dell R660: SYS utilization is high','','0','2','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R660: Current SYS utilization is high (util >= {$DELL.HTTP.SYS.UTIL.WARN}%)','b9d668629940497dbf06e212f297dc2a',''),
('24048','{34290}>={$DELL.HTTP.SYS.UTIL.HIGH}','Dell R660: SYS utilization is too high','','0','4','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R660: Current SYS utilization is too high (util >= {$DELL.HTTP.SYS.UTIL.HIGH}%)','be2e13c07a894816b6566101e31d017b',''),
('24049','{34291}=0','Dell R660: Redfish API service is unavailable','','0','4','The service is unavailable or does not accept TCP connections.',NULL,'0','0','0','','0','','0','','0','','28d07a7c2c914523b40d46bc8a19764a',''),
('24072','{34320}<>{34321} and length({34322})>0','Dell R660: 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','','06ad53c66cf241d285dd0e4a19b30105',''),
('24073','{34323}<>{34324} and length({34325})>0','Dell R660: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Dell R660: Device has been replaced (new serial number received)','ab50b7de4a004c1bb8bae012e87a9fae',''),
('24074','{34326}>0','Dell R660: Memory amount has changed','','0','3','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','9f583d671b3842798f0bd4d50d395c6e',''),
('24075','{34327}<>{34328} and length({34329})>0','Dell R660: 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 R660: System name has changed (new name: {ITEM.VALUE})','59cb6156e1f84f0fb28beb51a8046da3',''),
('24076','{34330}={$DELL.SNMP.HEALTH.STATUS.DISASTER}','Dell R660: System is in unrecoverable state','','0','4','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','81762ad908ba492c897572f690606da3',''),
('24077','{34331}={$DELL.SNMP.HEALTH.STATUS.CRIT}','Dell R660: System status is in critical state','','0','3','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','04c60944973d402b9d3a0e96049c42ad',''),
('24078','{34332}={$DELL.SNMP.HEALTH.STATUS.WARN}','Dell R660: 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','','31fbf1a98d0646bd9082efc946e2a424',''),
('24079','{34333}<>{34334} and length({34335})>0','Dell R660: Operating system description has changed','','0','1','Operating system description has changed. Possibly, the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','d76ca22d7fd742efb84e04940fa9a846',''),
('24080','{34336}=0','Dell R660: 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','','b7121bb9605148c299aa571ae0baaeac',''),
('24081','({34337}>0 and {34337}<10m) or ({34337}=0 and {34338}<10m)','Dell R660: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Dell R660: {HOST.NAME} has been restarted (uptime < 10m)','0c72f52ac52c46adab21c577c27381b1',''),
('24108','{34368}<>{34369} and length({34370})>0','Dell R720: Firmware has changed','','0','1','The firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','769dd4e6283f4e1e8a4c9271006f7123',''),
('24109','{34371}<>{34372} and length({34373})>0','Dell R720: 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','Dell R720: Device has been replaced (new serial number received)','32a56bf761a24da5966512e13741824c',''),
('24110','{34374}=3','Dell R720: Server is in a critical state','','0','3','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','231b61c2570141f1bae1a3ccd9083de5',''),
('24111','{34375}=2','Dell R720: Server is in a warning state','','0','2','Please check the device for warnings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','cac71a4bfffa4d87a15280fcbec67672',''),
('24112','{34376}>={$DELL.HTTP.CPU.UTIL.WARN}','Dell R720: CPU utilization is high','','0','2','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R720: Current CPU utilization is high (util >= {$DELL.HTTP.CPU.UTIL.WARN}%)','4ae5ed40c7ac4a4990f10afb0c578301',''),
('24113','{34377}>={$DELL.HTTP.CPU.UTIL.HIGH}','Dell R720: CPU utilization is too high','','0','4','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R720: Current CPU utilization is too high (util >= {$DELL.HTTP.CPU.UTIL.HIGH}%)','5d20edd65b914aadb3354b13d52f417f',''),
('24114','{34378}>={$DELL.HTTP.IO.UTIL.WARN}','Dell R720: IO utilization is high','','0','2','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R720: Current IO utilization is high (util >= {$DELL.HTTP.IO.UTIL.WARN}%)','6a345bd704aa4b719399125716967468',''),
('24115','{34379}>={$DELL.HTTP.IO.UTIL.HIGH}','Dell R720: IO utilization is too high','','0','4','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R720: Current IO utilization is too high (util >= {$DELL.HTTP.IO.UTIL.HIGH}%)','6d2c8ef6746d42299ffc53e0f837e095',''),
('24116','{34380}>={$DELL.HTTP.MEM.UTIL.WARN}','Dell R720: Memory utilization is high','','0','2','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R720: Current memory utilization is high (util >= {$DELL.HTTP.MEM.UTIL.WARN}%)','8640e51d349b427a9d57923236c4036f',''),
('24117','{34381}>={$DELL.HTTP.MEM.UTIL.HIGH}','Dell R720: Memory utilization is too high','','0','4','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R720: Current memory utilization is too high (util >= {$DELL.HTTP.MEM.UTIL.HIGH}%)','f91f48c6bfc5482c8813c5830807640e',''),
('24118','{34382}>={$DELL.HTTP.SYS.UTIL.WARN}','Dell R720: SYS utilization is high','','0','2','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R720: Current SYS utilization is high (util >= {$DELL.HTTP.SYS.UTIL.WARN}%)','da48f40dafd44f788bfd9c87896273d9',''),
('24119','{34383}>={$DELL.HTTP.SYS.UTIL.HIGH}','Dell R720: SYS utilization is too high','','0','4','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R720: Current SYS utilization is too high (util >= {$DELL.HTTP.SYS.UTIL.HIGH}%)','94d3375fe9af4d57b9542cd877546b02',''),
('24120','{34384}=0','Dell R720: Redfish API service is unavailable','','0','4','The service is unavailable or does not accept TCP connections.',NULL,'0','0','0','','0','','0','','0','','1a85b9c93c644fd98183df4fbda3a01f',''),
('24143','{34413}<>{34414} and length({34415})>0','Dell R720: 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','','46c22d9eca174756903b8c26ec69c792',''),
('24144','{34416}<>{34417} and length({34418})>0','Dell R720: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Dell R720: Device has been replaced (new serial number received)','1e3f0933fae74fc29c13177fe2cf6903',''),
('24145','{34419}>0','Dell R720: Memory amount has changed','','0','3','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','deb6d163f8824e489d9e64674d648d80',''),
('24146','{34420}<>{34421} and length({34422})>0','Dell R720: 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 R720: System name has changed (new name: {ITEM.VALUE})','12327b9851254d28b1db193fbca51f9a',''),
('24147','{34423}={$DELL.SNMP.HEALTH.STATUS.DISASTER}','Dell R720: System is in unrecoverable state','','0','4','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','7b6bbbaf7a6f4ba084e812fc98aee033',''),
('24148','{34424}={$DELL.SNMP.HEALTH.STATUS.CRIT}','Dell R720: System status is in critical state','','0','3','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','51bd134f73234388b1c9522468b73883',''),
('24149','{34425}={$DELL.SNMP.HEALTH.STATUS.WARN}','Dell R720: 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','','e026d877c5e540b9ae06d44874e7ec5d',''),
('24150','{34426}<>{34427} and length({34428})>0','Dell R720: Operating system description has changed','','0','1','Operating system description has changed. Possibly, the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','2e07d3f10a114360b4189e47cfd777f8',''),
('24151','{34429}=0','Dell R720: 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','','f0b0662e38cd4aa6893dc3b5f89b9c81',''),
('24152','({34430}>0 and {34430}<10m) or ({34430}=0 and {34431}<10m)','Dell R720: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Dell R720: {HOST.NAME} has been restarted (uptime < 10m)','03411617acad4aeb8ddcb5e873ae1b73',''),
('24179','{34461}<>{34462} and length({34463})>0','Dell R740: Firmware has changed','','0','1','The firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','e25c62f68b3f4c53a0680b651e99cdc7',''),
('24180','{34464}<>{34465} and length({34466})>0','Dell R740: 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','Dell R740: Device has been replaced (new serial number received)','99d9055edb1a486cbfd064b794b37450',''),
('24181','{34467}=3','Dell R740: Server is in a critical state','','0','3','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','99ebb04c198c4ce4ba5bb1eabe186d97',''),
('24182','{34468}=2','Dell R740: Server is in a warning state','','0','2','Please check the device for warnings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','c36399ae3aef4f18944a92ecc539371d',''),
('24183','{34469}>={$DELL.HTTP.CPU.UTIL.WARN}','Dell R740: CPU utilization is high','','0','2','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R740: Current CPU utilization is high (util >= {$DELL.HTTP.CPU.UTIL.WARN}%)','acfc613fa7ef4aea8673fa9804804480',''),
('24184','{34470}>={$DELL.HTTP.CPU.UTIL.HIGH}','Dell R740: CPU utilization is too high','','0','4','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R740: Current CPU utilization is too high (util >= {$DELL.HTTP.CPU.UTIL.HIGH}%)','a65d0e094829439da83b403d0373ad6c',''),
('24185','{34471}>={$DELL.HTTP.IO.UTIL.WARN}','Dell R740: IO utilization is high','','0','2','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R740: Current IO utilization is high (util >= {$DELL.HTTP.IO.UTIL.WARN}%)','a0912c7c62b342bbabc74fda99908c4e',''),
('24186','{34472}>={$DELL.HTTP.IO.UTIL.HIGH}','Dell R740: IO utilization is too high','','0','4','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R740: Current IO utilization is too high (util >= {$DELL.HTTP.IO.UTIL.HIGH}%)','c94f37d12fa9446a81095caaf68e4c70',''),
('24187','{34473}>={$DELL.HTTP.MEM.UTIL.WARN}','Dell R740: Memory utilization is high','','0','2','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R740: Current memory utilization is high (util >= {$DELL.HTTP.MEM.UTIL.WARN}%)','52c7a1c084f545b58ede5a24b06d0dda',''),
('24188','{34474}>={$DELL.HTTP.MEM.UTIL.HIGH}','Dell R740: Memory utilization is too high','','0','4','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R740: Current memory utilization is too high (util >= {$DELL.HTTP.MEM.UTIL.HIGH}%)','25d4b9b8fb244d58ab805e6f18ab3581',''),
('24189','{34475}>={$DELL.HTTP.SYS.UTIL.WARN}','Dell R740: SYS utilization is high','','0','2','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R740: Current SYS utilization is high (util >= {$DELL.HTTP.SYS.UTIL.WARN}%)','2813184ff5c44f128233860941ffe75b',''),
('24190','{34476}>={$DELL.HTTP.SYS.UTIL.HIGH}','Dell R740: SYS utilization is too high','','0','4','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R740: Current SYS utilization is too high (util >= {$DELL.HTTP.SYS.UTIL.HIGH}%)','d29b786246364813a98664d892e1189b',''),
('24191','{34477}=0','Dell R740: Redfish API service is unavailable','','0','4','The service is unavailable or does not accept TCP connections.',NULL,'0','0','0','','0','','0','','0','','abc84a9051bc411eab4481b539e58f5c',''),
('24214','{34506}<>{34507} and length({34508})>0','Dell R740: 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','','b77eee80359e4fac87d36257d8adc38a',''),
('24215','{34509}<>{34510} and length({34511})>0','Dell R740: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Dell R740: Device has been replaced (new serial number received)','0610dd019a64431f954a41b58e34e0a1',''),
('24216','{34512}>0','Dell R740: Memory amount has changed','','0','3','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','1b12170aa1dd4b278e887bd20d3a7f00',''),
('24217','{34513}<>{34514} and length({34515})>0','Dell R740: 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 R740: System name has changed (new name: {ITEM.VALUE})','bc5e7a8b73b6425d9ba59c7c1bb44276',''),
('24218','{34516}={$DELL.SNMP.HEALTH.STATUS.DISASTER}','Dell R740: System is in unrecoverable state','','0','4','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','85a8a9c18082436d8fedeebfca0b7173',''),
('24219','{34517}={$DELL.SNMP.HEALTH.STATUS.CRIT}','Dell R740: System status is in critical state','','0','3','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','f0cf8ea9011443b5bdb6cc92af5e63fb',''),
('24220','{34518}={$DELL.SNMP.HEALTH.STATUS.WARN}','Dell R740: 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','','9fe1bfd6ae724365b5ce13edf0dc8823',''),
('24221','{34519}<>{34520} and length({34521})>0','Dell R740: Operating system description has changed','','0','1','Operating system description has changed. Possibly, the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','6dc4593b42f341799eac23ee792f765d',''),
('24222','{34522}=0','Dell R740: 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','','c743348ae566468d93ac23508511443d',''),
('24223','({34523}>0 and {34523}<10m) or ({34523}=0 and {34524}<10m)','Dell R740: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Dell R740: {HOST.NAME} has been restarted (uptime < 10m)','88a6132f78a24d8ca66e8759526c2381',''),
('24250','{34554}<>{34555} and length({34556})>0','Dell R750: Firmware has changed','','0','1','The firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','479b1531bed7454d97773967e23d53f1',''),
('24251','{34557}<>{34558} and length({34559})>0','Dell R750: 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','Dell R750: Device has been replaced (new serial number received)','5c1ca8b9ce8146b2a7184e8e9b5f2eeb',''),
('24252','{34560}=3','Dell R750: Server is in a critical state','','0','3','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','71471cc70f114c43adec7410a9c76d16',''),
('24253','{34561}=2','Dell R750: Server is in a warning state','','0','2','Please check the device for warnings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','ca10f6c7deda4c64b5bcc5db15d0a9c5',''),
('24254','{34562}>={$DELL.HTTP.CPU.UTIL.WARN}','Dell R750: CPU utilization is high','','0','2','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R750: Current CPU utilization is high (util >= {$DELL.HTTP.CPU.UTIL.WARN}%)','3da411d4c9324ece8e54a7eb841a0b00',''),
('24255','{34563}>={$DELL.HTTP.CPU.UTIL.HIGH}','Dell R750: CPU utilization is too high','','0','4','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R750: Current CPU utilization is too high (util >= {$DELL.HTTP.CPU.UTIL.HIGH}%)','25ef27dc6f954cf684df80a45b82cb65',''),
('24256','{34564}>={$DELL.HTTP.IO.UTIL.WARN}','Dell R750: IO utilization is high','','0','2','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R750: Current IO utilization is high (util >= {$DELL.HTTP.IO.UTIL.WARN}%)','96bf746590ef41c5b4eb13e4b5775804',''),
('24257','{34565}>={$DELL.HTTP.IO.UTIL.HIGH}','Dell R750: IO utilization is too high','','0','4','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R750: Current IO utilization is too high (util >= {$DELL.HTTP.IO.UTIL.HIGH}%)','04bb737e97e7462ab0b226169191eb86',''),
('24258','{34566}>={$DELL.HTTP.MEM.UTIL.WARN}','Dell R750: Memory utilization is high','','0','2','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R750: Current memory utilization is high (util >= {$DELL.HTTP.MEM.UTIL.WARN}%)','c942008a07a140f5b2fc1552f190b240',''),
('24259','{34567}>={$DELL.HTTP.MEM.UTIL.HIGH}','Dell R750: Memory utilization is too high','','0','4','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R750: Current memory utilization is too high (util >= {$DELL.HTTP.MEM.UTIL.HIGH}%)','519ccd1746f84716848732a24d6c6adc',''),
('24260','{34568}>={$DELL.HTTP.SYS.UTIL.WARN}','Dell R750: SYS utilization is high','','0','2','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R750: Current SYS utilization is high (util >= {$DELL.HTTP.SYS.UTIL.WARN}%)','ad3b33164e5c44489b0a58824de01948',''),
('24261','{34569}>={$DELL.HTTP.SYS.UTIL.HIGH}','Dell R750: SYS utilization is too high','','0','4','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R750: Current SYS utilization is too high (util >= {$DELL.HTTP.SYS.UTIL.HIGH}%)','39ffa53a535a41a5b6143b09afd2e04d',''),
('24262','{34570}=0','Dell R750: Redfish API service is unavailable','','0','4','The service is unavailable or does not accept TCP connections.',NULL,'0','0','0','','0','','0','','0','','5cb42d522d814335861831685b6a5e4a',''),
('24285','{34599}<>{34600} and length({34601})>0','Dell R750: 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','','3cb240c2c5884c448a7ac399412dc00c',''),
('24286','{34602}<>{34603} and length({34604})>0','Dell R750: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Dell R750: Device has been replaced (new serial number received)','7e6fb4f6552d4643babba3d650f00c18',''),
('24287','{34605}>0','Dell R750: Memory amount has changed','','0','3','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','2f2f224a7ce3481eb04fd5c62530a57d',''),
('24288','{34606}<>{34607} and length({34608})>0','Dell R750: 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 R750: System name has changed (new name: {ITEM.VALUE})','45b605bae5bd4bfa8c7ab042a3bde257',''),
('24289','{34609}={$DELL.SNMP.HEALTH.STATUS.DISASTER}','Dell R750: System is in unrecoverable state','','0','4','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','58beec6c28a5424a862d427588b74207',''),
('24290','{34610}={$DELL.SNMP.HEALTH.STATUS.CRIT}','Dell R750: System status is in critical state','','0','3','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','652439f2023d46bf8ba84d8ac0154ee2',''),
('24291','{34611}={$DELL.SNMP.HEALTH.STATUS.WARN}','Dell R750: 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','','9702a49ff2034f3b98892d93c1060ff1',''),
('24292','{34612}<>{34613} and length({34614})>0','Dell R750: Operating system description has changed','','0','1','Operating system description has changed. Possibly, the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','2c37e6ae35404da199844a685b2ed28f',''),
('24293','{34615}=0','Dell R750: 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','','22caee353f3f4b74a150f8144f73eab2',''),
('24294','({34616}>0 and {34616}<10m) or ({34616}=0 and {34617}<10m)','Dell R750: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Dell R750: {HOST.NAME} has been restarted (uptime < 10m)','0eb0e7489c6a4e6b8a44fc2eae500006',''),
('24321','{34647}<>{34648} and length({34649})>0','Dell R820: Firmware has changed','','0','1','The firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','16d23330f3274801b7ad216aae251587',''),
('24322','{34650}<>{34651} and length({34652})>0','Dell R820: 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','Dell R820: Device has been replaced (new serial number received)','0ace6d0242b647519ddc539e990e2b75',''),
('24323','{34653}=3','Dell R820: Server is in a critical state','','0','3','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','df55250997fd474e8323ccf7438354f8',''),
('24324','{34654}=2','Dell R820: Server is in a warning state','','0','2','Please check the device for warnings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','f805d7fdab4842018b68acf3608fbfc4',''),
('24325','{34655}>={$DELL.HTTP.CPU.UTIL.WARN}','Dell R820: CPU utilization is high','','0','2','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R820: Current CPU utilization is high (util >= {$DELL.HTTP.CPU.UTIL.WARN}%)','1feff28d5dd74c52a3978645f7cecd62',''),
('24326','{34656}>={$DELL.HTTP.CPU.UTIL.HIGH}','Dell R820: CPU utilization is too high','','0','4','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R820: Current CPU utilization is too high (util >= {$DELL.HTTP.CPU.UTIL.HIGH}%)','069d0f8e16a1494d99bd45b96040ef12',''),
('24327','{34657}>={$DELL.HTTP.IO.UTIL.WARN}','Dell R820: IO utilization is high','','0','2','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R820: Current IO utilization is high (util >= {$DELL.HTTP.IO.UTIL.WARN}%)','0646200e61a7469c95471af24ddba10c',''),
('24328','{34658}>={$DELL.HTTP.IO.UTIL.HIGH}','Dell R820: IO utilization is too high','','0','4','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R820: Current IO utilization is too high (util >= {$DELL.HTTP.IO.UTIL.HIGH}%)','f99ead65893143c39f0ebe9c1038524d',''),
('24329','{34659}>={$DELL.HTTP.MEM.UTIL.WARN}','Dell R820: Memory utilization is high','','0','2','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R820: Current memory utilization is high (util >= {$DELL.HTTP.MEM.UTIL.WARN}%)','cd8f662e308f4c0ea7382962a0889812',''),
('24330','{34660}>={$DELL.HTTP.MEM.UTIL.HIGH}','Dell R820: Memory utilization is too high','','0','4','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R820: Current memory utilization is too high (util >= {$DELL.HTTP.MEM.UTIL.HIGH}%)','606b2c5625d844bb8a5641e351ab30fc',''),
('24331','{34661}>={$DELL.HTTP.SYS.UTIL.WARN}','Dell R820: SYS utilization is high','','0','2','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R820: Current SYS utilization is high (util >= {$DELL.HTTP.SYS.UTIL.WARN}%)','71a95d655db24c13b7ed1e89adf7cb43',''),
('24332','{34662}>={$DELL.HTTP.SYS.UTIL.HIGH}','Dell R820: SYS utilization is too high','','0','4','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R820: Current SYS utilization is too high (util >= {$DELL.HTTP.SYS.UTIL.HIGH}%)','c3bfbc51feb54025a32d0a7e43cf9a7c',''),
('24333','{34663}=0','Dell R820: Redfish API service is unavailable','','0','4','The service is unavailable or does not accept TCP connections.',NULL,'0','0','0','','0','','0','','0','','f60ee17e012e4db39d3b2a008cf86653',''),
('24356','{34692}<>{34693} and length({34694})>0','Dell R820: 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','','bf0330b9e03c40b3a8aa4f799ab4d677',''),
('24357','{34695}<>{34696} and length({34697})>0','Dell R820: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Dell R820: Device has been replaced (new serial number received)','85fc427d143b4bd784fc851464e30c60',''),
('24358','{34698}>0','Dell R820: Memory amount has changed','','0','3','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','d7121d536e9e472e84ed8521c66dc63b',''),
('24359','{34699}<>{34700} and length({34701})>0','Dell R820: 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 R820: System name has changed (new name: {ITEM.VALUE})','34d5734804fd4e28960e76d85b26230b',''),
('24360','{34702}={$DELL.SNMP.HEALTH.STATUS.DISASTER}','Dell R820: System is in unrecoverable state','','0','4','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','4109ee28d6d54d568965c21fc147791c',''),
('24361','{34703}={$DELL.SNMP.HEALTH.STATUS.CRIT}','Dell R820: System status is in critical state','','0','3','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','126c5d57fecc4785b1f620c413c5dd12',''),
('24362','{34704}={$DELL.SNMP.HEALTH.STATUS.WARN}','Dell R820: 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','','da0537de8fdb4cff88cd19ec031cf562',''),
('24363','{34705}<>{34706} and length({34707})>0','Dell R820: Operating system description has changed','','0','1','Operating system description has changed. Possibly, the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','b6a26d0134054b75b88dbcfcd3dc8d3c',''),
('24364','{34708}=0','Dell R820: 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','','81826abcb02d45b089024c47892bc52f',''),
('24365','({34709}>0 and {34709}<10m) or ({34709}=0 and {34710}<10m)','Dell R820: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Dell R820: {HOST.NAME} has been restarted (uptime < 10m)','75be35da1fa9433081562ce9c02af907',''),
('24392','{34740}<>{34741} and length({34742})>0','Dell R840: Firmware has changed','','0','1','The firmware version has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','Current value: {ITEM.LASTVALUE1}','0','','d69a362c4ddb41afac0233aa5cbfe7f2',''),
('24393','{34743}<>{34744} and length({34745})>0','Dell R840: 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','Dell R840: Device has been replaced (new serial number received)','7d3b78a42b2840dcac53aaad6fe0fd63',''),
('24394','{34746}=3','Dell R840: Server is in a critical state','','0','3','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','66eddf4db30c4f33a04fd1e7779a512b',''),
('24395','{34747}=2','Dell R840: Server is in a warning state','','0','2','Please check the device for warnings.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','d7bd59c648884a2db4e40518c80e9a7a',''),
('24396','{34748}>={$DELL.HTTP.CPU.UTIL.WARN}','Dell R840: CPU utilization is high','','0','2','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R840: Current CPU utilization is high (util >= {$DELL.HTTP.CPU.UTIL.WARN}%)','d043506ca50e46688f4e2b5d16fbb6b0',''),
('24397','{34749}>={$DELL.HTTP.CPU.UTIL.HIGH}','Dell R840: CPU utilization is too high','','0','4','Current CPU utilization has exceeded `{$DELL.HTTP.CPU.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R840: Current CPU utilization is too high (util >= {$DELL.HTTP.CPU.UTIL.HIGH}%)','7402c280344d4d1481dc4f9363b114cb',''),
('24398','{34750}>={$DELL.HTTP.IO.UTIL.WARN}','Dell R840: IO utilization is high','','0','2','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R840: Current IO utilization is high (util >= {$DELL.HTTP.IO.UTIL.WARN}%)','9d9b98ba6f0f4a09b0fe866ac75a45d9',''),
('24399','{34751}>={$DELL.HTTP.IO.UTIL.HIGH}','Dell R840: IO utilization is too high','','0','4','Current IO utilization has exceeded `{$DELL.HTTP.IO.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R840: Current IO utilization is too high (util >= {$DELL.HTTP.IO.UTIL.HIGH}%)','6458115ca51b4f82a00f9f70f081168b',''),
('24400','{34752}>={$DELL.HTTP.MEM.UTIL.WARN}','Dell R840: Memory utilization is high','','0','2','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R840: Current memory utilization is high (util >= {$DELL.HTTP.MEM.UTIL.WARN}%)','108975d790e84418852a3918ca9c721c',''),
('24401','{34753}>={$DELL.HTTP.MEM.UTIL.HIGH}','Dell R840: Memory utilization is too high','','0','4','Current memory utilization has exceeded `{$DELL.HTTP.MEM.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R840: Current memory utilization is too high (util >= {$DELL.HTTP.MEM.UTIL.HIGH}%)','28dbce9e2c374351853bce93a4d45533',''),
('24402','{34754}>={$DELL.HTTP.SYS.UTIL.WARN}','Dell R840: SYS utilization is high','','0','2','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.WARN}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R840: Current SYS utilization is high (util >= {$DELL.HTTP.SYS.UTIL.WARN}%)','4914f2bb5add4d1e879bd98e723cba68',''),
('24403','{34755}>={$DELL.HTTP.SYS.UTIL.HIGH}','Dell R840: SYS utilization is too high','','0','4','Current SYS utilization has exceeded `{$DELL.HTTP.SYS.UTIL.HIGH}`%.',NULL,'0','0','0','','0','','0','Current utilization: {ITEM.LASTVALUE1}','0','Dell R840: Current SYS utilization is too high (util >= {$DELL.HTTP.SYS.UTIL.HIGH}%)','32dc9d0ef93649aaa05b80c1681ebd00',''),
('24404','{34756}=0','Dell R840: Redfish API service is unavailable','','0','4','The service is unavailable or does not accept TCP connections.',NULL,'0','0','0','','0','','0','','0','','890f7b925b324a9c8ddcbf900248983f',''),
('24427','{34785}<>{34786} and length({34787})>0','Dell R840: 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','','26f924a3a9e1470891cb0d9e9136ad9d',''),
('24428','{34788}<>{34789} and length({34790})>0','Dell R840: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Dell R840: Device has been replaced (new serial number received)','8d1e926bb5f640b4bf8c8342b5cf1d56',''),
('24429','{34791}>0','Dell R840: Memory amount has changed','','0','3','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','c44165ebea1346c78970c1f8d96da0be',''),
('24430','{34792}<>{34793} and length({34794})>0','Dell R840: 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 R840: System name has changed (new name: {ITEM.VALUE})','673eda315d9b4dfcb15509fa01fffac2',''),
('24431','{34795}={$DELL.SNMP.HEALTH.STATUS.DISASTER}','Dell R840: System is in unrecoverable state','','0','4','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','c3e8fd8fd0d0406d8c2d9a2c45eeecee',''),
('24432','{34796}={$DELL.SNMP.HEALTH.STATUS.CRIT}','Dell R840: System status is in critical state','','0','3','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','4b32809fad0e468bb5f1bd09c7078def',''),
('24433','{34797}={$DELL.SNMP.HEALTH.STATUS.WARN}','Dell R840: 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','','a75745134dad4592a23c43ca77975d95',''),
('24434','{34798}<>{34799} and length({34800})>0','Dell R840: Operating system description has changed','','0','1','Operating system description has changed. Possibly, the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','4096c84c616743bfbfca9707e43a3db3',''),
('24435','{34801}=0','Dell R840: 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','','6f00331597c0443a93c182a86040cca4',''),
('24436','({34802}>0 and {34802}<10m) or ({34802}=0 and {34803}<10m)','Dell R840: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Dell R840: {HOST.NAME} has been restarted (uptime < 10m)','93a63868ca09460e89d3f40f72259828',''),
('24463','{34833}<>{34834} and length({34835})>0','Dell iDRAC: 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','','480535363667492389588bf2e66a69d4',''),
('24464','{34836}<>{34837} and length({34838})>0','Dell iDRAC: Device has been replaced','','0','1','Device serial number has changed. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','Dell iDRAC: Device has been replaced (new serial number received)','a4ad832c9a174442913b4b08b38eee83',''),
('24465','{34839}>0','Dell iDRAC: Memory amount has changed','','0','3','',NULL,'0','0','0','','0','','0','Current value: {ITEM.LASTVALUE1}','0','','05bd4537d8b84a028658a9abbe9ab292',''),
('24466','{34840}<>{34841} and length({34842})>0','Dell iDRAC: 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 iDRAC: System name has changed (new name: {ITEM.VALUE})','d10fc658e7324deaa5318f69d6161a88',''),
('24467','{34843}={$DELL.SNMP.HEALTH.STATUS.DISASTER}','Dell iDRAC: System is in unrecoverable state','','0','4','Please check the device for faults.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','c602802bb6f549e383832bc98c0b55dd',''),
('24468','{34844}={$DELL.SNMP.HEALTH.STATUS.CRIT}','Dell iDRAC: System status is in critical state','','0','3','Please check the device for errors.',NULL,'0','0','0','','0','','0','Current state: {ITEM.LASTVALUE1}','0','','4e6d3cd166454403a9113fcb8aac9330',''),
('24469','{34845}={$DELL.SNMP.HEALTH.STATUS.WARN}','Dell iDRAC: 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','','2b7b4a8610d9417c87fb620f5a8dc32b',''),
('24470','{34846}<>{34847} and length({34848})>0','Dell iDRAC: Operating system description has changed','','0','1','Operating system description has changed. Possibly, the system has been updated or replaced. Acknowledge to close the problem manually.',NULL,'0','0','0','','0','','1','','0','','b724627a28704440aedb965cbacd7e66',''),
('24471','{34849}=0','Dell iDRAC: 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','','cffe4af5209841119605e7a82e9a8429',''),
('24472','({34850}>0 and {34850}<10m) or ({34850}=0 and {34851}<10m)','Dell iDRAC: Host has been restarted','','0','2','Uptime is less than 10 minutes.',NULL,'0','0','0','','0','','1','','0','Dell iDRAC: {HOST.NAME} has been restarted (uptime < 10m)','e9fc724fff1840a9931ef9d379475349',''),
('24499','{34882}=1','Zabbix proxy: Wrong template assigned','','0','5','Check that the template has been selected correctly.',NULL,'0','0','0','','0','','1','','0','Zabbix proxy: Zabbix proxy template is assigned to Zabbix server','7c54b686ce754537b7f379ec1af4e630',''),
('24500','{34883}=1','Zabbix proxy: Wrong template assigned','','0','5','Check that the template has been selected correctly.',NULL,'0','0','0','','0','','1','','0','Zabbix proxy: Zabbix proxy template is assigned to Zabbix server','714e140b408d4b219fbee840e800b841',''),
('24501','{34884}>{$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','{34884}<{$ZABBIX.PROXY.UTIL.MIN:"agent poller"}','0','','0','','0','Zabbix proxy: Utilization of agent poller processes over {$ZABBIX.PROXY.UTIL.MAX:"agent poller"}%','2bc7af614177457381d7dac14073b167',''),
('24502','{34885}>{$ZABBIX.PROXY.UTIL.MAX:"availability manager"}','Zabbix proxy: Utilization of availability manager processes is high','','0','3','Indicates potential performance issues with the availability manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34885}<{$ZABBIX.PROXY.UTIL.MIN:"availability manager"}','0','','0','','0','Zabbix proxy: Utilization of availability manager processes over {$ZABBIX.PROXY.UTIL.MAX:"availability manager"}%','b93bf2d4f9094eefa462588f4121f339',''),
('24503','{34886}>{$ZABBIX.PROXY.UTIL.MAX:"browser poller"}','Zabbix proxy: Utilization of browser poller processes is high','','0','3','Indicates potential performance issues with the browser poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34886}<{$ZABBIX.PROXY.UTIL.MIN:"browser poller"}','0','','0','','0','Zabbix proxy: Utilization of browser poller processes over {$ZABBIX.PROXY.UTIL.MAX:"browser poller"}%','edc46311472f4d26a08989a1cc5fc4ad',''),
('24504','{34887}>{$ZABBIX.PROXY.UTIL.MAX:"configuration syncer"}','Zabbix proxy: Utilization of configuration syncer processes is high','','0','3','Indicates potential performance issues with the configuration syncer, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34887}<{$ZABBIX.PROXY.UTIL.MIN:"configuration syncer"}','0','','0','','0','Zabbix proxy: Utilization of configuration syncer processes over {$ZABBIX.PROXY.UTIL.MAX:"configuration syncer"}%','fdbac62718014e8ba5b9663ecd2c87cf',''),
('24505','{34888}>{$ZABBIX.PROXY.UTIL.MAX:"data sender"}','Zabbix proxy: Utilization of data sender processes is high','','0','3','Indicates potential performance issues with the data sender, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34888}<{$ZABBIX.PROXY.UTIL.MIN:"data sender"}','0','','0','','0','Zabbix proxy: Utilization of data sender processes over {$ZABBIX.PROXY.UTIL.MAX:"data sender"}%','638a37f1268d4545bd037b88eb0f46b5',''),
('24506','{34889}>{$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','{34889}<{$ZABBIX.PROXY.UTIL.MIN:"discovery manager"}','0','','0','','0','Zabbix proxy: Utilization of discovery manager processes over {$ZABBIX.PROXY.UTIL.MAX:"discovery manager"}%','e4a34e7e45964602a329c04bedf0be11',''),
('24507','{34890}>{$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','{34890}<{$ZABBIX.PROXY.UTIL.MIN:"discovery worker"}','0','','0','','0','Zabbix proxy: Utilization of discovery worker processes over {$ZABBIX.PROXY.UTIL.MAX:"discovery worker"}%','afd226d5a01c444bbe7ec7cc8e890385',''),
('24508','{34891}>{$ZABBIX.PROXY.UTIL.MAX:"history syncer"}','Zabbix proxy: Utilization of history syncer processes is high','','0','3','Indicates potential performance issues with the history syncer, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34891}<{$ZABBIX.PROXY.UTIL.MIN:"history syncer"}','0','','0','','0','Zabbix proxy: Utilization of history syncer processes over {$ZABBIX.PROXY.UTIL.MAX:"history syncer"}%','edc13a63baa94f898c5b90cffd568725',''),
('24509','{34892}>{$ZABBIX.PROXY.UTIL.MAX:"housekeeper"}','Zabbix proxy: Utilization of housekeeper processes is high','','0','3','Indicates potential performance issues with the housekeeper, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34892}<{$ZABBIX.PROXY.UTIL.MIN:"housekeeper"}','0','','0','','0','Zabbix proxy: Utilization of housekeeper processes over {$ZABBIX.PROXY.UTIL.MAX:"housekeeper"}%','6db57127f7b74e3293be2942442665a5',''),
('24510','{34893}>{$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','{34893}<{$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"}%','2e968911946b437da198218d0c9c53d7',''),
('24511','{34894}>{$ZABBIX.PROXY.UTIL.MAX:"http poller"}','Zabbix proxy: Utilization of http poller processes is high','','0','3','Indicates potential performance issues with the http poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34894}<{$ZABBIX.PROXY.UTIL.MIN:"http poller"}','0','','0','','0','Zabbix proxy: Utilization of http poller processes over {$ZABBIX.PROXY.UTIL.MAX:"http poller"}%','a968792590324fd88c887619859b6aaa',''),
('24512','{34895}>{$ZABBIX.PROXY.UTIL.MAX:"icmp pinger"}','Zabbix proxy: Utilization of icmp pinger processes is high','','0','3','Indicates potential performance issues with the icmp pinger, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34895}<{$ZABBIX.PROXY.UTIL.MIN:"icmp pinger"}','0','','0','','0','Zabbix proxy: Utilization of icmp pinger processes over {$ZABBIX.PROXY.UTIL.MAX:"icmp pinger"}%','4accc46c86674786a09962d2ba865fad',''),
('24513','{34896}>{$ZABBIX.PROXY.UTIL.MAX:"internal poller"}','Zabbix proxy: Utilization of internal poller processes is high','','0','3','Indicates potential performance issues with the internal poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34896}<{$ZABBIX.PROXY.UTIL.MIN:"internal poller"}','0','','0','','0','Zabbix proxy: Utilization of internal poller processes over {$ZABBIX.PROXY.UTIL.MAX:"internal poller"}%','eb18c6abd7244d1b9addd5c0c411eef4',''),
('24514','{34897}>{$ZABBIX.PROXY.UTIL.MAX:"ipmi manager"}','Zabbix proxy: Utilization of ipmi manager processes is high','','0','3','Indicates potential performance issues with the ipmi manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34897}<{$ZABBIX.PROXY.UTIL.MIN:"ipmi manager"}','0','','0','','0','Zabbix proxy: Utilization of ipmi manager processes over {$ZABBIX.PROXY.UTIL.MAX:"ipmi manager"}%','8b7ba23a9571419985996aaa5545c093',''),
('24515','{34898}>{$ZABBIX.PROXY.UTIL.MAX:"ipmi poller"}','Zabbix proxy: Utilization of ipmi poller processes is high','','0','3','Indicates potential performance issues with the ipmi poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34898}<{$ZABBIX.PROXY.UTIL.MIN:"ipmi poller"}','0','','0','','0','Zabbix proxy: Utilization of ipmi poller processes over {$ZABBIX.PROXY.UTIL.MAX:"ipmi poller"}%','f108f03ff3174bf0be5bab5f8dd3edd9',''),
('24516','{34899}>{$ZABBIX.PROXY.UTIL.MAX:"java poller"}','Zabbix proxy: Utilization of java poller processes is high','','0','3','Indicates potential performance issues with the java poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34899}<{$ZABBIX.PROXY.UTIL.MIN:"java poller"}','0','','0','','0','Zabbix proxy: Utilization of java poller processes over {$ZABBIX.PROXY.UTIL.MAX:"java poller"}%','6e21610d53534d17a46e82ba77d94839',''),
('24517','{34900}>{$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','{34900}<{$ZABBIX.PROXY.UTIL.MIN:"ODBC poller"}','0','','0','','0','Zabbix proxy: Utilization of ODBC poller processes over {$ZABBIX.PROXY.UTIL.MAX:"ODBC poller"}%','f792aff9eafc495e82717b11e15c61eb',''),
('24518','{34901}>{$ZABBIX.PROXY.UTIL.MAX:"poller"}','Zabbix proxy: Utilization of poller processes is high','','0','3','Indicates potential performance issues with the poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34901}<{$ZABBIX.PROXY.UTIL.MIN:"poller"}','0','','0','','0','Zabbix proxy: Utilization of poller processes over {$ZABBIX.PROXY.UTIL.MAX:"poller"}%','b0e501fd7ee44bfb8e4b76b8ed3f7bcf',''),
('24519','{34902}>{$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','{34902}<{$ZABBIX.PROXY.UTIL.MIN:"preprocessing manager"}','0','','0','','0','Zabbix proxy: Utilization of preprocessing manager processes over {$ZABBIX.PROXY.UTIL.MAX:"preprocessing manager"}%','16d99a3deb574313ac1c9d3514b2174e',''),
('24520','{34903}>{$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','{34903}<{$ZABBIX.PROXY.UTIL.MIN:"preprocessing worker"}','0','','0','','0','Zabbix proxy: Utilization of preprocessing worker processes over {$ZABBIX.PROXY.UTIL.MAX:"preprocessing worker"}%','44b4036596a648249665be9bdaf99001',''),
('24521','{34904}>{$ZABBIX.PROXY.UTIL.MAX:"self-monitoring"}','Zabbix proxy: Utilization of self-monitoring processes is high','','0','3','Indicates potential performance issues with the self-monitoring, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34904}<{$ZABBIX.PROXY.UTIL.MIN:"self-monitoring"}','0','','0','','0','Zabbix proxy: Utilization of self-monitoring processes over {$ZABBIX.PROXY.UTIL.MAX:"self-monitoring"}%','bf4a1a0d24da4929afd8ef77cc8e0aee',''),
('24522','{34905}>{$ZABBIX.PROXY.UTIL.MAX:"snmp poller"}','Zabbix proxy: Utilization of snmp poller processes is high','','0','3','Indicates potential performance issues with the snmp poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34905}<{$ZABBIX.PROXY.UTIL.MIN:"snmp poller"}','0','','0','','0','Zabbix proxy: Utilization of snmp poller processes over {$ZABBIX.PROXY.UTIL.MAX:"snmp poller"}%','3fab2971d5eb46d8953bc34af262eef7',''),
('24523','{34906}>{$ZABBIX.PROXY.UTIL.MAX:"snmp trapper"}','Zabbix proxy: Utilization of snmp trapper processes is high','','0','3','Indicates potential performance issues with the snmp trapper, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34906}<{$ZABBIX.PROXY.UTIL.MIN:"snmp trapper"}','0','','0','','0','Zabbix proxy: Utilization of snmp trapper processes over {$ZABBIX.PROXY.UTIL.MAX:"snmp trapper"}%','c67d6cf7bb414ba5bf5e295323ceca3e',''),
('24524','{34907}>{$ZABBIX.PROXY.UTIL.MAX:"task manager"}','Zabbix proxy: Utilization of task manager processes is high','','0','3','Indicates potential performance issues with the task manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34907}<{$ZABBIX.PROXY.UTIL.MIN:"task manager"}','0','','0','','0','Zabbix proxy: Utilization of task manager processes over {$ZABBIX.PROXY.UTIL.MAX:"task manager"}%','fbba9326edf24178b4ef43de4c545fcc',''),
('24525','{34908}>{$ZABBIX.PROXY.UTIL.MAX:"trapper"}','Zabbix proxy: Utilization of trapper processes is high','','0','3','Indicates potential performance issues with the trapper, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34908}<{$ZABBIX.PROXY.UTIL.MIN:"trapper"}','0','','0','','0','Zabbix proxy: Utilization of trapper processes over {$ZABBIX.PROXY.UTIL.MAX:"trapper"}%','7ab1c8f1b661480da56f12d7e9df525d',''),
('24526','{34909}>{$ZABBIX.PROXY.UTIL.MAX:"unreachable poller"}','Zabbix proxy: Utilization of unreachable poller processes is high','','0','3','Indicates potential performance issues with the unreachable poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34909}<{$ZABBIX.PROXY.UTIL.MIN:"unreachable poller"}','0','','0','','0','Zabbix proxy: Utilization of unreachable poller processes over {$ZABBIX.PROXY.UTIL.MAX:"unreachable poller"}%','0dd4fe44dd7c45a589b95af7410e44e1',''),
('24527','{34910}>{$ZABBIX.PROXY.UTIL.MAX:"vmware collector"}','Zabbix proxy: Utilization of vmware collector processes is high','','0','3','Indicates potential performance issues with the vmware collector, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34910}<{$ZABBIX.PROXY.UTIL.MIN:"vmware collector"}','0','','0','','0','Zabbix proxy: Utilization of vmware collector processes over {$ZABBIX.PROXY.UTIL.MAX:"vmware collector"}%','e4c5051b01aa4c3bbad9237e7c593308',''),
('24528','{34911}>{$ZABBIX.PROXY.UTIL.MAX:"proxy buffer"}','Zabbix proxy: Excessive proxy memory buffer usage','','0','3','Consider increasing ProxyMemoryBufferSize in the zabbix_proxy.conf configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"proxy buffer"}% used in the proxy memory buffer','c784f7f231c34461a63d0a5cb2ce4a45',''),
('24529','{34912}=1','Zabbix proxy: Wrong template assigned','','0','5','Check that the template has been selected correctly.',NULL,'0','0','0','','0','','1','','0','Zabbix proxy: Zabbix proxy template is assigned to Zabbix server','315fc2009a02420cbe059ac199171d6d',''),
('24530','{34913}>{$ZABBIX.PROXY.UTIL.MAX:"configuration cache"}','Zabbix proxy: Excessive configuration cache usage','','0','3','Consider increasing `CacheSize` in the `zabbix_proxy.conf` configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"configuration cache"}% used in the configuration cache','523f092b9f8b41f9b652eeb7fdafe40c',''),
('24531','{34914}=1','Zabbix proxy: Failed to fetch stats data','','0','2','Zabbix has not received statistics data for `{$ZABBIX.PROXY.NODATA_TIMEOUT}`.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: Failed to fetch stats data (or no data for {$ZABBIX.PROXY.NODATA_TIMEOUT})','013a980007284540964d72be2de27a0d',''),
('24532','{34915}<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)','187bc575a0a14bbc84ad86225ddbcb61',''),
('24533','{34916}<>{34917} and length({34918})>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})','0a95e8c307074bc4ba9f55d9f172ff0a',''),
('24534','{34919}>{$ZABBIX.PROXY.UTIL.MAX:"vmware cache"}','Zabbix proxy: Excessive vmware cache usage','','0','3','Consider increasing `VMwareCacheSize` in the `zabbix_proxy.conf` configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"vmware cache"}% used in the vmware cache','04c4161b994046fe9d657da0a5a1c3db',''),
('24535','{34920}>{$ZABBIX.PROXY.UTIL.MAX:"history cache"}','Zabbix proxy: Excessive history cache usage','','0','3','Consider increasing `HistoryCacheSize` in the `zabbix_proxy.conf` configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"history cache"}% used in the history cache','042eaacf59f74383b29c0a8130ae4b16',''),
('24536','{34921}>{$ZABBIX.PROXY.UTIL.MAX:"index cache"}','Zabbix proxy: Excessive history index cache usage','','0','3','Consider increasing `HistoryIndexCacheSize` in the `zabbix_proxy.conf` configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"index cache"}% used in the history index cache','fa7be5e77ff04e728db5ee0369708dde',''),
('24537','{34922}>100','Zabbix proxy: More than 100 items have been missing data for over 10 minutes','','0','2','Indicates potential issues with network connectivity, agent failures, or unresponsive monitored resources that require attention.',NULL,'0','0','0','','0','','0','','0','','73460db4082c4feaac254b6ed790045a',''),
('24538','{34923}>{$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','{34923}<{$ZABBIX.PROXY.UTIL.MIN:"agent poller"}','0','','0','','0','Zabbix proxy: Utilization of agent poller processes over {$ZABBIX.PROXY.UTIL.MAX:"agent poller"}%','781f2b17fc384acebdcbb008a3f24bc1',''),
('24539','{34924}>{$ZABBIX.PROXY.UTIL.MAX:"availability manager"}','Zabbix proxy: Utilization of availability manager processes is high','','0','3','Indicates potential performance issues with the availability manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34924}<{$ZABBIX.PROXY.UTIL.MIN:"availability manager"}','0','','0','','0','Zabbix proxy: Utilization of availability manager processes over {$ZABBIX.PROXY.UTIL.MAX:"availability manager"}%','60c4627e26e24f5583b13ac51c652bb6',''),
('24540','{34925}>{$ZABBIX.PROXY.UTIL.MAX:"browser poller"}','Zabbix proxy: Utilization of browser poller processes is high','','0','3','Indicates potential performance issues with the browser poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34925}<{$ZABBIX.PROXY.UTIL.MIN:"browser poller"}','0','','0','','0','Zabbix proxy: Utilization of browser poller processes over {$ZABBIX.PROXY.UTIL.MAX:"browser poller"}%','9ceb9623900f4fd097c96be779088a1a',''),
('24541','{34926}>{$ZABBIX.PROXY.UTIL.MAX:"configuration syncer"}','Zabbix proxy: Utilization of configuration syncer processes is high','','0','3','Indicates potential performance issues with the configuration syncer, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34926}<{$ZABBIX.PROXY.UTIL.MIN:"configuration syncer"}','0','','0','','0','Zabbix proxy: Utilization of configuration syncer processes over {$ZABBIX.PROXY.UTIL.MAX:"configuration syncer"}%','4fc6ad715b6d4eea89c47e9a80cc1bd2',''),
('24542','{34927}>{$ZABBIX.PROXY.UTIL.MAX:"data sender"}','Zabbix proxy: Utilization of data sender processes is high','','0','3','Indicates potential performance issues with the data sender, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34927}<{$ZABBIX.PROXY.UTIL.MIN:"data sender"}','0','','0','','0','Zabbix proxy: Utilization of data sender processes over {$ZABBIX.PROXY.UTIL.MAX:"data sender"}%','53a13b3f8ae746a5aa698c48beeb782f',''),
('24543','{34928}>{$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','{34928}<{$ZABBIX.PROXY.UTIL.MIN:"discovery manager"}','0','','0','','0','Zabbix proxy: Utilization of discovery manager processes over {$ZABBIX.PROXY.UTIL.MAX:"discovery manager"}%','ac5583b00510498ea9f0cf75835dc8c9',''),
('24544','{34929}>{$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','{34929}<{$ZABBIX.PROXY.UTIL.MIN:"discovery worker"}','0','','0','','0','Zabbix proxy: Utilization of discovery worker processes over {$ZABBIX.PROXY.UTIL.MAX:"discovery worker"}%','2368cc40dca345dc81b4e06f6c652f5a',''),
('24545','{34930}>{$ZABBIX.PROXY.UTIL.MAX:"history syncer"}','Zabbix proxy: Utilization of history syncer processes is high','','0','3','Indicates potential performance issues with the history syncer, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34930}<{$ZABBIX.PROXY.UTIL.MIN:"history syncer"}','0','','0','','0','Zabbix proxy: Utilization of history syncer processes over {$ZABBIX.PROXY.UTIL.MAX:"history syncer"}%','f56becd9ed784dcf9f97fa703269b46e',''),
('24546','{34931}>{$ZABBIX.PROXY.UTIL.MAX:"housekeeper"}','Zabbix proxy: Utilization of housekeeper processes is high','','0','3','Indicates potential performance issues with the housekeeper, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34931}<{$ZABBIX.PROXY.UTIL.MIN:"housekeeper"}','0','','0','','0','Zabbix proxy: Utilization of housekeeper processes over {$ZABBIX.PROXY.UTIL.MAX:"housekeeper"}%','f81451219df048ce92a35b9673548358',''),
('24547','{34932}>{$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','{34932}<{$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"}%','b0bd0d9770fc4276be324b97150c691c',''),
('24548','{34933}>{$ZABBIX.PROXY.UTIL.MAX:"http poller"}','Zabbix proxy: Utilization of http poller processes is high','','0','3','Indicates potential performance issues with the http poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34933}<{$ZABBIX.PROXY.UTIL.MIN:"http poller"}','0','','0','','0','Zabbix proxy: Utilization of http poller processes over {$ZABBIX.PROXY.UTIL.MAX:"http poller"}%','43b21d9aff8441cba1c0db97e7b193e0',''),
('24549','{34934}>{$ZABBIX.PROXY.UTIL.MAX:"icmp pinger"}','Zabbix proxy: Utilization of icmp pinger processes is high','','0','3','Indicates potential performance issues with the icmp pinger, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34934}<{$ZABBIX.PROXY.UTIL.MIN:"icmp pinger"}','0','','0','','0','Zabbix proxy: Utilization of icmp pinger processes over {$ZABBIX.PROXY.UTIL.MAX:"icmp pinger"}%','417d421e076342e5b38ab7a925dc7ee6',''),
('24550','{34935}>{$ZABBIX.PROXY.UTIL.MAX:"internal poller"}','Zabbix proxy: Utilization of internal poller processes is high','','0','3','Indicates potential performance issues with the internal poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34935}<{$ZABBIX.PROXY.UTIL.MIN:"internal poller"}','0','','0','','0','Zabbix proxy: Utilization of internal poller processes over {$ZABBIX.PROXY.UTIL.MAX:"internal poller"}%','60dacadac60641789e7f8eb2a6441498',''),
('24551','{34936}>{$ZABBIX.PROXY.UTIL.MAX:"ipmi manager"}','Zabbix proxy: Utilization of ipmi manager processes is high','','0','3','Indicates potential performance issues with the ipmi manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34936}<{$ZABBIX.PROXY.UTIL.MIN:"ipmi manager"}','0','','0','','0','Zabbix proxy: Utilization of ipmi manager processes over {$ZABBIX.PROXY.UTIL.MAX:"ipmi manager"}%','773bcda0a0d44428bd66f619df41a94d',''),
('24552','{34937}>{$ZABBIX.PROXY.UTIL.MAX:"ipmi poller"}','Zabbix proxy: Utilization of ipmi poller processes is high','','0','3','Indicates potential performance issues with the ipmi poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34937}<{$ZABBIX.PROXY.UTIL.MIN:"ipmi poller"}','0','','0','','0','Zabbix proxy: Utilization of ipmi poller processes over {$ZABBIX.PROXY.UTIL.MAX:"ipmi poller"}%','520d3b11a75c42cd911ec3e8639c7325',''),
('24553','{34938}>{$ZABBIX.PROXY.UTIL.MAX:"java poller"}','Zabbix proxy: Utilization of java poller processes is high','','0','3','Indicates potential performance issues with the java poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34938}<{$ZABBIX.PROXY.UTIL.MIN:"java poller"}','0','','0','','0','Zabbix proxy: Utilization of java poller processes over {$ZABBIX.PROXY.UTIL.MAX:"java poller"}%','48c63db097c94a52a13cfea9d53a5d6e',''),
('24554','{34939}>{$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','{34939}<{$ZABBIX.PROXY.UTIL.MIN:"ODBC poller"}','0','','0','','0','Zabbix proxy: Utilization of ODBC poller processes over {$ZABBIX.PROXY.UTIL.MAX:"ODBC poller"}%','d3d1b01114b14de1b5a432fb574713f1',''),
('24555','{34940}>{$ZABBIX.PROXY.UTIL.MAX:"poller"}','Zabbix proxy: Utilization of poller processes is high','','0','3','Indicates potential performance issues with the poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34940}<{$ZABBIX.PROXY.UTIL.MIN:"poller"}','0','','0','','0','Zabbix proxy: Utilization of poller processes over {$ZABBIX.PROXY.UTIL.MAX:"poller"}%','1d7cee57cd28400790ea8fea6901d0a9',''),
('24556','{34941}>{$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','{34941}<{$ZABBIX.PROXY.UTIL.MIN:"preprocessing manager"}','0','','0','','0','Zabbix proxy: Utilization of preprocessing manager processes over {$ZABBIX.PROXY.UTIL.MAX:"preprocessing manager"}%','a3692dec8449492b8c1c0fc0ffc38ba7',''),
('24557','{34942}>{$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','{34942}<{$ZABBIX.PROXY.UTIL.MIN:"preprocessing worker"}','0','','0','','0','Zabbix proxy: Utilization of preprocessing worker processes over {$ZABBIX.PROXY.UTIL.MAX:"preprocessing worker"}%','cbdfa6eab86547a9bcc15308cb24ecec',''),
('24558','{34943}>{$ZABBIX.PROXY.UTIL.MAX:"self-monitoring"}','Zabbix proxy: Utilization of self-monitoring processes is high','','0','3','Indicates potential performance issues with the self-monitoring, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34943}<{$ZABBIX.PROXY.UTIL.MIN:"self-monitoring"}','0','','0','','0','Zabbix proxy: Utilization of self-monitoring processes over {$ZABBIX.PROXY.UTIL.MAX:"self-monitoring"}%','8c731df045474ff78961106f51943a2d',''),
('24559','{34944}>{$ZABBIX.PROXY.UTIL.MAX:"snmp poller"}','Zabbix proxy: Utilization of snmp poller processes is high','','0','3','Indicates potential performance issues with the snmp poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34944}<{$ZABBIX.PROXY.UTIL.MIN:"snmp poller"}','0','','0','','0','Zabbix proxy: Utilization of snmp poller processes over {$ZABBIX.PROXY.UTIL.MAX:"snmp poller"}%','37f76a103450441c91dc980877685fdf',''),
('24560','{34945}>{$ZABBIX.PROXY.UTIL.MAX:"snmp trapper"}','Zabbix proxy: Utilization of snmp trapper processes is high','','0','3','Indicates potential performance issues with the snmp trapper, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34945}<{$ZABBIX.PROXY.UTIL.MIN:"snmp trapper"}','0','','0','','0','Zabbix proxy: Utilization of snmp trapper processes over {$ZABBIX.PROXY.UTIL.MAX:"snmp trapper"}%','125f0015cbab441f8fb585273b1be59d',''),
('24561','{34946}>{$ZABBIX.PROXY.UTIL.MAX:"task manager"}','Zabbix proxy: Utilization of task manager processes is high','','0','3','Indicates potential performance issues with the task manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34946}<{$ZABBIX.PROXY.UTIL.MIN:"task manager"}','0','','0','','0','Zabbix proxy: Utilization of task manager processes over {$ZABBIX.PROXY.UTIL.MAX:"task manager"}%','639ce0f06fa4454784458426fedce080',''),
('24562','{34947}>{$ZABBIX.PROXY.UTIL.MAX:"trapper"}','Zabbix proxy: Utilization of trapper processes is high','','0','3','Indicates potential performance issues with the trapper, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34947}<{$ZABBIX.PROXY.UTIL.MIN:"trapper"}','0','','0','','0','Zabbix proxy: Utilization of trapper processes over {$ZABBIX.PROXY.UTIL.MAX:"trapper"}%','dd4185cd7ff646ccaee1d7c36eba58b4',''),
('24563','{34948}>{$ZABBIX.PROXY.UTIL.MAX:"unreachable poller"}','Zabbix proxy: Utilization of unreachable poller processes is high','','0','3','Indicates potential performance issues with the unreachable poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34948}<{$ZABBIX.PROXY.UTIL.MIN:"unreachable poller"}','0','','0','','0','Zabbix proxy: Utilization of unreachable poller processes over {$ZABBIX.PROXY.UTIL.MAX:"unreachable poller"}%','353e0603f5454b92806bc27442e4675a',''),
('24564','{34949}>{$ZABBIX.PROXY.UTIL.MAX:"vmware collector"}','Zabbix proxy: Utilization of vmware collector processes is high','','0','3','Indicates potential performance issues with the vmware collector, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34949}<{$ZABBIX.PROXY.UTIL.MIN:"vmware collector"}','0','','0','','0','Zabbix proxy: Utilization of vmware collector processes over {$ZABBIX.PROXY.UTIL.MAX:"vmware collector"}%','19212b4c55a5412a8358486ccec73867',''),
('24565','{34950}>{$ZABBIX.PROXY.UTIL.MAX:"proxy buffer"}','Zabbix proxy: Excessive proxy memory buffer usage','','0','3','Consider increasing ProxyMemoryBufferSize in the zabbix_proxy.conf configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"proxy buffer"}% used in the proxy memory buffer','58582605c4644fffaabca8e403ae7529',''),
('24566','{34951}=1','Zabbix proxy: Wrong template assigned','','0','5','Check that the template has been selected correctly.',NULL,'0','0','0','','0','','1','','0','Zabbix proxy: Zabbix proxy template is assigned to Zabbix server','90d305b0cf7246c19aedc74b4c566148',''),
('24567','{34952}>{$ZABBIX.PROXY.UTIL.MAX:"configuration cache"}','Zabbix proxy: Excessive configuration cache usage','','0','3','Consider increasing `CacheSize` in the `zabbix_proxy.conf` configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"configuration cache"}% used in the configuration cache','280ce16d51a04a2c98574da85639df8a',''),
('24568','{34953}=1','Zabbix proxy: Failed to fetch stats data','','0','2','Zabbix has not received statistics data for `{$ZABBIX.PROXY.NODATA_TIMEOUT}`.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: Failed to fetch stats data (or no data for {$ZABBIX.PROXY.NODATA_TIMEOUT})','78ee655520bb495097142ba6b4ac30ab',''),
('24569','{34954}<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)','f31a41c673c541e89fa0d4792506316a',''),
('24570','{34955}<>{34956} and length({34957})>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})','2e0d640f83e14fd1940d195bbb133ed8',''),
('24571','{34958}>{$ZABBIX.PROXY.UTIL.MAX:"vmware cache"}','Zabbix proxy: Excessive vmware cache usage','','0','3','Consider increasing `VMwareCacheSize` in the `zabbix_proxy.conf` configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"vmware cache"}% used in the vmware cache','a0ed7fac6d7c4b1ea5e66e476dfdc9d1',''),
('24572','{34959}>{$ZABBIX.PROXY.UTIL.MAX:"history cache"}','Zabbix proxy: Excessive history cache usage','','0','3','Consider increasing `HistoryCacheSize` in the `zabbix_proxy.conf` configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"history cache"}% used in the history cache','eba5460898154090bb57db9b6f80aefb',''),
('24573','{34960}>{$ZABBIX.PROXY.UTIL.MAX:"index cache"}','Zabbix proxy: Excessive history index cache usage','','0','3','Consider increasing `HistoryIndexCacheSize` in the `zabbix_proxy.conf` configuration file.',NULL,'0','0','0','','0','','0','','0','Zabbix proxy: More than {$ZABBIX.PROXY.UTIL.MAX:"index cache"}% used in the history index cache','0ed6244bfe5f405face0941e87c9233a',''),
('24574','{34961}>100','Zabbix proxy: More than 100 items have been missing data for over 10 minutes','','0','2','Indicates potential issues with network connectivity, agent failures, or unresponsive monitored resources that require attention.',NULL,'0','0','0','','0','','0','','0','','1bdab54e366e423aa9320baeec90f57b',''),
('24575','{34962}=0','Zabbix server: Wrong template assigned','','0','5','Check that the template has been selected correctly.',NULL,'0','0','0','','0','','1','','0','Zabbix server: Zabbix server template is assigned to Zabbix proxy','49e7153a96e74b60aad73cd91a792098',''),
('24576','{34963}=0','Zabbix server: Wrong template assigned','','0','5','Check that the template has been selected correctly.',NULL,'0','0','0','','0','','1','','0','Zabbix server: Zabbix server template is assigned to Zabbix proxy','3b0969d950ac4f9e878d0f7d72d83af2',''),
('24577','{34964}>{$ZABBIX.SERVER.UTIL.MAX:"agent poller"}','Zabbix server: 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','{34964}<{$ZABBIX.SERVER.UTIL.MIN:"agent poller"}','0','','0','','0','Zabbix server: Utilization of agent poller processes over {$ZABBIX.SERVER.UTIL.MAX:"agent poller"}%','6a89e07170e14a9c95154a64fb0248fc',''),
('24578','{34965}>{$ZABBIX.SERVER.UTIL.MAX:"alerter"}','Zabbix server: Utilization of alerter processes is high','','0','3','Indicates potential performance issues with the alerter, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34965}<{$ZABBIX.SERVER.UTIL.MIN:"alerter"}','0','','0','','0','Zabbix server: Utilization of alerter processes over {$ZABBIX.SERVER.UTIL.MAX:"alerter"}%','a1f644d8d3e34b658c57ef671422038d',''),
('24579','{34966}>{$ZABBIX.SERVER.UTIL.MAX:"alert manager"}','Zabbix server: Utilization of alert manager processes is high','','0','3','Indicates potential performance issues with the alert manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34966}<{$ZABBIX.SERVER.UTIL.MIN:"alert manager"}','0','','0','','0','Zabbix server: Utilization of alert manager processes over {$ZABBIX.SERVER.UTIL.MAX:"alert manager"}%','0a9ebdc127bf42ccbbeeeffe02b57095',''),
('24580','{34967}>{$ZABBIX.SERVER.UTIL.MAX:"alert syncer"}','Zabbix server: Utilization of alert syncer processes is high','','0','3','Indicates potential performance issues with the alert syncer, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34967}<{$ZABBIX.SERVER.UTIL.MIN:"alert syncer"}','0','','0','','0','Zabbix server: Utilization of alert syncer processes over {$ZABBIX.SERVER.UTIL.MAX:"alert syncer"}%','bc7ed4d8ea2a455d813ff1146a010a6f',''),
('24581','{34968}>{$ZABBIX.SERVER.UTIL.MAX:"availability manager"}','Zabbix server: Utilization of availability manager processes is high','','0','3','Indicates potential performance issues with the availability manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34968}<{$ZABBIX.SERVER.UTIL.MIN:"availability manager"}','0','','0','','0','Zabbix server: Utilization of availability manager processes over {$ZABBIX.SERVER.UTIL.MAX:"availability manager"}%','956b94177f544386bb4add58df433ca6',''),
('24582','{34969}>{$ZABBIX.SERVER.UTIL.MAX:"browser poller"}','Zabbix server: Utilization of browser poller processes is high','','0','3','Indicates potential performance issues with the browser poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34969}<{$ZABBIX.SERVER.UTIL.MIN:"browser poller"}','0','','0','','0','Zabbix server: Utilization of browser poller processes over {$ZABBIX.SERVER.UTIL.MAX:"browser poller"}%','8df9cc8b0e1f462cae4898c6a54020fc',''),
('24583','{34970}>{$ZABBIX.SERVER.UTIL.MAX:"configuration syncer"}','Zabbix server: Utilization of configuration syncer processes is high','','0','3','Indicates potential performance issues with the configuration syncer, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34970}<{$ZABBIX.SERVER.UTIL.MIN:"configuration syncer"}','0','','0','','0','Zabbix server: Utilization of configuration syncer processes over {$ZABBIX.SERVER.UTIL.MAX:"configuration syncer"}%','cb4f8f5ad7e24fbcbc64ab8006643124',''),
('24584','{34971}>{$ZABBIX.SERVER.UTIL.MAX:"configuration syncer worker"}','Zabbix server: Utilization of configuration syncer worker processes is high','','0','3','Indicates potential performance issues with the configuration syncer worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34971}<{$ZABBIX.SERVER.UTIL.MIN:"configuration syncer worker"}','0','','0','','0','Zabbix server: Utilization of configuration syncer worker processes over {$ZABBIX.SERVER.UTIL.MAX:"configuration syncer worker"}%','5e4ee9a96013447ebe40b745c105fd03',''),
('24585','{34972}>{$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','{34972}<{$ZABBIX.SERVER.UTIL.MIN:"connector manager"}','0','','0','','0','Zabbix server: Utilization of connector manager processes over {$ZABBIX.SERVER.UTIL.MAX:"connector manager"}%','eb8957d071b74a80bf3279444473cddb',''),
('24586','{34973}>{$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','{34973}<{$ZABBIX.SERVER.UTIL.MIN:"connector worker"}','0','','0','','0','Zabbix server: Utilization of connector worker processes over {$ZABBIX.SERVER.UTIL.MAX:"connector worker"}%','79881c61531b4446a8f3107127ce36ed',''),
('24587','{34974}>{$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','{34974}<{$ZABBIX.SERVER.UTIL.MIN:"discovery manager"}','0','','0','','0','Zabbix server: Utilization of discovery manager processes over {$ZABBIX.SERVER.UTIL.MAX:"discovery manager"}%','622a1cf7158c407789313819e74310cd',''),
('24588','{34975}>{$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','{34975}<{$ZABBIX.SERVER.UTIL.MIN:"discovery worker"}','0','','0','','0','Zabbix server: Utilization of discovery worker processes over {$ZABBIX.SERVER.UTIL.MAX:"discovery worker"}%','38b49ca5610244b782c66e068727264f',''),
('24589','{34976}>{$ZABBIX.SERVER.UTIL.MAX:"escalator"}','Zabbix server: Utilization of escalator processes is high','','0','3','Indicates potential performance issues with the escalator, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34976}<{$ZABBIX.SERVER.UTIL.MIN:"escalator"}','0','','0','','0','Zabbix server: Utilization of escalator processes over {$ZABBIX.SERVER.UTIL.MAX:"escalator"}%','21eb9b4f3b204a348738b74752c9927d',''),
('24590','{34977}>{$ZABBIX.SERVER.UTIL.MAX:"history poller"}','Zabbix server: Utilization of history poller processes is high','','0','3','Indicates potential performance issues with the history poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34977}<{$ZABBIX.SERVER.UTIL.MIN:"history poller"}','0','','0','','0','Zabbix server: Utilization of history poller processes over {$ZABBIX.SERVER.UTIL.MAX:"history poller"}%','a1886afb06824e1091220fbe5193461f',''),
('24591','{34978}>{$ZABBIX.SERVER.UTIL.MAX:"history syncer"}','Zabbix server: Utilization of history syncer processes is high','','0','3','Indicates potential performance issues with the history syncer, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34978}<{$ZABBIX.SERVER.UTIL.MIN:"history syncer"}','0','','0','','0','Zabbix server: Utilization of history syncer processes over {$ZABBIX.SERVER.UTIL.MAX:"history syncer"}%','f738b0289c324e78989436bb92493720',''),
('24592','{34979}>{$ZABBIX.SERVER.UTIL.MAX:"housekeeper"}','Zabbix server: Utilization of housekeeper processes is high','','0','3','Indicates potential performance issues with the housekeeper, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34979}<{$ZABBIX.SERVER.UTIL.MIN:"housekeeper"}','0','','0','','0','Zabbix server: Utilization of housekeeper processes over {$ZABBIX.SERVER.UTIL.MAX:"housekeeper"}%','96ceff1b787e41b0a02a2d2221f57f6e',''),
('24593','{34980}>{$ZABBIX.SERVER.UTIL.MAX:"http agent poller"}','Zabbix server: 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','{34980}<{$ZABBIX.SERVER.UTIL.MIN:"http agent poller"}','0','','0','','0','Zabbix server: Utilization of http agent poller processes over {$ZABBIX.SERVER.UTIL.MAX:"http agent poller"}%','e4d7add47be94419824f333fcc48880f',''),
('24594','{34981}>{$ZABBIX.SERVER.UTIL.MAX:"http poller"}','Zabbix server: Utilization of http poller processes is high','','0','3','Indicates potential performance issues with the http poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34981}<{$ZABBIX.SERVER.UTIL.MIN:"http poller"}','0','','0','','0','Zabbix server: Utilization of http poller processes over {$ZABBIX.SERVER.UTIL.MAX:"http poller"}%','f254894eb0fb491989e803af02e707d2',''),
('24595','{34982}>{$ZABBIX.SERVER.UTIL.MAX:"icmp pinger"}','Zabbix server: Utilization of icmp pinger processes is high','','0','3','Indicates potential performance issues with the icmp pinger, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34982}<{$ZABBIX.SERVER.UTIL.MIN:"icmp pinger"}','0','','0','','0','Zabbix server: Utilization of icmp pinger processes over {$ZABBIX.SERVER.UTIL.MAX:"icmp pinger"}%','b1ebb6969696476da6a90c6f0d8de5eb',''),
('24596','{34983}>{$ZABBIX.SERVER.UTIL.MAX:"internal poller"}','Zabbix server: Utilization of internal poller processes is high','','0','3','Indicates potential performance issues with the internal poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34983}<{$ZABBIX.SERVER.UTIL.MIN:"internal poller"}','0','','0','','0','Zabbix server: Utilization of internal poller processes over {$ZABBIX.SERVER.UTIL.MAX:"internal poller"}%','99fad58c6c5244f58d71e4d45840f355',''),
('24597','{34984}>{$ZABBIX.SERVER.UTIL.MAX:"ipmi manager"}','Zabbix server: Utilization of ipmi manager processes is high','','0','3','Indicates potential performance issues with the ipmi manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34984}<{$ZABBIX.SERVER.UTIL.MIN:"ipmi manager"}','0','','0','','0','Zabbix server: Utilization of ipmi manager processes over {$ZABBIX.SERVER.UTIL.MAX:"ipmi manager"}%','19f8d398245a4fa993467451571eb06a',''),
('24598','{34985}>{$ZABBIX.SERVER.UTIL.MAX:"ipmi poller"}','Zabbix server: Utilization of ipmi poller processes is high','','0','3','Indicates potential performance issues with the ipmi poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34985}<{$ZABBIX.SERVER.UTIL.MIN:"ipmi poller"}','0','','0','','0','Zabbix server: Utilization of ipmi poller processes over {$ZABBIX.SERVER.UTIL.MAX:"ipmi poller"}%','eb82596e6a25422fbbb2da9910616557',''),
('24599','{34986}>{$ZABBIX.SERVER.UTIL.MAX:"java poller"}','Zabbix server: Utilization of java poller processes is high','','0','3','Indicates potential performance issues with the java poller, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34986}<{$ZABBIX.SERVER.UTIL.MIN:"java poller"}','0','','0','','0','Zabbix server: Utilization of java poller processes over {$ZABBIX.SERVER.UTIL.MAX:"java poller"}%','21114bc6d4be4ab393141ddc34eaec5f',''),
('24600','{34987}>{$ZABBIX.SERVER.UTIL.MAX:"LLD manager"}','Zabbix server: Utilization of LLD manager processes is high','','0','3','Indicates potential performance issues with the LLD manager, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34987}<{$ZABBIX.SERVER.UTIL.MIN:"LLD manager"}','0','','0','','0','Zabbix server: Utilization of LLD manager processes over {$ZABBIX.SERVER.UTIL.MAX:"LLD manager"}%','8b1e71a2be054aa9913b0d0ab980d7a3',''),
('24601','{34988}>{$ZABBIX.SERVER.UTIL.MAX:"LLD worker"}','Zabbix server: Utilization of LLD worker processes is high','','0','3','Indicates potential performance issues with the LLD worker, which may affect monitoring efficiency and response times.',NULL,'0','0','1','{34988}<{$ZABBIX.SERVER.UTIL.MIN:"LLD worker"}','0','','0','','0','Zabbix server: Utilization of LLD worker processes over {$ZABBIX.SERVER.UTIL.MAX:"LLD worker"}%','26ab68bbf6a54277aeaa51f41b413da6',''),
