diff --git a/.github/jekyll/_data/meta.json b/.github/jekyll/_data/meta.json index 8e9a5f2e6..f44a2f57d 100644 --- a/.github/jekyll/_data/meta.json +++ b/.github/jekyll/_data/meta.json @@ -1,23 +1,23 @@ { "name": ".", "type": "folder", - "sync": 1646275486, + "sync": 1646290172, "next": [ { "name": "Applications", "type": "folder", - "sync": 1646275496, + "sync": 1646290193, "next": [ { "name": "1C", "type": "folder", - "sync": 1646275486, + "sync": 1646290172, "next": [ { "name": "template_1c_enterprise", "template": "1C Enterprise", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "1C", @@ -28,14 +28,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290172, "description": "## Overview\n\n **Zabbix 1C Enterprise**\n\n\nMonitor sessions number for each base in cluster and for each cluster. Items names include base name and cluster name.\n\n\nUsing LLD for base discovery\n\n\nSuggestions are welcome.\n\n\nUPD Added items for monitoring\n\n\nUPD2 Added converted to exe Python scripts, so you don't need install Python interpreter, but you need be very fearless to use exe files from Internet :)", "template_file": "template_1c_enterprise.xml", "name": "1C Enterprise" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290172, + "description": "## Overview\n\n **Zabbix 1C Enterprise**\n\n\nMonitor sessions number for each base in cluster and for each cluster. Items names include base name and cluster name.\n\n\nUsing LLD for base discovery\n\n\nSuggestions are welcome.\n\n\nUPD Added items for monitoring\n\n\nUPD2 Added converted to exe Python scripts, so you don't need install Python interpreter, but you need be very fearless to use exe files from Internet :) \n", + "template_file": "template_1c_enterprise.yaml", + "name": "1C Enterprise" + }, + { + "version": 6.0, + "sync": 1646290172, "description": "## Overview\n\n **Zabbix 1C Enterprise**\n\n\nMonitor sessions number for each base in cluster and for each cluster. Items names include base name and cluster name.\n\n\nUsing LLD for base discovery\n\n\nSuggestions are welcome.\n\n\nUPD Added items for monitoring\n\n\nUPD2 Added converted to exe Python scripts, so you don't need install Python interpreter, but you need be very fearless to use exe files from Internet :) \n", "template_file": "template_1c_enterprise.yaml", "name": "1C Enterprise" @@ -53,13 +60,13 @@ { "name": "Anti-Virus", "type": "folder", - "sync": 1646275486, + "sync": 1646290172, "next": [ { "name": "template_kaspersky", "template": "App Kaspersky", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Anti-Virus", @@ -70,14 +77,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290172, "description": "## Overview\n\nÉ obrigatório ter o SNMP habilitado no server, bem como ter habilitado o SNMP na console de gerenciamento do Kaspersky (KSC)\n\n\nMétodo de coleta, via SNMPv2\n\n\nItens coletados:\n\n\n* Quantidade de Hosts com licenças expiradas\n* Quantidade de Hosts sem verificação\n* Quantidade de Hosts sem conexão\n* Quantidade de hosts com licença expirando\n* Quantidade de hosts localizados\n* Quantidade de hosts com Antivírus\n* Número de vírus no Unprocessed files\n* Quantidade de eventos críticos\n* Status da atualização da base\n* Último update.\n\n\n## Author\n\nCarlos Eduardo", "template_file": "template_kaspersky.xml", "name": "App Kaspersky" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290172, + "description": "## Overview\n\nÉ obrigatório ter o SNMP habilitado no server, bem como ter habilitado o SNMP na console de gerenciamento do Kaspersky (KSC)\n\n\nMétodo de coleta, via SNMPv2\n\n\nItens coletados:\n\n\n* Quantidade de Hosts com licenças expiradas\n* Quantidade de Hosts sem verificação\n* Quantidade de Hosts sem conexão\n* Quantidade de hosts com licença expirando\n* Quantidade de hosts localizados\n* Quantidade de hosts com Antivírus\n* Número de vírus no Unprocessed files\n* Quantidade de eventos críticos\n* Status da atualização da base\n* Último update.\n\n\n## Author\n\nCarlos Eduardo\n", + "template_file": "template_kaspersky.yaml", + "name": "App Kaspersky" + }, + { + "version": 6.0, + "sync": 1646290172, "description": "## Overview\n\nÉ obrigatório ter o SNMP habilitado no server, bem como ter habilitado o SNMP na console de gerenciamento do Kaspersky (KSC)\n\n\nMétodo de coleta, via SNMPv2\n\n\nItens coletados:\n\n\n* Quantidade de Hosts com licenças expiradas\n* Quantidade de Hosts sem verificação\n* Quantidade de Hosts sem conexão\n* Quantidade de hosts com licença expirando\n* Quantidade de hosts localizados\n* Quantidade de hosts com Antivírus\n* Número de vírus no Unprocessed files\n* Quantidade de eventos críticos\n* Status da atualização da base\n* Último update.\n\n\n## Author\n\nCarlos Eduardo\n", "template_file": "template_kaspersky.yaml", "name": "App Kaspersky" @@ -94,7 +108,7 @@ "name": "template_kaspersky_security_center_11", "template": "Kaspersky Security Center 11", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Anti-Virus", @@ -105,14 +119,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290172, "description": "", "template_file": "template_kaspersky_security_center_11.xml", "name": "Kaspersky Security Center 11" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290172, + "description": "", + "template_file": "template_kaspersky_security_center_11.yaml", + "name": "Kaspersky Security Center 11" + }, + { + "version": 6.0, + "sync": 1646290172, "description": "", "template_file": "template_kaspersky_security_center_11.yaml", "name": "Kaspersky Security Center 11" @@ -131,13 +152,13 @@ { "name": "Backup", "type": "folder", - "sync": 1646275487, + "sync": 1646290173, "next": [ { "name": "template_arcserve_udp_vm_backup_jobs", "template": "Arcserve UDP VM Backup Check", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -148,14 +169,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290172, "description": "## Overview\n\n**Zabbix-Template Arcserve UDP VM Backups**\n\n\nThis template checks out-of-the-box only VM Backups from Arcserve UDP. This script only counts the number of successful or unsuccessful backup jobs and throws a trigger if necessary.\n\n\nInstallation steps für Arcserve UDP VM Backup checks:\n\n\n1. Copy the script file \"Arcserve\\_UDP\\_VMCount.ps1\" to your Zabbix Agent Script folder on the Arcserve UDP Host.\n2. Modify script parameter if necessary (protocol, port, JobID)\n3. Test the script manually on the Arcserve UDP Host: \n`.\\Arcserve_UDP_VMCount.ps1 JobSuccessCount`\n4. For debugging of errors you can enable \"$Debug=$True\" in the script..\n5. Check the script for correct results of the VM backup jobs.\n6. Add the UserParameter to the zabbix\\_agentd.conf: \nUserParameter=custom.arcserveudpvm[*],powershell.exe -NoProfile -ExecutionPolicy Bypass -file \"C:\\Program Files\\Zabbix Agent\\Scripts\\Arcserve\\_UDP\\_VMCount.ps1\" $1 $2 $3 $4 $5\n7. Import des Zabbix Template \"Template\\_Arcserve UDP VM Backup Check.xml\" to the Zabbix Server.\n8. Assign the template to the Zabbix host for ARcserve UDP.\n9. Modify the macro \"{$ARCSERVE\\_DOMAIN}\", \"{$ARCSERVE\\_USER}\" and \"{$ARCSERVE\\_PASS} with the read only user login for Arcserve UDP.\n10. Check the latest value of application \"ArcserveUDP Jobs\".\n\n\n## Author\n\nR.P.Wimmer", "template_file": "template_arcserve_udp_vm_backup_jobs.xml", "name": "Arcserve UDP VM Backup Check" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290172, + "description": "## Overview\n\n**Zabbix-Template Arcserve UDP VM Backups**\n\n\nThis template checks out-of-the-box only VM Backups from Arcserve UDP. This script only counts the number of successful or unsuccessful backup jobs and throws a trigger if necessary.\n\n\nInstallation steps für Arcserve UDP VM Backup checks:\n\n\n1. Copy the script file \"Arcserve\\_UDP\\_VMCount.ps1\" to your Zabbix Agent Script folder on the Arcserve UDP Host.\n2. Modify script parameter if necessary (protocol, port, JobID)\n3. Test the script manually on the Arcserve UDP Host: \n`.\\Arcserve_UDP_VMCount.ps1 JobSuccessCount`\n4. For debugging of errors you can enable \"$Debug=$True\" in the script..\n5. Check the script for correct results of the VM backup jobs.\n6. Add the UserParameter to the zabbix\\_agentd.conf: \nUserParameter=custom.arcserveudpvm[*],powershell.exe -NoProfile -ExecutionPolicy Bypass -file \"C:\\Program Files\\Zabbix Agent\\Scripts\\Arcserve\\_UDP\\_VMCount.ps1\" $1 $2 $3 $4 $5\n7. Import des Zabbix Template \"Template\\_Arcserve UDP VM Backup Check.xml\" to the Zabbix Server.\n8. Assign the template to the Zabbix host for ARcserve UDP.\n9. Modify the macro \"{$ARCSERVE\\_DOMAIN}\", \"{$ARCSERVE\\_USER}\" and \"{$ARCSERVE\\_PASS} with the read only user login for Arcserve UDP.\n10. Check the latest value of application \"ArcserveUDP Jobs\".\n\n\n## Author\n\nR.P.Wimmer\n", + "template_file": "template_arcserve_udp_vm_backup_jobs.yaml", + "name": "Arcserve UDP VM Backup Check" + }, + { + "version": 6.0, + "sync": 1646290172, "description": "## Overview\n\n**Zabbix-Template Arcserve UDP VM Backups**\n\n\nThis template checks out-of-the-box only VM Backups from Arcserve UDP. This script only counts the number of successful or unsuccessful backup jobs and throws a trigger if necessary.\n\n\nInstallation steps für Arcserve UDP VM Backup checks:\n\n\n1. Copy the script file \"Arcserve\\_UDP\\_VMCount.ps1\" to your Zabbix Agent Script folder on the Arcserve UDP Host.\n2. Modify script parameter if necessary (protocol, port, JobID)\n3. Test the script manually on the Arcserve UDP Host: \n`.\\Arcserve_UDP_VMCount.ps1 JobSuccessCount`\n4. For debugging of errors you can enable \"$Debug=$True\" in the script..\n5. Check the script for correct results of the VM backup jobs.\n6. Add the UserParameter to the zabbix\\_agentd.conf: \nUserParameter=custom.arcserveudpvm[*],powershell.exe -NoProfile -ExecutionPolicy Bypass -file \"C:\\Program Files\\Zabbix Agent\\Scripts\\Arcserve\\_UDP\\_VMCount.ps1\" $1 $2 $3 $4 $5\n7. Import des Zabbix Template \"Template\\_Arcserve UDP VM Backup Check.xml\" to the Zabbix Server.\n8. Assign the template to the Zabbix host for ARcserve UDP.\n9. Modify the macro \"{$ARCSERVE\\_DOMAIN}\", \"{$ARCSERVE\\_USER}\" and \"{$ARCSERVE\\_PASS} with the read only user login for Arcserve UDP.\n10. Check the latest value of application \"ArcserveUDP Jobs\".\n\n\n## Author\n\nR.P.Wimmer\n", "template_file": "template_arcserve_udp_vm_backup_jobs.yaml", "name": "Arcserve UDP VM Backup Check" @@ -171,7 +199,7 @@ "name": "template_asigra_backup_snmp_traps", "template": "Asigra Backup SNMP Traps", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -182,14 +210,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290172, "description": "## Overview\n\nThis template will store Asigra Client Backup Jobs (failed and successful) in Items. It also includes triggers when a Backup Job fails.\n\n\nThe triggers will NOT auto recover. So user needs to either acknowledge or close the trigger manually. \n\n\nPrerequisites:\n\n\n- SNMP Traps configured and working on Zabbix Server or Proxy.\n\n\n- Asigra Client needs to be configured to sent SNMP Traps to Zabbix Server or Proxy.\n\n\n- Host sending the traps needs to be configured with SNMP interface in Zabbix Server Frontend GUI.\n\n\n \n\n\nTested on Version 4.4.5", "template_file": "template_asigra_backup_snmp_traps.xml", "name": "Asigra Backup SNMP Traps" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290172, + "description": "## Overview\n\nThis template will store Asigra Client Backup Jobs (failed and successful) in Items. It also includes triggers when a Backup Job fails.\n\n\nThe triggers will NOT auto recover. So user needs to either acknowledge or close the trigger manually. \n\n\nPrerequisites:\n\n\n- SNMP Traps configured and working on Zabbix Server or Proxy.\n\n\n- Asigra Client needs to be configured to sent SNMP Traps to Zabbix Server or Proxy.\n\n\n- Host sending the traps needs to be configured with SNMP interface in Zabbix Server Frontend GUI.\n\n\n \n\n\nTested on Version 4.4.5\n", + "template_file": "template_asigra_backup_snmp_traps.yaml", + "name": "Asigra Backup SNMP Traps" + }, + { + "version": 6.0, + "sync": 1646290172, "description": "## Overview\n\nThis template will store Asigra Client Backup Jobs (failed and successful) in Items. It also includes triggers when a Backup Job fails.\n\n\nThe triggers will NOT auto recover. So user needs to either acknowledge or close the trigger manually. \n\n\nPrerequisites:\n\n\n- SNMP Traps configured and working on Zabbix Server or Proxy.\n\n\n- Asigra Client needs to be configured to sent SNMP Traps to Zabbix Server or Proxy.\n\n\n- Host sending the traps needs to be configured with SNMP interface in Zabbix Server Frontend GUI.\n\n\n \n\n\nTested on Version 4.4.5\n", "template_file": "template_asigra_backup_snmp_traps.yaml", "name": "Asigra Backup SNMP Traps" @@ -205,7 +240,7 @@ "name": "template_backuppc_monitoring", "template": "App BackupPC by Zabbix agent", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -216,14 +251,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290172, "description": "## Description\n\nThe template to monitor BackupPC metrics API by Zabbix agent without need for extra scripts on server. Template Version v0.0.1 - Evren Yurtesen Tested on Zabbix5 and BackupPC 4.4.1 (needs updated metrics)\n\n## Overview\n\nPlease see the GitHub repository for newest version and reporting issues.\n\n\n\n\n\n \n\n\nThis template requires no external scripts. \n\n\n \n\n\nIt is tested with latest BackupPC which has updated metrics. It may function partially in older BackupPC versions.\n\n\nhttps://github.com/backuppc/backuppc/pull/391\n\n\n\n## Author\n\nEvren Yurtesen", "template_file": "template_backuppc_monitoring.xml", "name": "App BackupPC by Zabbix agent" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290172, + "description": "## Description\n\nThe template to monitor BackupPC metrics API by Zabbix agent without need for extra scripts on server. Template Version v0.0.1 - Evren Yurtesen Tested on Zabbix5 and BackupPC 4.4.1 (needs updated metrics)\n\n## Overview\n\nPlease see the GitHub repository for newest version and reporting issues.\n\n\n\n\n\n \n\n\nThis template requires no external scripts. \n\n\n \n\n\nIt is tested with latest BackupPC which has updated metrics. It may function partially in older BackupPC versions.\n\n\nhttps://github.com/backuppc/backuppc/pull/391\n\n\n\n## Author\n\nEvren Yurtesen\n", + "template_file": "template_backuppc_monitoring.yaml", + "name": "App BackupPC by Zabbix agent" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Description\n\nThe template to monitor BackupPC metrics API by Zabbix agent without need for extra scripts on server. Template Version v0.0.1 - Evren Yurtesen Tested on Zabbix5 and BackupPC 4.4.1 (needs updated metrics)\n\n## Overview\n\nPlease see the GitHub repository for newest version and reporting issues.\n\n\n\n\n\n \n\n\nThis template requires no external scripts. \n\n\n \n\n\nIt is tested with latest BackupPC which has updated metrics. It may function partially in older BackupPC versions.\n\n\nhttps://github.com/backuppc/backuppc/pull/391\n\n\n\n## Author\n\nEvren Yurtesen\n", "template_file": "template_backuppc_monitoring.yaml", "name": "App BackupPC by Zabbix agent" @@ -239,7 +281,7 @@ "name": "template_nakivo_backup_&_replication", "template": "Nakivo", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -250,14 +292,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290173, "description": "## Overview\n\nExternal Zabbix Script with discovery rule for nakivo backups\n\n\n\n## Author\n\nMichael Weber", "template_file": "template_nakivo_backup_&_replication.xml", "name": "Nakivo" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290173, + "description": "## Overview\n\nExternal Zabbix Script with discovery rule for nakivo backups\n\n\n\n## Author\n\nMichael Weber\n", + "template_file": "template_nakivo_backup_&_replication.yaml", + "name": "Nakivo" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Overview\n\nExternal Zabbix Script with discovery rule for nakivo backups\n\n\n\n## Author\n\nMichael Weber\n", "template_file": "template_nakivo_backup_&_replication.yaml", "name": "Nakivo" @@ -273,7 +322,7 @@ "name": "template_restic_backup", "template": "restic backup by Zabbix agent", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -284,14 +333,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290173, "description": "## Overview\n\nGet alerts when your restic backup have failed, or didn't finish on time. The default is in last 26 hours but can be changed via a MACRO.\n \nTwo MACROs are available:\n* `{$BACKUP_STATUS_FILE}` which contain the full path of the status file. Default is `/home/backup/status.json`.\n* `{$MAX_HOURS_BETWEEN}` which contain the maximum number of hours before it triggers an alert. Default is `26` hours (for backup running once a day, plus some time if it takes a bit longer than usual).\n\n\n This is using the status file generated by [resticprofile](https://github.com/creativeprojects/resticprofile/).\n \nFor more information, see the [README](https://github.com/creativeprojects/resticprofile/tree/master/contrib/zabbix).", "template_file": "template_restic_backup.xml", "name": "restic backup by Zabbix agent" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290173, + "description": "## Overview\n\nGet alerts when your restic backup have failed, or didn't finish on time. The default is in last 26 hours but can be changed via a MACRO.\n \nTwo MACROs are available:\n* `{$BACKUP_STATUS_FILE}` which contain the full path of the status file. Default is `/home/backup/status.json`.\n* `{$MAX_HOURS_BETWEEN}` which contain the maximum number of hours before it triggers an alert. Default is `26` hours (for backup running once a day, plus some time if it takes a bit longer than usual).\n\n\n This is using the status file generated by [resticprofile](https://github.com/creativeprojects/resticprofile/).\n \nFor more information, see the [README](https://github.com/creativeprojects/resticprofile/tree/master/contrib/zabbix).\n", + "template_file": "template_restic_backup.yaml", + "name": "restic backup by Zabbix agent" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Overview\n\nGet alerts when your restic backup have failed, or didn't finish on time. The default is in last 26 hours but can be changed via a MACRO.\n \nTwo MACROs are available:\n* `{$BACKUP_STATUS_FILE}` which contain the full path of the status file. Default is `/home/backup/status.json`.\n* `{$MAX_HOURS_BETWEEN}` which contain the maximum number of hours before it triggers an alert. Default is `26` hours (for backup running once a day, plus some time if it takes a bit longer than usual).\n\n\n This is using the status file generated by [resticprofile](https://github.com/creativeprojects/resticprofile/).\n \nFor more information, see the [README](https://github.com/creativeprojects/resticprofile/tree/master/contrib/zabbix).\n", "template_file": "template_restic_backup.yaml", "name": "restic backup by Zabbix agent" @@ -307,7 +363,7 @@ "name": "template_sap_backup_tenant_systemdb", "template": "SAP Backup", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -318,14 +374,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290173, "description": "## Overview\n\n================ SAP-Backup-TENANT-SYSTEMDB ================ \n \nO presente documento tem por objetivo apresentar todas as etapas técnicas \npara implantação do monitoramento do Backup SAP utilizando shell script \ne hdbsql, e a função do Userparameter do agente Zabbix. \n \nProjeto idealizado na comunidade Zabbix Brasil no Telegram pelos usuários \nWilson Fernandes e Eduardo Freitas. \n \nA ideia do projeto foi monitorar os backups executados pelo SAP. \n \n* Data da execucão do backup \n* Status do backup do SYSTEMDB \n* Status do backup do TENANT\n\n\n\n## Author\n\nwilsonwers", "template_file": "template_sap_backup_tenant_systemdb.xml", "name": "SAP Backup" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290173, + "description": "## Overview\n\n================ SAP-Backup-TENANT-SYSTEMDB ================ \n \nO presente documento tem por objetivo apresentar todas as etapas técnicas \npara implantação do monitoramento do Backup SAP utilizando shell script \ne hdbsql, e a função do Userparameter do agente Zabbix. \n \nProjeto idealizado na comunidade Zabbix Brasil no Telegram pelos usuários \nWilson Fernandes e Eduardo Freitas. \n \nA ideia do projeto foi monitorar os backups executados pelo SAP. \n \n* Data da execucão do backup \n* Status do backup do SYSTEMDB \n* Status do backup do TENANT\n\n\n\n## Author\n\nwilsonwers\n", + "template_file": "template_sap_backup_tenant_systemdb.yaml", + "name": "SAP Backup" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Overview\n\n================ SAP-Backup-TENANT-SYSTEMDB ================ \n \nO presente documento tem por objetivo apresentar todas as etapas técnicas \npara implantação do monitoramento do Backup SAP utilizando shell script \ne hdbsql, e a função do Userparameter do agente Zabbix. \n \nProjeto idealizado na comunidade Zabbix Brasil no Telegram pelos usuários \nWilson Fernandes e Eduardo Freitas. \n \nA ideia do projeto foi monitorar os backups executados pelo SAP. \n \n* Data da execucão do backup \n* Status do backup do SYSTEMDB \n* Status do backup do TENANT\n\n\n\n## Author\n\nwilsonwers\n", "template_file": "template_sap_backup_tenant_systemdb.yaml", "name": "SAP Backup" @@ -342,7 +405,7 @@ "name": "template_tsm_client_scheduler_service", "template": "App TSM Client Scheduler", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -353,14 +416,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290173, "description": "## Overview\n\n*** Template App TSM Client Scheduler ***\n-----------------------------------------\n\n\n \n\n\nA basic template for monitoring IBM TSM Client Scheduler.\n\n\nIBM Spectrum Protect (Tivoli Storage Manager)\n\n\n- Haim Cohen 2017\n\n\n\n## Author\n\nHaim Cohen", "template_file": "template_tsm_client_scheduler_service.xml", "name": "App TSM Client Scheduler" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290173, + "description": "## Overview\n\n*** Template App TSM Client Scheduler ***\n-----------------------------------------\n\n\n \n\n\nA basic template for monitoring IBM TSM Client Scheduler.\n\n\nIBM Spectrum Protect (Tivoli Storage Manager)\n\n\n- Haim Cohen 2017\n\n\n\n## Author\n\nHaim Cohen\n", + "template_file": "template_tsm_client_scheduler_service.yaml", + "name": "App TSM Client Scheduler" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Overview\n\n*** Template App TSM Client Scheduler ***\n-----------------------------------------\n\n\n \n\n\nA basic template for monitoring IBM TSM Client Scheduler.\n\n\nIBM Spectrum Protect (Tivoli Storage Manager)\n\n\n- Haim Cohen 2017\n\n\n\n## Author\n\nHaim Cohen\n", "template_file": "template_tsm_client_scheduler_service.yaml", "name": "App TSM Client Scheduler" @@ -377,7 +447,7 @@ "name": "template_tsm_journal_service", "template": "App TSM Journal Service", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -388,14 +458,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290173, "description": "## Overview\n\nTemplate for check if \"TSM Journal Service\" is running.\n\n\n IBM Spectrum Protect (Tivoli Storage Manager)\n\n\nNote that trigger service name is: \"TSM Journal Service\"\n\n\n \n\n\nYou can also create (manual) action auto-start service in case service is down:\n\n\n \n\n\nGo to Configuration → Actions\n\n\n \n\n\n**Conditions:**\n\n\n* Maintenance status not in maintenance\n* Trigger value = PROBLEM\n* Trigger name like TSM Journal Service Stopped\n* \n* \n\n\n**Operations:**\n\n\n* **Operation type:** Remote command\n* **Commands:** NET START \"TSM Journal Service\"\n\n\n \n\n\n*- Haim Cohen 2017 -*\n\n\n\n## Author\n\nHaim Cohen", "template_file": "template_tsm_journal_service.xml", "name": "App TSM Journal Service" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290173, + "description": "## Overview\n\nTemplate for check if \"TSM Journal Service\" is running.\n\n\n IBM Spectrum Protect (Tivoli Storage Manager)\n\n\nNote that trigger service name is: \"TSM Journal Service\"\n\n\n \n\n\nYou can also create (manual) action auto-start service in case service is down:\n\n\n \n\n\nGo to Configuration → Actions\n\n\n \n\n\n**Conditions:**\n\n\n* Maintenance status not in maintenance\n* Trigger value = PROBLEM\n* Trigger name like TSM Journal Service Stopped\n* \n* \n\n\n**Operations:**\n\n\n* **Operation type:** Remote command\n* **Commands:** NET START \"TSM Journal Service\"\n\n\n \n\n\n*- Haim Cohen 2017 -*\n\n\n\n## Author\n\nHaim Cohen\n", + "template_file": "template_tsm_journal_service.yaml", + "name": "App TSM Journal Service" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Overview\n\nTemplate for check if \"TSM Journal Service\" is running.\n\n\n IBM Spectrum Protect (Tivoli Storage Manager)\n\n\nNote that trigger service name is: \"TSM Journal Service\"\n\n\n \n\n\nYou can also create (manual) action auto-start service in case service is down:\n\n\n \n\n\nGo to Configuration → Actions\n\n\n \n\n\n**Conditions:**\n\n\n* Maintenance status not in maintenance\n* Trigger value = PROBLEM\n* Trigger name like TSM Journal Service Stopped\n* \n* \n\n\n**Operations:**\n\n\n* **Operation type:** Remote command\n* **Commands:** NET START \"TSM Journal Service\"\n\n\n \n\n\n*- Haim Cohen 2017 -*\n\n\n\n## Author\n\nHaim Cohen\n", "template_file": "template_tsm_journal_service.yaml", "name": "App TSM Journal Service" @@ -412,7 +489,7 @@ "name": "template_veeam_agents_for_microsoft_windows", "template": "VEEAM-Agents", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -423,14 +500,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290173, "description": "## Overview\n\nThis template provide a way to monitor backup made by [Veeam Backup Agent for Microsoft Windows](https://www.veeam.com/windows-cloud-server-backup-agent.html).\n\n\nThere is no additionnals scripts needed, all results are read from the Windows Event Log.\n\n\nIt also monitor the service state of the application.\n\n\nThis template is made with \"zabbix active\" item, meaning it can work behind remote firewall.\n\n\n \n\n\n \n\n\n \n\n\n\n## Author\n\nCédric MARCOUX", "template_file": "template_veeam_agents_for_microsoft_windows.xml", "name": "VEEAM-Agents" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290173, + "description": "## Overview\n\nThis template provide a way to monitor backup made by [Veeam Backup Agent for Microsoft Windows](https://www.veeam.com/windows-cloud-server-backup-agent.html).\n\n\nThere is no additionnals scripts needed, all results are read from the Windows Event Log.\n\n\nIt also monitor the service state of the application.\n\n\nThis template is made with \"zabbix active\" item, meaning it can work behind remote firewall.\n\n\n \n\n\n \n\n\n \n\n\n\n## Author\n\nCédric MARCOUX\n", + "template_file": "template_veeam_agents_for_microsoft_windows.yaml", + "name": "VEEAM-Agents" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Overview\n\nThis template provide a way to monitor backup made by [Veeam Backup Agent for Microsoft Windows](https://www.veeam.com/windows-cloud-server-backup-agent.html).\n\n\nThere is no additionnals scripts needed, all results are read from the Windows Event Log.\n\n\nIt also monitor the service state of the application.\n\n\nThis template is made with \"zabbix active\" item, meaning it can work behind remote firewall.\n\n\n \n\n\n \n\n\n \n\n\n\n## Author\n\nCédric MARCOUX\n", "template_file": "template_veeam_agents_for_microsoft_windows.yaml", "name": "VEEAM-Agents" @@ -447,7 +531,7 @@ "name": "template_veeam_backup_&_replication_by_smtp", "template": "VEEAM SMTP trapper", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -458,14 +542,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290173, "description": "## Overview\n\nThis Veeam Backup & Replication use email and not Powershell snippet. It is as efficient (or more) as other method of integration with Zabbix and it requires a lot less ressources. It monitors even Backup Database backup (which others do not).\n\n\n \n\n\nUsing a specific script it can be applied to Free Agents as well.\n\n\n \n\n\nIt uses zbxsmtptrap (on an idea from here : )\n\n\n\n\n\nNB: a bug was recently corrected about Veeam sending multiline subjects - not really nice... but it can happen if you have long hostnames and happen to be sudenly out of support (which adds some garbage at the begining of the title)\n\n\n \n\n\nGive it a try!\n\n\n \n\n\nPS: to use this script with Veeam Free Agents without a VBR server (if you use a VBR server with a Free Agent, then you do not need this script because VBR will report by email to you), you'll need this small script to send the email :\n\n\n\n\n\n \n\n\n\n## Author\n\nRaynald de Lahondès", "template_file": "template_veeam_backup_&_replication_by_smtp.xml", "name": "VEEAM SMTP trapper" }, { "version": 5.4, - "sync": 1646275486, + "sync": 1646290173, + "description": "## Overview\n\nThis Veeam Backup & Replication use email and not Powershell snippet. It is as efficient (or more) as other method of integration with Zabbix and it requires a lot less ressources. It monitors even Backup Database backup (which others do not).\n\n\n \n\n\nUsing a specific script it can be applied to Free Agents as well.\n\n\n \n\n\nIt uses zbxsmtptrap (on an idea from here : )\n\n\n\n\n\nNB: a bug was recently corrected about Veeam sending multiline subjects - not really nice... but it can happen if you have long hostnames and happen to be sudenly out of support (which adds some garbage at the begining of the title)\n\n\n \n\n\nGive it a try!\n\n\n \n\n\nPS: to use this script with Veeam Free Agents without a VBR server (if you use a VBR server with a Free Agent, then you do not need this script because VBR will report by email to you), you'll need this small script to send the email :\n\n\n\n\n\n \n\n\n\n## Author\n\nRaynald de Lahondès\n", + "template_file": "template_veeam_backup_&_replication_by_smtp.yaml", + "name": "VEEAM SMTP trapper" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Overview\n\nThis Veeam Backup & Replication use email and not Powershell snippet. It is as efficient (or more) as other method of integration with Zabbix and it requires a lot less ressources. It monitors even Backup Database backup (which others do not).\n\n\n \n\n\nUsing a specific script it can be applied to Free Agents as well.\n\n\n \n\n\nIt uses zbxsmtptrap (on an idea from here : )\n\n\n\n\n\nNB: a bug was recently corrected about Veeam sending multiline subjects - not really nice... but it can happen if you have long hostnames and happen to be sudenly out of support (which adds some garbage at the begining of the title)\n\n\n \n\n\nGive it a try!\n\n\n \n\n\nPS: to use this script with Veeam Free Agents without a VBR server (if you use a VBR server with a Free Agent, then you do not need this script because VBR will report by email to you), you'll need this small script to send the email :\n\n\n\n\n\n \n\n\n\n## Author\n\nRaynald de Lahondès\n", "template_file": "template_veeam_backup_&_replication_by_smtp.yaml", "name": "VEEAM SMTP trapper" @@ -478,7 +569,7 @@ "name": "template_veritas_symantec_backup_exec_server", "template": "Backup Exec Server", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Backup", @@ -489,14 +580,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275486, + "sync": 1646290173, "description": "## Description\n\nVeritas/Simantec Backup Exec Server template All checks executes with T-SQL, so you must configure Zabbix to use FreeTDS for MS SQL Server. Backup Jobs ODBC LLD rules: - Backup Exec Windows Service - Backup Exec Jobs (FULL) - Backup Exec Jobs (INCREMENTAL) Two rules needs for creating triggers with different severity levels for Full job types and Incremental job types. Macroses {$BE.USER} and {$BE.PASSWORD} must be set on template or host level before usage. These are username and password to connect to BEDB database. LLD returns {#JOB.TYPE} macros, containig 'FULL' or 'INCR' string to determine backup job type. On database level it's: 16777216 - INCR 16973824 - FULL Documentation will be available soon on my GitHub page (https://github.com/asand3r).\n\n## Overview\n\n**Veritas/Symantec Backup Exec Server template**\n\n\nAll checks executes with T-SQL, so you must configure Zabbix to use FreeTDS for MS SQL Server. \nBackup Jobs LLD rules: \n- Backup Exec Windows Service \n- Backup Exec Jobs Discovery \n \nMacroses {$BE.USER} and {$BE.PASSWORD} **must** be set on template or host level before usage. These are username and password to connect to BEDB database. \n \nLLD returns {#JOB.TYPE} macros, containig 'full' or 'incr' string to determine backup job type. \nOn database level it's: \n16777216, 20971520 - incr \n16973824 - full \n \n\n\n\n\n## Author\n\nKhatsayuk Alexander", "template_file": "template_veritas_symantec_backup_exec_server.xml", "name": "Backup Exec Server" }, { "version": 5.4, - "sync": 1646275487, + "sync": 1646290173, + "description": "## Description\n\nVeritas/Simantec Backup Exec Server template All checks executes with T-SQL, so you must configure Zabbix to use FreeTDS for MS SQL Server. Backup Jobs ODBC LLD rules: - Backup Exec Windows Service - Backup Exec Jobs (FULL) - Backup Exec Jobs (INCREMENTAL) Two rules needs for creating triggers with different severity levels for Full job types and Incremental job types. Macroses {$BE.USER} and {$BE.PASSWORD} must be set on template or host level before usage. These are username and password to connect to BEDB database. LLD returns {#JOB.TYPE} macros, containig 'FULL' or 'INCR' string to determine backup job type. On database level it's: 16777216 - INCR 16973824 - FULL Documentation will be available soon on my GitHub page (https://github.com/asand3r).\n\n## Overview\n\n**Veritas/Symantec Backup Exec Server template**\n\n\nAll checks executes with T-SQL, so you must configure Zabbix to use FreeTDS for MS SQL Server. \nBackup Jobs LLD rules: \n- Backup Exec Windows Service \n- Backup Exec Jobs Discovery \n \nMacroses {$BE.USER} and {$BE.PASSWORD} **must** be set on template or host level before usage. These are username and password to connect to BEDB database. \n \nLLD returns {#JOB.TYPE} macros, containig 'full' or 'incr' string to determine backup job type. \nOn database level it's: \n16777216, 20971520 - incr \n16973824 - full \n \n\n\n\n\n## Author\n\nKhatsayuk Alexander\n", + "template_file": "template_veritas_symantec_backup_exec_server.yaml", + "name": "Backup Exec Server" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Description\n\nVeritas/Simantec Backup Exec Server template All checks executes with T-SQL, so you must configure Zabbix to use FreeTDS for MS SQL Server. Backup Jobs ODBC LLD rules: - Backup Exec Windows Service - Backup Exec Jobs (FULL) - Backup Exec Jobs (INCREMENTAL) Two rules needs for creating triggers with different severity levels for Full job types and Incremental job types. Macroses {$BE.USER} and {$BE.PASSWORD} must be set on template or host level before usage. These are username and password to connect to BEDB database. LLD returns {#JOB.TYPE} macros, containig 'FULL' or 'INCR' string to determine backup job type. On database level it's: 16777216 - INCR 16973824 - FULL Documentation will be available soon on my GitHub page (https://github.com/asand3r).\n\n## Overview\n\n**Veritas/Symantec Backup Exec Server template**\n\n\nAll checks executes with T-SQL, so you must configure Zabbix to use FreeTDS for MS SQL Server. \nBackup Jobs LLD rules: \n- Backup Exec Windows Service \n- Backup Exec Jobs Discovery \n \nMacroses {$BE.USER} and {$BE.PASSWORD} **must** be set on template or host level before usage. These are username and password to connect to BEDB database. \n \nLLD returns {#JOB.TYPE} macros, containig 'full' or 'incr' string to determine backup job type. \nOn database level it's: \n16777216, 20971520 - incr \n16973824 - full \n \n\n\n\n\n## Author\n\nKhatsayuk Alexander\n", "template_file": "template_veritas_symantec_backup_exec_server.yaml", "name": "Backup Exec Server" @@ -513,13 +611,13 @@ { "name": "Cluster", "type": "folder", - "sync": 1646275487, + "sync": 1646290173, "next": [ { "name": "template_corosync_status", "template": "CoroSync-Ring-0", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Cluster", @@ -530,14 +628,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275487, + "sync": 1646290173, "description": "## Overview\n\nTemplate and script below checks the status of the corosync Ring(s)\n\n\n \n\n\n1: Create a Script File under the zabbix scripts directory, called corosync.pl and paste the script content into it\n\n\n2: Make it executable and ownd by the zabbix user\n\n\n3: Add the user Parameter below to the zabbix agent on the cluster nodes\n\n\n \n\n\n**Zabbix Agent Config:**\n\n\n\n```\n**#**\n# Corosync Status\n#\nUserParameter=check\\_corosync[*], /etc/zabbix/scripts/corosync.pl $1\n```\n\n \n\n\n**Corosync Script:**\n\n\n \n\n\n#!/usr/bin/perl\n\n\n \n\n\nmy $sudo = '/usr/bin/sudo';\n\n\nmy $cfgtool = '/usr/sbin/corosync-cfgtool -s';\n\n\n \n\n\n$num\\_args = $#ARGV + 1;\n\n\nif ($num\\_args != 1) {\n\n\n print \"\\nUsage: corosync.pl ring number\\n\";\n\n\n exit;\n\n\n}\n\n\nmy $ringNumber = $ARGV[0];\n\n\nopen( $fh, \"$cfgtool |\" ) or die ( \"Running corosync-cfgtool failed\" );\n\n\nforeach my $line (<$fh>) {\n\n\n if ( $line =~ m/status\\s*=\\s*(\\S.+)/ ) {\n\n\n my $status = $1;\n\n\n if ( $status =~ m/^ring $ringNumber/ ) {\n\n\n # print \"RING NUMBER $ringNumber STATUS: $status\\n\";\n\n\n if ( $status =~ m/^ring $ringNumber active with no faults/ ) {\n\n\n print \"0\";\n\n\n } else {\n\n\n print \"1\";\n\n\n }\n\n\n exit;\n\n\n }\n\n\n }\n\n\n}\n\n\nclose($fh) or die ( \"Running corosync-cfgtool failed\" );\n\n\n \n\n\n\n## Author\n\nRoland Käser", "template_file": "template_corosync_status.xml", "name": "CoroSync-Ring-0" }, { "version": 5.4, - "sync": 1646275487, + "sync": 1646290173, + "description": "## Overview\n\nTemplate and script below checks the status of the corosync Ring(s)\n\n\n \n\n\n1: Create a Script File under the zabbix scripts directory, called corosync.pl and paste the script content into it\n\n\n2: Make it executable and ownd by the zabbix user\n\n\n3: Add the user Parameter below to the zabbix agent on the cluster nodes\n\n\n \n\n\n**Zabbix Agent Config:**\n\n\n\n```\n**#**\n# Corosync Status\n#\nUserParameter=check\\_corosync[*], /etc/zabbix/scripts/corosync.pl $1\n```\n\n \n\n\n**Corosync Script:**\n\n\n \n\n\n#!/usr/bin/perl\n\n\n \n\n\nmy $sudo = '/usr/bin/sudo';\n\n\nmy $cfgtool = '/usr/sbin/corosync-cfgtool -s';\n\n\n \n\n\n$num\\_args = $#ARGV + 1;\n\n\nif ($num\\_args != 1) {\n\n\n print \"\\nUsage: corosync.pl ring number\\n\";\n\n\n exit;\n\n\n}\n\n\nmy $ringNumber = $ARGV[0];\n\n\nopen( $fh, \"$cfgtool |\" ) or die ( \"Running corosync-cfgtool failed\" );\n\n\nforeach my $line (<$fh>) {\n\n\n if ( $line =~ m/status\\s*=\\s*(\\S.+)/ ) {\n\n\n my $status = $1;\n\n\n if ( $status =~ m/^ring $ringNumber/ ) {\n\n\n # print \"RING NUMBER $ringNumber STATUS: $status\\n\";\n\n\n if ( $status =~ m/^ring $ringNumber active with no faults/ ) {\n\n\n print \"0\";\n\n\n } else {\n\n\n print \"1\";\n\n\n }\n\n\n exit;\n\n\n }\n\n\n }\n\n\n}\n\n\nclose($fh) or die ( \"Running corosync-cfgtool failed\" );\n\n\n \n\n\n\n## Author\n\nRoland Käser\n", + "template_file": "template_corosync_status.yaml", + "name": "CoroSync-Ring-0" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Overview\n\nTemplate and script below checks the status of the corosync Ring(s)\n\n\n \n\n\n1: Create a Script File under the zabbix scripts directory, called corosync.pl and paste the script content into it\n\n\n2: Make it executable and ownd by the zabbix user\n\n\n3: Add the user Parameter below to the zabbix agent on the cluster nodes\n\n\n \n\n\n**Zabbix Agent Config:**\n\n\n\n```\n**#**\n# Corosync Status\n#\nUserParameter=check\\_corosync[*], /etc/zabbix/scripts/corosync.pl $1\n```\n\n \n\n\n**Corosync Script:**\n\n\n \n\n\n#!/usr/bin/perl\n\n\n \n\n\nmy $sudo = '/usr/bin/sudo';\n\n\nmy $cfgtool = '/usr/sbin/corosync-cfgtool -s';\n\n\n \n\n\n$num\\_args = $#ARGV + 1;\n\n\nif ($num\\_args != 1) {\n\n\n print \"\\nUsage: corosync.pl ring number\\n\";\n\n\n exit;\n\n\n}\n\n\nmy $ringNumber = $ARGV[0];\n\n\nopen( $fh, \"$cfgtool |\" ) or die ( \"Running corosync-cfgtool failed\" );\n\n\nforeach my $line (<$fh>) {\n\n\n if ( $line =~ m/status\\s*=\\s*(\\S.+)/ ) {\n\n\n my $status = $1;\n\n\n if ( $status =~ m/^ring $ringNumber/ ) {\n\n\n # print \"RING NUMBER $ringNumber STATUS: $status\\n\";\n\n\n if ( $status =~ m/^ring $ringNumber active with no faults/ ) {\n\n\n print \"0\";\n\n\n } else {\n\n\n print \"1\";\n\n\n }\n\n\n exit;\n\n\n }\n\n\n }\n\n\n}\n\n\nclose($fh) or die ( \"Running corosync-cfgtool failed\" );\n\n\n \n\n\n\n## Author\n\nRoland Käser\n", "template_file": "template_corosync_status.yaml", "name": "CoroSync-Ring-0" @@ -553,7 +658,7 @@ "name": "template_oracle_exadata", "template": "ILOM ORACLE SRV X8-2 SNMP Trap", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Cluster", @@ -564,14 +669,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275487, + "sync": 1646290173, "description": "## Description\n\nExadata Database Machine X8-2\n\n## Overview\n\nTemplate for monitoring Oracle Exadata Infraestructure.\n\n\n \n\n## Author\n\nAnael Silva | Bruno Luz", "template_file": "template_oracle_exadata.xml", "name": "ILOM ORACLE SRV X8-2 SNMP Trap" }, { "version": 5.4, - "sync": 1646275487, + "sync": 1646290173, + "description": "## Description\n\nExadata Database Machine X8-2\n\n## Overview\n\nTemplate for monitoring Oracle Exadata Infraestructure.\n\n\n \n\n## Author\n\nAnael Silva | Bruno Luz\n", + "template_file": "template_oracle_exadata.yaml", + "name": "ILOM ORACLE SRV X8-2 SNMP Trap" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Description\n\nExadata Database Machine X8-2\n\n## Overview\n\nTemplate for monitoring Oracle Exadata Infraestructure.\n\n\n \n\n## Author\n\nAnael Silva | Bruno Luz\n", "template_file": "template_oracle_exadata.yaml", "name": "ILOM ORACLE SRV X8-2 SNMP Trap" @@ -589,13 +701,13 @@ { "name": "Clustered_File_Systems", "type": "folder", - "sync": 1646275487, + "sync": 1646290173, "next": [ { "name": "template_glusterfs_discovery", "template": "Gluster Storage", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Clustered_File_Systems", @@ -606,14 +718,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275487, + "sync": 1646290173, "description": "## Overview\n\n This project was created to monitor Gluster Storage with Zabbix. In this repository there are two files. One python script that calls [gstatus](https://github.com/gluster/gstatus), discovering gluster volumes and print data we want, according to the arguments given. You have to install gstatus [gstatus](https://github.com/gluster/gstatus)\n\n\nYou should save the script in any directory you want, in order to do it executable from zabbix user using sudo. You have to create a file in /etc/zabbix/zabbix\\_server.conf.d/ and add UserParameters:\n\n\n* You should save the script in any directory you want, do it executable from zabbix user using sudo.\n* You have to create a file in /etc/zabbix/zabbix\\_server.conf.d/ and add UserParameters: ... UserParameter=gluster\\_volume\\_info[*],sudo /path/gstatus\\_discovery.py $1 $2 UserParameter=gluster\\_storage\\_info[*],sudo /path/gstatus\\_discovery.py $1 UserParameter=gluster\\_volume\\_info,sudo /path/gstatus\\_discovery.py\n* The last one shoud be import zabbix\\_template.xml in zabbix\n\n\nYou can check my [github repository](https://github.com/MrCirca/zabbix-glusterfs)\n\n\n\n## Author\n\nMrCirca", "template_file": "template_glusterfs_discovery.xml", "name": "Gluster Storage" }, { "version": 5.4, - "sync": 1646275487, + "sync": 1646290173, + "description": "## Overview\n\n This project was created to monitor Gluster Storage with Zabbix. In this repository there are two files. One python script that calls [gstatus](https://github.com/gluster/gstatus), discovering gluster volumes and print data we want, according to the arguments given. You have to install gstatus [gstatus](https://github.com/gluster/gstatus)\n\n\nYou should save the script in any directory you want, in order to do it executable from zabbix user using sudo. You have to create a file in /etc/zabbix/zabbix\\_server.conf.d/ and add UserParameters:\n\n\n* You should save the script in any directory you want, do it executable from zabbix user using sudo.\n* You have to create a file in /etc/zabbix/zabbix\\_server.conf.d/ and add UserParameters: ... UserParameter=gluster\\_volume\\_info[*],sudo /path/gstatus\\_discovery.py $1 $2 UserParameter=gluster\\_storage\\_info[*],sudo /path/gstatus\\_discovery.py $1 UserParameter=gluster\\_volume\\_info,sudo /path/gstatus\\_discovery.py\n* The last one shoud be import zabbix\\_template.xml in zabbix\n\n\nYou can check my [github repository](https://github.com/MrCirca/zabbix-glusterfs)\n\n\n\n## Author\n\nMrCirca\n", + "template_file": "template_glusterfs_discovery.yaml", + "name": "Gluster Storage" + }, + { + "version": 6.0, + "sync": 1646290173, "description": "## Overview\n\n This project was created to monitor Gluster Storage with Zabbix. In this repository there are two files. One python script that calls [gstatus](https://github.com/gluster/gstatus), discovering gluster volumes and print data we want, according to the arguments given. You have to install gstatus [gstatus](https://github.com/gluster/gstatus)\n\n\nYou should save the script in any directory you want, in order to do it executable from zabbix user using sudo. You have to create a file in /etc/zabbix/zabbix\\_server.conf.d/ and add UserParameters:\n\n\n* You should save the script in any directory you want, do it executable from zabbix user using sudo.\n* You have to create a file in /etc/zabbix/zabbix\\_server.conf.d/ and add UserParameters: ... UserParameter=gluster\\_volume\\_info[*],sudo /path/gstatus\\_discovery.py $1 $2 UserParameter=gluster\\_storage\\_info[*],sudo /path/gstatus\\_discovery.py $1 UserParameter=gluster\\_volume\\_info,sudo /path/gstatus\\_discovery.py\n* The last one shoud be import zabbix\\_template.xml in zabbix\n\n\nYou can check my [github repository](https://github.com/MrCirca/zabbix-glusterfs)\n\n\n\n## Author\n\nMrCirca\n", "template_file": "template_glusterfs_discovery.yaml", "name": "Gluster Storage" @@ -630,13 +749,13 @@ { "name": "DNS", "type": "folder", - "sync": 1646275487, + "sync": 1646290174, "next": [ { "name": "template_app_powerdns_dnsdist", "template": "App PowerDNS dnsdist", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "DNS", @@ -647,14 +766,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275487, + "sync": 1646290173, "description": "## Description\n\nSelf-contained Zabbix template to get information about PowerDNS dnsdist. Source: https://github.com/frei-style/zabbix-powerdns-dnsdist-template/\n\n## Overview\n\nSelf-contained Zabbix template to get information about PowerDNS dnsdist.\n\n\nFor installation instructions see: [https://github.com/frei-style/zabbix-powerdns-dnsdist-template](cat-app/dns/app-powerdns-dnsdist/visit)\n\n\n\n## Author\n\nManuel Frei", "template_file": "template_app_powerdns_dnsdist.xml", "name": "App PowerDNS dnsdist" }, { "version": 5.4, - "sync": 1646275487, + "sync": 1646290174, + "description": "## Description\n\nSelf-contained Zabbix template to get information about PowerDNS dnsdist. Source: https://github.com/frei-style/zabbix-powerdns-dnsdist-template/\n\n## Overview\n\nSelf-contained Zabbix template to get information about PowerDNS dnsdist.\n\n\nFor installation instructions see: [https://github.com/frei-style/zabbix-powerdns-dnsdist-template](cat-app/dns/app-powerdns-dnsdist/visit)\n\n\n\n## Author\n\nManuel Frei\n", + "template_file": "template_app_powerdns_dnsdist.yaml", + "name": "App PowerDNS dnsdist" + }, + { + "version": 6.0, + "sync": 1646290174, "description": "## Description\n\nSelf-contained Zabbix template to get information about PowerDNS dnsdist. Source: https://github.com/frei-style/zabbix-powerdns-dnsdist-template/\n\n## Overview\n\nSelf-contained Zabbix template to get information about PowerDNS dnsdist.\n\n\nFor installation instructions see: [https://github.com/frei-style/zabbix-powerdns-dnsdist-template](cat-app/dns/app-powerdns-dnsdist/visit)\n\n\n\n## Author\n\nManuel Frei\n", "template_file": "template_app_powerdns_dnsdist.yaml", "name": "App PowerDNS dnsdist" @@ -671,7 +797,7 @@ "name": "template_bind_recursive_queries", "template": "Bind queries", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "DNS", @@ -682,14 +808,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275487, + "sync": 1646290174, "description": "## Description\n\n/etc/zabbix/zabbix_agentd.d/userparameter_bind.conf: UserParameter=bind.tcpcl,/bin/cat /tmp/namedtcp.log UserParameter=bind.udpcl,/bin/cat /tmp/namedudp.log --------------- cron every 30 sec: /var/spool/cron/root: SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin 0-59 * * * * /etc/zabbix/custom/named.sh 0-59 * * * * ( sleep 30; /etc/zabbix/custom/named.sh ) /etc/zabbix/custom/named.sh: #!/bin/bash /usr/local/named/sbin/rndc status > /tmp/rndcstatus cat /tmp/rndcstatus | grep tcp | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedtcp.log cat /tmp/rndcstatus | grep recursive | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedudp.log ----------------------------- add key for rndc in config of named\n\n## Overview\n\nShows recursive queries on your BIND server. Triggers on excesive usage. Best for caching servers.\n\n\n \n\n\nInstalation description:\n\n\n/etc/zabbix/zabbix\\_agentd.d/userparameter\\_bind.conf: \n \nUserParameter=bind.tcpcl,/bin/cat /tmp/namedtcp.log \nUserParameter=bind.udpcl,/bin/cat /tmp/namedudp.log \n \n--------------- \ncron every 30 sec: \n /var/spool/cron/root: \n \nSHELL=/bin/sh \nPATH=/sbin:/bin:/usr/sbin:/usr/bin \n0-59 * * * * /etc/zabbix/custom/named.sh \n0-59 * * * * ( sleep 30; /etc/zabbix/custom/named.sh ) \n \nchmod +x /etc/zabbix/custom/named.sh: \n \n#!/bin/bash \n/usr/local/named/sbin/rndc status > /tmp/rndcstatus \ncat /tmp/rndcstatus | grep tcp | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedtcp.log \ncat /tmp/rndcstatus | grep recursive | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedudp.log \n \n----------------------------- \nadd key for rndc in config of named", "template_file": "template_bind_recursive_queries.xml", "name": "Bind queries" }, { "version": 5.4, - "sync": 1646275487, + "sync": 1646290174, + "description": "## Description\n\n/etc/zabbix/zabbix_agentd.d/userparameter_bind.conf: UserParameter=bind.tcpcl,/bin/cat /tmp/namedtcp.log UserParameter=bind.udpcl,/bin/cat /tmp/namedudp.log --------------- cron every 30 sec: /var/spool/cron/root: SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin 0-59 * * * * /etc/zabbix/custom/named.sh 0-59 * * * * ( sleep 30; /etc/zabbix/custom/named.sh ) /etc/zabbix/custom/named.sh: #!/bin/bash /usr/local/named/sbin/rndc status > /tmp/rndcstatus cat /tmp/rndcstatus | grep tcp | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedtcp.log cat /tmp/rndcstatus | grep recursive | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedudp.log ----------------------------- add key for rndc in config of named\n\n## Overview\n\nShows recursive queries on your BIND server. Triggers on excesive usage. Best for caching servers.\n\n\n \n\n\nInstalation description:\n\n\n/etc/zabbix/zabbix\\_agentd.d/userparameter\\_bind.conf: \n \nUserParameter=bind.tcpcl,/bin/cat /tmp/namedtcp.log \nUserParameter=bind.udpcl,/bin/cat /tmp/namedudp.log \n \n--------------- \ncron every 30 sec: \n /var/spool/cron/root: \n \nSHELL=/bin/sh \nPATH=/sbin:/bin:/usr/sbin:/usr/bin \n0-59 * * * * /etc/zabbix/custom/named.sh \n0-59 * * * * ( sleep 30; /etc/zabbix/custom/named.sh ) \n \nchmod +x /etc/zabbix/custom/named.sh: \n \n#!/bin/bash \n/usr/local/named/sbin/rndc status > /tmp/rndcstatus \ncat /tmp/rndcstatus | grep tcp | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedtcp.log \ncat /tmp/rndcstatus | grep recursive | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedudp.log \n \n----------------------------- \nadd key for rndc in config of named\n", + "template_file": "template_bind_recursive_queries.yaml", + "name": "Bind queries" + }, + { + "version": 6.0, + "sync": 1646290174, "description": "## Description\n\n/etc/zabbix/zabbix_agentd.d/userparameter_bind.conf: UserParameter=bind.tcpcl,/bin/cat /tmp/namedtcp.log UserParameter=bind.udpcl,/bin/cat /tmp/namedudp.log --------------- cron every 30 sec: /var/spool/cron/root: SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin 0-59 * * * * /etc/zabbix/custom/named.sh 0-59 * * * * ( sleep 30; /etc/zabbix/custom/named.sh ) /etc/zabbix/custom/named.sh: #!/bin/bash /usr/local/named/sbin/rndc status > /tmp/rndcstatus cat /tmp/rndcstatus | grep tcp | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedtcp.log cat /tmp/rndcstatus | grep recursive | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedudp.log ----------------------------- add key for rndc in config of named\n\n## Overview\n\nShows recursive queries on your BIND server. Triggers on excesive usage. Best for caching servers.\n\n\n \n\n\nInstalation description:\n\n\n/etc/zabbix/zabbix\\_agentd.d/userparameter\\_bind.conf: \n \nUserParameter=bind.tcpcl,/bin/cat /tmp/namedtcp.log \nUserParameter=bind.udpcl,/bin/cat /tmp/namedudp.log \n \n--------------- \ncron every 30 sec: \n /var/spool/cron/root: \n \nSHELL=/bin/sh \nPATH=/sbin:/bin:/usr/sbin:/usr/bin \n0-59 * * * * /etc/zabbix/custom/named.sh \n0-59 * * * * ( sleep 30; /etc/zabbix/custom/named.sh ) \n \nchmod +x /etc/zabbix/custom/named.sh: \n \n#!/bin/bash \n/usr/local/named/sbin/rndc status > /tmp/rndcstatus \ncat /tmp/rndcstatus | grep tcp | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedtcp.log \ncat /tmp/rndcstatus | grep recursive | awk '{ print $3 }' | cut -d '/' -f 1 > /tmp/namedudp.log \n \n----------------------------- \nadd key for rndc in config of named\n", "template_file": "template_bind_recursive_queries.yaml", "name": "Bind queries" @@ -706,7 +839,7 @@ "name": "template_bind_stat", "template": "DNS-bind", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "DNS", @@ -717,14 +850,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275487, + "sync": 1646290174, "description": "## Overview\n\n**Requirements** \n Bind Server 9 and above \n Zabbix Server 4+ and above \n Zabbix Agent on monitored host \n \n \n**How it works** \nInclude statistics in named.conf \n \nstatistics-channels { \n inet 127.0.0.1 port 8053 allow { 127.0.0.1; }; \n };\n\n\nInclude - zabbix\\_agentd.d/bind.conf \nUserParameter=bind.net.udp,netstat -nua | grep :53 | wc -l \nUserParameter=bind.net.tcp,netstat -nta | grep :53 | wc -l \nUserParameter=bind.queries.in[*],curl http://127.0.0.1:8053/ 2>/dev/null | xml2 | grep -A1 \"/statistics/server/counters/counter/@name=$1$\" | tail -1 | cut -d= -f2 \nUserParameter=bind.queries.out[*],curl http://127.0.0.1:8053/ 2>/dev/null | xml2 | grep -A1 \"/statistics/views/view/counters/counter/@name=$1$\" | tail -1 | cut -d= -f2 \nUserParameter=bind.queries.query[*],curl http://127.0.0.1:8053/ 2>/dev/null | xml2 | grep -A1 \"/statistics/server/counters/counter/@name=Qry$1$\" | tail -1 | cut -d= -f2\n\n\n![](http://img.dzek.ru/images/dns.jpg)", "template_file": "template_bind_stat.xml", "name": "DNS-bind" }, { "version": 5.4, - "sync": 1646275487, + "sync": 1646290174, + "description": "## Overview\n\n**Requirements** \n Bind Server 9 and above \n Zabbix Server 4+ and above \n Zabbix Agent on monitored host \n \n \n**How it works** \nInclude statistics in named.conf \n \nstatistics-channels { \n inet 127.0.0.1 port 8053 allow { 127.0.0.1; }; \n };\n\n\nInclude - zabbix\\_agentd.d/bind.conf \nUserParameter=bind.net.udp,netstat -nua | grep :53 | wc -l \nUserParameter=bind.net.tcp,netstat -nta | grep :53 | wc -l \nUserParameter=bind.queries.in[*],curl http://127.0.0.1:8053/ 2>/dev/null | xml2 | grep -A1 \"/statistics/server/counters/counter/@name=$1$\" | tail -1 | cut -d= -f2 \nUserParameter=bind.queries.out[*],curl http://127.0.0.1:8053/ 2>/dev/null | xml2 | grep -A1 \"/statistics/views/view/counters/counter/@name=$1$\" | tail -1 | cut -d= -f2 \nUserParameter=bind.queries.query[*],curl http://127.0.0.1:8053/ 2>/dev/null | xml2 | grep -A1 \"/statistics/server/counters/counter/@name=Qry$1$\" | tail -1 | cut -d= -f2\n\n\n![](http://img.dzek.ru/images/dns.jpg)\n", + "template_file": "template_bind_stat.yaml", + "name": "DNS-bind" + }, + { + "version": 6.0, + "sync": 1646290174, "description": "## Overview\n\n**Requirements** \n Bind Server 9 and above \n Zabbix Server 4+ and above \n Zabbix Agent on monitored host \n \n \n**How it works** \nInclude statistics in named.conf \n \nstatistics-channels { \n inet 127.0.0.1 port 8053 allow { 127.0.0.1; }; \n };\n\n\nInclude - zabbix\\_agentd.d/bind.conf \nUserParameter=bind.net.udp,netstat -nua | grep :53 | wc -l \nUserParameter=bind.net.tcp,netstat -nta | grep :53 | wc -l \nUserParameter=bind.queries.in[*],curl http://127.0.0.1:8053/ 2>/dev/null | xml2 | grep -A1 \"/statistics/server/counters/counter/@name=$1$\" | tail -1 | cut -d= -f2 \nUserParameter=bind.queries.out[*],curl http://127.0.0.1:8053/ 2>/dev/null | xml2 | grep -A1 \"/statistics/views/view/counters/counter/@name=$1$\" | tail -1 | cut -d= -f2 \nUserParameter=bind.queries.query[*],curl http://127.0.0.1:8053/ 2>/dev/null | xml2 | grep -A1 \"/statistics/server/counters/counter/@name=Qry$1$\" | tail -1 | cut -d= -f2\n\n\n![](http://img.dzek.ru/images/dns.jpg)\n", "template_file": "template_bind_stat.yaml", "name": "DNS-bind" @@ -741,7 +881,7 @@ "name": "template_knot_resolver", "template": "Knot Resolver Statistics", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "DNS", @@ -752,14 +892,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275487, + "sync": 1646290174, "description": "## Description\n\nCollects statistic values from Knot Resolver\n\n## Overview\n\nKnot Resolver statistics\n\n\nRequirements\n------------\n\n\n* None\n\n\nInstallation\n------------\n\n\n* Import the template\n* If needed, modify *{$KRESD\\_STATS\\_URL}* macro on the Host (under Inherited and host macros) to the URL of your Knot Resolver statistics service, usually *https://localhost:8453/stats* or *http://localhost:8053/stats*\n\n\nTested on Zabbix 4.0.11\n\n\nBased on template from https://github.com/heximcz/kresd-stats-zabbix\n\n\n\n## Author\n\nVáclav Nováček", "template_file": "template_knot_resolver.xml", "name": "Knot Resolver Statistics" }, { "version": 5.4, - "sync": 1646275487, + "sync": 1646290174, + "description": "## Description\n\nCollects statistic values from Knot Resolver\n\n## Overview\n\nKnot Resolver statistics\n\n\nRequirements\n------------\n\n\n* None\n\n\nInstallation\n------------\n\n\n* Import the template\n* If needed, modify *{$KRESD\\_STATS\\_URL}* macro on the Host (under Inherited and host macros) to the URL of your Knot Resolver statistics service, usually *https://localhost:8453/stats* or *http://localhost:8053/stats*\n\n\nTested on Zabbix 4.0.11\n\n\nBased on template from https://github.com/heximcz/kresd-stats-zabbix\n\n\n\n## Author\n\nVáclav Nováček\n", + "template_file": "template_knot_resolver.yaml", + "name": "Knot Resolver Statistics" + }, + { + "version": 6.0, + "sync": 1646290174, "description": "## Description\n\nCollects statistic values from Knot Resolver\n\n## Overview\n\nKnot Resolver statistics\n\n\nRequirements\n------------\n\n\n* None\n\n\nInstallation\n------------\n\n\n* Import the template\n* If needed, modify *{$KRESD\\_STATS\\_URL}* macro on the Host (under Inherited and host macros) to the URL of your Knot Resolver statistics service, usually *https://localhost:8453/stats* or *http://localhost:8053/stats*\n\n\nTested on Zabbix 4.0.11\n\n\nBased on template from https://github.com/heximcz/kresd-stats-zabbix\n\n\n\n## Author\n\nVáclav Nováček\n", "template_file": "template_knot_resolver.yaml", "name": "Knot Resolver Statistics" @@ -776,7 +923,7 @@ "name": "template_net.dns.perf", "template": "net.dns.perf", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "DNS", @@ -787,14 +934,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275487, + "sync": 1646290174, "description": "## Description\n\nDNS応答時間測定\n\n## Overview\n\nDNSの応答性能を測定します。\n\n\nテンプレートを利用する場合zabbix\\_agentd.confでリモートコマンドを有効にしてください。\n\n\nEnableRemoteCommands=1 \nUnsafeUserParameters=1\n\n\nマクロ\n\n\n{$DNS\\_SERVER}＝利用するDNSサーバを指定します。 \n{$DOMAIN\\_NAME}＝対象ドメイン名を指定します。", "template_file": "template_net.dns.perf.xml", "name": "net.dns.perf" }, { "version": 5.4, - "sync": 1646275487, + "sync": 1646290174, + "description": "## Description\n\nDNS応答時間測定\n\n## Overview\n\nDNSの応答性能を測定します。\n\n\nテンプレートを利用する場合zabbix\\_agentd.confでリモートコマンドを有効にしてください。\n\n\nEnableRemoteCommands=1 \nUnsafeUserParameters=1\n\n\nマクロ\n\n\n{$DNS\\_SERVER}＝利用するDNSサーバを指定します。 \n{$DOMAIN\\_NAME}＝対象ドメイン名を指定します。 \n", + "template_file": "template_net.dns.perf.yaml", + "name": "net.dns.perf" + }, + { + "version": 6.0, + "sync": 1646290174, "description": "## Description\n\nDNS応答時間測定\n\n## Overview\n\nDNSの応答性能を測定します。\n\n\nテンプレートを利用する場合zabbix\\_agentd.confでリモートコマンドを有効にしてください。\n\n\nEnableRemoteCommands=1 \nUnsafeUserParameters=1\n\n\nマクロ\n\n\n{$DNS\\_SERVER}＝利用するDNSサーバを指定します。 \n{$DOMAIN\\_NAME}＝対象ドメイン名を指定します。 \n", "template_file": "template_net.dns.perf.yaml", "name": "net.dns.perf" @@ -811,7 +965,7 @@ "name": "template_pihole_daemon_check", "template": "pihole-FTL over zabbix active agent", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "DNS", @@ -822,14 +976,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275487, + "sync": 1646290174, "description": "## Description\n\npihole-FTL [zabbix active agent] check status pihole-FTL service if not \"start\" send alarm triger\n\n## Overview\n\ncheck status pihole-FTL service\n\n\nif not \"start\" send alarm triger\n\n\n\n## Author\n\nwhyborn", "template_file": "template_pihole_daemon_check.xml", "name": "pihole-FTL over zabbix active agent" }, { "version": 5.4, - "sync": 1646275487, + "sync": 1646290174, + "description": "## Description\n\npihole-FTL [zabbix active agent] check status pihole-FTL service if not \"start\" send alarm triger\n\n## Overview\n\ncheck status pihole-FTL service\n\n\nif not \"start\" send alarm triger\n\n\n\n## Author\n\nwhyborn\n", + "template_file": "template_pihole_daemon_check.yaml", + "name": "pihole-FTL over zabbix active agent" + }, + { + "version": 6.0, + "sync": 1646290174, "description": "## Description\n\npihole-FTL [zabbix active agent] check status pihole-FTL service if not \"start\" send alarm triger\n\n## Overview\n\ncheck status pihole-FTL service\n\n\nif not \"start\" send alarm triger\n\n\n\n## Author\n\nwhyborn\n", "template_file": "template_pihole_daemon_check.yaml", "name": "pihole-FTL over zabbix active agent" @@ -847,13 +1008,13 @@ { "name": "Excel_Export", "type": "folder", - "sync": 1646275488, + "sync": 1646290175, "next": [ { "name": "template_nexus_3xxx", "template": "NEXUS 3xxx", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Excel_Export", @@ -864,14 +1025,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275487, + "sync": 1646290174, "description": "## Description\n\nA template to monitor nexus switch via SNMP\n\n## Overview\n\nA Nexus 3xxx template to get SNMP system informations.\n\n\nThis template will find interface, CPU, Fan, create graphs, check ip/tcp/udp/icmp information, create some triggers etc...\n\n\nAll items, triggers and discovery rules have brief descriptions.\n\n\nIf SNMP is not your friend, you can check this web page (https://cric.grenoble.cnrs.fr/Administrateurs/Outils/MIBS/?oid=1.3.6.1.2.1) to help you.\n\n\n\n## Author\n\nLeo Cardao", "template_file": "template_nexus_3xxx.xml", "name": "NEXUS 3xxx" }, { "version": 5.4, - "sync": 1646275488, + "sync": 1646290175, + "description": "## Description\n\nA template to monitor nexus switch via SNMP\n\n## Overview\n\nA Nexus 3xxx template to get SNMP system informations.\n\n\nThis template will find interface, CPU, Fan, create graphs, check ip/tcp/udp/icmp information, create some triggers etc...\n\n\nAll items, triggers and discovery rules have brief descriptions.\n\n\nIf SNMP is not your friend, you can check this web page (https://cric.grenoble.cnrs.fr/Administrateurs/Outils/MIBS/?oid=1.3.6.1.2.1) to help you.\n\n\n\n## Author\n\nLeo Cardao\n", + "template_file": "template_nexus_3xxx.yaml", + "name": "NEXUS 3xxx" + }, + { + "version": 6.0, + "sync": 1646290175, "description": "## Description\n\nA template to monitor nexus switch via SNMP\n\n## Overview\n\nA Nexus 3xxx template to get SNMP system informations.\n\n\nThis template will find interface, CPU, Fan, create graphs, check ip/tcp/udp/icmp information, create some triggers etc...\n\n\nAll items, triggers and discovery rules have brief descriptions.\n\n\nIf SNMP is not your friend, you can check this web page (https://cric.grenoble.cnrs.fr/Administrateurs/Outils/MIBS/?oid=1.3.6.1.2.1) to help you.\n\n\n\n## Author\n\nLeo Cardao\n", "template_file": "template_nexus_3xxx.yaml", "name": "NEXUS 3xxx" @@ -890,13 +1058,13 @@ { "name": "Firewall", "type": "folder", - "sync": 1646275488, + "sync": 1646290176, "next": [ { "name": "template_fail2ban", "template": "Fail2ban", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Firewall", @@ -907,14 +1075,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275488, + "sync": 1646290175, "description": "## Overview\n\nFail2Ban template for Zabbix\n============================\n\n\n**Features:**\n\n\nAutomatic discovery of jails\n\n\nMonitor service status\n\n\nMonitor jails\n\n\nJails graph\n\n\n \n\n\n**The installation instruction is in this repository.** [github.com/hermanekt/zabbix-fail2ban-discovery-](cat-app/firewall/fail2ban/visit)\n\n\n\n## Author\n\nTomas Hermanek", "template_file": "template_fail2ban.xml", "name": "Fail2ban" }, { "version": 5.4, - "sync": 1646275488, + "sync": 1646290175, + "description": "## Overview\n\nFail2Ban template for Zabbix\n============================\n\n\n**Features:**\n\n\nAutomatic discovery of jails\n\n\nMonitor service status\n\n\nMonitor jails\n\n\nJails graph\n\n\n \n\n\n**The installation instruction is in this repository.** [github.com/hermanekt/zabbix-fail2ban-discovery-](cat-app/firewall/fail2ban/visit)\n\n\n\n## Author\n\nTomas Hermanek\n", + "template_file": "template_fail2ban.yaml", + "name": "Fail2ban" + }, + { + "version": 6.0, + "sync": 1646290175, "description": "## Overview\n\nFail2Ban template for Zabbix\n============================\n\n\n**Features:**\n\n\nAutomatic discovery of jails\n\n\nMonitor service status\n\n\nMonitor jails\n\n\nJails graph\n\n\n \n\n\n**The installation instruction is in this repository.** [github.com/hermanekt/zabbix-fail2ban-discovery-](cat-app/firewall/fail2ban/visit)\n\n\n\n## Author\n\nTomas Hermanek\n", "template_file": "template_fail2ban.yaml", "name": "Fail2ban" @@ -930,7 +1105,7 @@ "name": "template_vipnet_ids_snmpv2", "template": "ViPNet IDS SNMPv2", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Firewall", @@ -941,14 +1116,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275488, + "sync": 1646290175, "description": "## Description\n\nViPNet IDS SNMPv2 template\n\n## Overview\n\nInfotecs ViPNet IDS \n\n\n \n\n\n\n## Author\n\nAntik89", "template_file": "template_vipnet_ids_snmpv2.xml", "name": "ViPNet IDS SNMPv2" }, { "version": 5.4, - "sync": 1646275488, + "sync": 1646290176, + "description": "## Description\n\nViPNet IDS SNMPv2 template\n\n## Overview\n\nInfotecs ViPNet IDS \n\n\n \n\n\n\n## Author\n\nAntik89\n", + "template_file": "template_vipnet_ids_snmpv2.yaml", + "name": "ViPNet IDS SNMPv2" + }, + { + "version": 6.0, + "sync": 1646290176, "description": "## Description\n\nViPNet IDS SNMPv2 template\n\n## Overview\n\nInfotecs ViPNet IDS \n\n\n \n\n\n\n## Author\n\nAntik89\n", "template_file": "template_vipnet_ids_snmpv2.yaml", "name": "ViPNet IDS SNMPv2" @@ -966,13 +1148,13 @@ { "name": "Gitlab", "type": "folder", - "sync": 1646275488, + "sync": 1646290176, "next": [ { "name": "template_gitlab_update_check", "template": "Template Gitlab Update Check", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Gitlab", @@ -983,7 +1165,7 @@ "versions": [ { "version": 5.0, - "sync": 1646275488, + "sync": 1646290176, "description": "", "template_file": "zabbix_template_gitlab_update_check.xml", "name": "Template Gitlab Update Check" @@ -997,13 +1179,13 @@ { "name": "High_Availability_(HA)", "type": "folder", - "sync": 1646275488, + "sync": 1646290176, "next": [ { "name": "template_haproxy_using_socket", "template": "HAProxy", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "High_Availability_(HA)", @@ -1014,7 +1196,7 @@ "versions": [ { "version": 5.0, - "sync": 1646275488, + "sync": 1646290176, "description": "## Overview\n\n How to install:\n\n\n1. Add in HAProxy (or make sure that you have) next rules to enable statistics on socket\n\n\nvi /etc/haproxy/haproxy.cfg \nstats socket /var/lib/haproxy/stats mode 666 level admin \nstats timeout 30s \n\n\n\n2. Install socat and nc: yum install nc socat -yum\n\n\n3. Make sure that HAProxy user can read from socket :sudo -uhaproxy echo \"show info;show stat\" | socat stdio unix-connect:/var/lib/haproxy/stats\n\n\n4. Copy files:\n\n\na) `userparameter\\_haproxy.conf` in `/etc/zabbix/zabbix\\_agentd.d/`\n\n\nb) haproxy\\_discovery.sh in /etc/zabbix/scripts/\n\n\nc) haproxy\\_stats.sh in /etc/zabbix/scripts/ \n \nMake b and c scripts executable with chmod +x script\\_name \n \nNote: Make sure that /etc/zabbix/scripts/ exist, if not, create it: mkdir -p /etc/zabbix/scripts/ \n \n5. Add host for HAProxy in Zabbix, add template, wait some time for get data \n \n(You can change LLD discovery time to get data more faster, but after change to initial) \n \nThis template is based on: \n \na) Solution by Anastas Dancha - https://github.com/anapsix/zabbix-haproxy \n \nb) Official template from Zabbix for Zabbix > 4.4 - https://www.zabbix.com/integrations/haproxy \n \nThe reason why I create this template was to have official zabbix template logic in Zabbix under 4.4 \n \nFiles are there \n \na) https://cloud.mail.ru/public/D2M5%2F7ZEamjnVF \n \nb) https://drive.google.com/open?id=16xoJyWut9R\\_EudcRyAf2Ui8WuPyTxw6D \n \nWrite to tudorticau@mail.ru if something is not clear \n \nHave a nice day\n\n\n\n## Author\n\nTudor Ticau", "template_file": "template_haproxy_using_socket.xml", "name": "HAProxy" @@ -1032,13 +1214,13 @@ { "name": "Java_Application", "type": "folder", - "sync": 1646275488, + "sync": 1646290177, "next": [ { "name": "template_app_generic_java_jmx_with_metaspace", "template": "Template App Generic Java JMX", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Java_Application", @@ -1049,14 +1231,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275488, + "sync": 1646290176, "description": "", "template_file": "template_app_generic_java_jmx_with_metaspace.xml", "name": "Template App Generic Java JMX" }, { "version": 5.4, - "sync": 1646275488, + "sync": 1646290176, + "description": "", + "template_file": "template_app_generic_java_jmx_with_metaspace.yaml", + "name": "Template App Generic Java JMX" + }, + { + "version": 6.0, + "sync": 1646290176, "description": "", "template_file": "template_app_generic_java_jmx_with_metaspace.yaml", "name": "Template App Generic Java JMX" @@ -1073,7 +1262,7 @@ "name": "template_glassfish_webserver", "template": "App Glassfish server.jvm", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Java_Application", @@ -1084,14 +1273,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275488, + "sync": 1646290176, "description": "## Overview\n\n#SO LUONG KET NOI TICH LUY\n\n\nUserParameter=glassfish.counttotalconnections-starttime,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.counttotalconnections-starttime | grep server |cut -d ' ' -f3\n\n\nUserParameter=glassfish.counttotalconnections-count,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.counttotalconnections-count | grep server |cut -d ' ' -f3\n\n\n#SO LUONG KET NOI DANG MO\n\n\nUserParameter=glassfish.countopenconnections-count,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.countopenconnections-count | grep server |cut -d ' ' -f3\n\n\n#SO LUONG KET NOI CO DUOC TRONG 5 PHUT\n\n\nUserParameter=glassfish.countqueued5minutesaverage-count,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.countqueued5minutesaverage-count | grep server |cut -d ' ' -f3", "template_file": "template_glassfish_webserver.xml", "name": "App Glassfish server.jvm" }, { "version": 5.4, - "sync": 1646275488, + "sync": 1646290176, + "description": "## Overview\n\n#SO LUONG KET NOI TICH LUY\n\n\nUserParameter=glassfish.counttotalconnections-starttime,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.counttotalconnections-starttime | grep server |cut -d ' ' -f3\n\n\nUserParameter=glassfish.counttotalconnections-count,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.counttotalconnections-count | grep server |cut -d ' ' -f3\n\n\n#SO LUONG KET NOI DANG MO\n\n\nUserParameter=glassfish.countopenconnections-count,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.countopenconnections-count | grep server |cut -d ' ' -f3\n\n\n#SO LUONG KET NOI CO DUOC TRONG 5 PHUT\n\n\nUserParameter=glassfish.countqueued5minutesaverage-count,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.countqueued5minutesaverage-count | grep server |cut -d ' ' -f3\n\n\n \n\n\n \n", + "template_file": "template_glassfish_webserver.yaml", + "name": "App Glassfish server.jvm" + }, + { + "version": 6.0, + "sync": 1646290176, "description": "## Overview\n\n#SO LUONG KET NOI TICH LUY\n\n\nUserParameter=glassfish.counttotalconnections-starttime,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.counttotalconnections-starttime | grep server |cut -d ' ' -f3\n\n\nUserParameter=glassfish.counttotalconnections-count,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.counttotalconnections-count | grep server |cut -d ' ' -f3\n\n\n#SO LUONG KET NOI DANG MO\n\n\nUserParameter=glassfish.countopenconnections-count,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.countopenconnections-count | grep server |cut -d ' ' -f3\n\n\n#SO LUONG KET NOI CO DUOC TRONG 5 PHUT\n\n\nUserParameter=glassfish.countqueued5minutesaverage-count,/home/glassfish/bin/asadmin --passwordfile /home/webserver2/asadminpass get --monitor server.network.http-listener-1.connection-queue.countqueued5minutesaverage-count | grep server |cut -d ' ' -f3\n\n\n \n\n\n \n", "template_file": "template_glassfish_webserver.yaml", "name": "App Glassfish server.jvm" @@ -1108,7 +1304,7 @@ "name": "template_jvm_and_g1_gc_monitoring_with_jmx", "template": "JVM Generic", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Java_Application", @@ -1119,14 +1315,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275488, + "sync": 1646290176, "description": "## Overview\n\nThis is a modification of [official template for generic java applications, customized for G1 GC. (and includes better graphs)\n\n\n\n\n\n\n## Author\n\nTaha Jahangir", "template_file": "template_jvm_and_g1_gc_monitoring_with_jmx.xml", "name": "JVM Generic" }, { "version": 5.4, - "sync": 1646275488, + "sync": 1646290176, + "description": "## Overview\n\nThis is a modification of [official template for generic java applications, customized for G1 GC. (and includes better graphs)\n\n\n\n\n\n\n## Author\n\nTaha Jahangir\n", + "template_file": "template_jvm_and_g1_gc_monitoring_with_jmx.yaml", + "name": "JVM Generic" + }, + { + "version": 6.0, + "sync": 1646290177, "description": "## Overview\n\nThis is a modification of [official template for generic java applications, customized for G1 GC. (and includes better graphs)\n\n\n\n\n\n\n## Author\n\nTaha Jahangir\n", "template_file": "template_jvm_and_g1_gc_monitoring_with_jmx.yaml", "name": "JVM Generic" @@ -1144,13 +1347,13 @@ { "name": "Mail_servers", "type": "folder", - "sync": 1646275490, + "sync": 1646290180, "next": [ { "name": "template_cisco_esa_(_ironport_)_additional_monitoring", "template": "ESA-CISCO XML Status", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Mail_servers", @@ -1161,14 +1364,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275488, + "sync": 1646290177, "description": "## Overview\n\nTemplate allows to monitor your CISCO ESA ( IRONPORT ). number of active recipients, number of completed recipietns per minute, number of injected (recieved by esa) messages per minute, number of connections and so on. For now there is no triggers.\n\n\nInstallation:\n\n\n1. import the template,\n2. create read\\_only\\_operator user in your ESA,\n3. create and fill in value macros in zabbix ESA host: {$IRP\\_LOGIN} for login and {$IRP\\_PASS} for password (both created on step 2)\n4. link imported template to ESA host\n\n\nDefault update interval is 5 min. you can chage it in \"Get\\_Ironport\\_xml\\_status\" item.\n\n\nTempalate contains 28 items. \"HTTP agent\" item (Get\\_Ironport\\_xml\\_status) reads xml status page from ESA (https://{HOST.IP}/xml/status) and 27 dependet items, using preproceccing and XML Path to get items from XML:\n\n\n* 5xx\\_hard\\_bounced\\_recips\n* active\\_recips\n* completed\\_recips\n* completed\\_recips\\_last\\_1\\_min\n* conn\\_in\n* conn\\_out\n* deleted\\_recips\n* delivered\\_recips\n* delivered\\_recips\\_last\\_1\\_min\n* dns\\_hard\\_bounced\\_recips\n* dropped\\_msgs\n* expired\\_hard\\_bounced\\_recips\n* filter\\_hard\\_bounced\\_recips\n* gen\\_bounce\\_recips\n* global\\_unsub\\_hits\n* hard\\_bounced\\_recips\n* hard\\_bounced\\_recips\\_last\\_1\\_min\n* inj\\_msgs\n* inj\\_msgs\\_last\\_1\\_min\n* inj\\_recips\n* inj\\_recips\\_last\\_1\\_min\n* kbytes\\_in\\_policy\\_virus\\_outbreak\\_quarantine\n* msgs\\_in\\_policy\\_virus\\_outbreak\\_quarantine\n* other\\_hard\\_bounced\\_recips\n* rejected\\_recips\n* soft\\_bounced\\_evts\n* soft\\_bounced\\_evts\\_last\\_1\\_min\n\n\n## Author\n\nDK", "template_file": "template_cisco_esa_(_ironport_)_additional_monitoring.xml", "name": "ESA-CISCO XML Status" }, { "version": 5.4, - "sync": 1646275489, + "sync": 1646290177, + "description": "## Overview\n\nTemplate allows to monitor your CISCO ESA ( IRONPORT ). number of active recipients, number of completed recipietns per minute, number of injected (recieved by esa) messages per minute, number of connections and so on. For now there is no triggers.\n\n\nInstallation:\n\n\n1. import the template,\n2. create read\\_only\\_operator user in your ESA,\n3. create and fill in value macros in zabbix ESA host: {$IRP\\_LOGIN} for login and {$IRP\\_PASS} for password (both created on step 2)\n4. link imported template to ESA host\n\n\nDefault update interval is 5 min. you can chage it in \"Get\\_Ironport\\_xml\\_status\" item.\n\n\nTempalate contains 28 items. \"HTTP agent\" item (Get\\_Ironport\\_xml\\_status) reads xml status page from ESA (https://{HOST.IP}/xml/status) and 27 dependet items, using preproceccing and XML Path to get items from XML:\n\n\n* 5xx\\_hard\\_bounced\\_recips\n* active\\_recips\n* completed\\_recips\n* completed\\_recips\\_last\\_1\\_min\n* conn\\_in\n* conn\\_out\n* deleted\\_recips\n* delivered\\_recips\n* delivered\\_recips\\_last\\_1\\_min\n* dns\\_hard\\_bounced\\_recips\n* dropped\\_msgs\n* expired\\_hard\\_bounced\\_recips\n* filter\\_hard\\_bounced\\_recips\n* gen\\_bounce\\_recips\n* global\\_unsub\\_hits\n* hard\\_bounced\\_recips\n* hard\\_bounced\\_recips\\_last\\_1\\_min\n* inj\\_msgs\n* inj\\_msgs\\_last\\_1\\_min\n* inj\\_recips\n* inj\\_recips\\_last\\_1\\_min\n* kbytes\\_in\\_policy\\_virus\\_outbreak\\_quarantine\n* msgs\\_in\\_policy\\_virus\\_outbreak\\_quarantine\n* other\\_hard\\_bounced\\_recips\n* rejected\\_recips\n* soft\\_bounced\\_evts\n* soft\\_bounced\\_evts\\_last\\_1\\_min\n\n\n## Author\n\nDK\n", + "template_file": "template_cisco_esa_(_ironport_)_additional_monitoring.yaml", + "name": "ESA-CISCO XML Status" + }, + { + "version": 6.0, + "sync": 1646290177, "description": "## Overview\n\nTemplate allows to monitor your CISCO ESA ( IRONPORT ). number of active recipients, number of completed recipietns per minute, number of injected (recieved by esa) messages per minute, number of connections and so on. For now there is no triggers.\n\n\nInstallation:\n\n\n1. import the template,\n2. create read\\_only\\_operator user in your ESA,\n3. create and fill in value macros in zabbix ESA host: {$IRP\\_LOGIN} for login and {$IRP\\_PASS} for password (both created on step 2)\n4. link imported template to ESA host\n\n\nDefault update interval is 5 min. you can chage it in \"Get\\_Ironport\\_xml\\_status\" item.\n\n\nTempalate contains 28 items. \"HTTP agent\" item (Get\\_Ironport\\_xml\\_status) reads xml status page from ESA (https://{HOST.IP}/xml/status) and 27 dependet items, using preproceccing and XML Path to get items from XML:\n\n\n* 5xx\\_hard\\_bounced\\_recips\n* active\\_recips\n* completed\\_recips\n* completed\\_recips\\_last\\_1\\_min\n* conn\\_in\n* conn\\_out\n* deleted\\_recips\n* delivered\\_recips\n* delivered\\_recips\\_last\\_1\\_min\n* dns\\_hard\\_bounced\\_recips\n* dropped\\_msgs\n* expired\\_hard\\_bounced\\_recips\n* filter\\_hard\\_bounced\\_recips\n* gen\\_bounce\\_recips\n* global\\_unsub\\_hits\n* hard\\_bounced\\_recips\n* hard\\_bounced\\_recips\\_last\\_1\\_min\n* inj\\_msgs\n* inj\\_msgs\\_last\\_1\\_min\n* inj\\_recips\n* inj\\_recips\\_last\\_1\\_min\n* kbytes\\_in\\_policy\\_virus\\_outbreak\\_quarantine\n* msgs\\_in\\_policy\\_virus\\_outbreak\\_quarantine\n* other\\_hard\\_bounced\\_recips\n* rejected\\_recips\n* soft\\_bounced\\_evts\n* soft\\_bounced\\_evts\\_last\\_1\\_min\n\n\n## Author\n\nDK\n", "template_file": "template_cisco_esa_(_ironport_)_additional_monitoring.yaml", "name": "ESA-CISCO XML Status" @@ -1186,7 +1396,7 @@ "name": "template_exchange_2010_client_access_performance_monitoring_(rus)", "template": "Exchange Mailbox Servers_RU", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Mail_servers", @@ -1197,14 +1407,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275489, + "sync": 1646290177, "description": "## Overview\n\n \n\n## Author\n\nStephen E. Fritz", "template_file": "template_exchange_2010_client_access_performance_monitoring_(rus).xml", "name": "Exchange Mailbox Servers_RU" }, { "version": 5.4, - "sync": 1646275489, + "sync": 1646290177, + "description": "## Overview\n\n \n\n## Author\n\nStephen E. Fritz\n", + "template_file": "template_exchange_2010_client_access_performance_monitoring_(rus).yaml", + "name": "Exchange Mailbox Servers_RU" + }, + { + "version": 6.0, + "sync": 1646290177, "description": "## Overview\n\n \n\n## Author\n\nStephen E. Fritz\n", "template_file": "template_exchange_2010_client_access_performance_monitoring_(rus).yaml", "name": "Exchange Mailbox Servers_RU" @@ -1221,7 +1438,7 @@ "name": "template_exchange_2010_client_access_performance_monitoring_(rus)_1", "template": "Exchange Mailbox Servers_RU", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Mail_servers", @@ -1232,14 +1449,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275489, + "sync": 1646290177, "description": "## Overview\n\n39 Items, 5 Triggers 13 Graphs and 6 Screens built from Exchange 2010 Client Access Server Performance Counters for advanced troubleshooting, trending and capacity planning.\n\n\nИзменены названия Performance Couters для поддержки русской версии сервера Exchange\n\n\n\n## Author\n\nStephen E. Fritz", "template_file": "template_exchange_2010_client_access_performance_monitoring_(rus)_1.xml", "name": "Exchange Mailbox Servers_RU" }, { "version": 5.4, - "sync": 1646275489, + "sync": 1646290178, + "description": "## Overview\n\n39 Items, 5 Triggers 13 Graphs and 6 Screens built from Exchange 2010 Client Access Server Performance Counters for advanced troubleshooting, trending and capacity planning.\n\n\nИзменены названия Performance Couters для поддержки русской версии сервера Exchange\n\n\n\n## Author\n\nStephen E. Fritz\n", + "template_file": "template_exchange_2010_client_access_performance_monitoring_(rus)_1.yaml", + "name": "Exchange Mailbox Servers_RU" + }, + { + "version": 6.0, + "sync": 1646290178, "description": "## Overview\n\n39 Items, 5 Triggers 13 Graphs and 6 Screens built from Exchange 2010 Client Access Server Performance Counters for advanced troubleshooting, trending and capacity planning.\n\n\nИзменены названия Performance Couters для поддержки русской версии сервера Exchange\n\n\n\n## Author\n\nStephen E. Fritz\n", "template_file": "template_exchange_2010_client_access_performance_monitoring_(rus)_1.yaml", "name": "Exchange Mailbox Servers_RU" @@ -1252,7 +1476,7 @@ "name": "template_exchange_2016-services", "template": "Microsoft Exchange Server 2016 - Services", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Mail_servers", @@ -1263,14 +1487,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275489, + "sync": 1646290178, "description": "## Overview\n\n\n```\nThe \"Exchange 2016 - Services\" is mostly used to restart critical services by using \"ACTIONS\" and has discovery rules (Which Are Disabled by Default)\n\nThis template is based on using the {EVENT.TAGS} as a execute command within Actions.\n(Note: The whole Trigger will execute all alerts and do with them as you specify but independently execute based on 5m run-times)\nSo if there are three (3) services out, it may take fifteen (15) to twenty (20) mins to restart them.\n\n\nTo create an \"ACTION\" do the following.\n\nAdd \"All Services\" and tag them as (Trigger equals XXX)\n\nSee Example: Trigger equals Template Microsoft Exchange Server 2016 - Services: Service: MSExchangeUMCR on Template Microsoft Exchange Server 2016 - Services\n\nIf done correctly, you will have A~AE Trigger equals, about (31 Objects)\n\nOnce done, under \"Operations\" to Execute a command on the windows server use the following configuration.\n\nOperation Type: Remote Command (Note: Zabbix Agent must be set to \"Allow Remote Commands)\nTarget list: Current Host\nType: Custom Script\nExecute on: Zabbix Agent\nCommands: net start {EVENT.TAGS}\n\nYes, it a \"Vague\" tutorial (Sorry)\n```\n\n\n## Author\n\nRoute Packets", "template_file": "template_exchange_2016-services.xml", "name": "Microsoft Exchange Server 2016 - Services" }, { "version": 5.4, - "sync": 1646275489, + "sync": 1646290178, + "description": "## Overview\n\n\n```\nThe \"Exchange 2016 - Services\" is mostly used to restart critical services by using \"ACTIONS\" and has discovery rules (Which Are Disabled by Default)\n\nThis template is based on using the {EVENT.TAGS} as a execute command within Actions.\n(Note: The whole Trigger will execute all alerts and do with them as you specify but independently execute based on 5m run-times)\nSo if there are three (3) services out, it may take fifteen (15) to twenty (20) mins to restart them.\n\n\nTo create an \"ACTION\" do the following.\n\nAdd \"All Services\" and tag them as (Trigger equals XXX)\n\nSee Example: Trigger equals Template Microsoft Exchange Server 2016 - Services: Service: MSExchangeUMCR on Template Microsoft Exchange Server 2016 - Services\n\nIf done correctly, you will have A~AE Trigger equals, about (31 Objects)\n\nOnce done, under \"Operations\" to Execute a command on the windows server use the following configuration.\n\nOperation Type: Remote Command (Note: Zabbix Agent must be set to \"Allow Remote Commands)\nTarget list: Current Host\nType: Custom Script\nExecute on: Zabbix Agent\nCommands: net start {EVENT.TAGS}\n\nYes, it a \"Vague\" tutorial (Sorry)\n```\n\n\n## Author\n\nRoute Packets\n", + "template_file": "template_exchange_2016-services.yaml", + "name": "Microsoft Exchange Server 2016 - Services" + }, + { + "version": 6.0, + "sync": 1646290178, "description": "## Overview\n\n\n```\nThe \"Exchange 2016 - Services\" is mostly used to restart critical services by using \"ACTIONS\" and has discovery rules (Which Are Disabled by Default)\n\nThis template is based on using the {EVENT.TAGS} as a execute command within Actions.\n(Note: The whole Trigger will execute all alerts and do with them as you specify but independently execute based on 5m run-times)\nSo if there are three (3) services out, it may take fifteen (15) to twenty (20) mins to restart them.\n\n\nTo create an \"ACTION\" do the following.\n\nAdd \"All Services\" and tag them as (Trigger equals XXX)\n\nSee Example: Trigger equals Template Microsoft Exchange Server 2016 - Services: Service: MSExchangeUMCR on Template Microsoft Exchange Server 2016 - Services\n\nIf done correctly, you will have A~AE Trigger equals, about (31 Objects)\n\nOnce done, under \"Operations\" to Execute a command on the windows server use the following configuration.\n\nOperation Type: Remote Command (Note: Zabbix Agent must be set to \"Allow Remote Commands)\nTarget list: Current Host\nType: Custom Script\nExecute on: Zabbix Agent\nCommands: net start {EVENT.TAGS}\n\nYes, it a \"Vague\" tutorial (Sorry)\n```\n\n\n## Author\n\nRoute Packets\n", "template_file": "template_exchange_2016-services.yaml", "name": "Microsoft Exchange Server 2016 - Services" @@ -1287,7 +1518,7 @@ "name": "template_exchange_server_2016_performance_monitoring", "template": "Exchange 2016", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Mail_servers", @@ -1298,14 +1529,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275489, + "sync": 1646290178, "description": "## Overview\n\nConverted the Exchange 2010 Performance Monitoring Templates. Removed unsupported items and replaced them with equivalents that could be found. Added some new items and graphs.\n\n\n\n## Author\n\nmatt snead", "template_file": "template_exchange_server_2016_performance_monitoring.xml", "name": "Exchange 2016" }, { "version": 5.4, - "sync": 1646275489, + "sync": 1646290178, + "description": "## Overview\n\nConverted the Exchange 2010 Performance Monitoring Templates. Removed unsupported items and replaced them with equivalents that could be found. Added some new items and graphs.\n\n\n\n## Author\n\nmatt snead\n", + "template_file": "template_exchange_server_2016_performance_monitoring.yaml", + "name": "Exchange 2016" + }, + { + "version": 6.0, + "sync": 1646290179, "description": "## Overview\n\nConverted the Exchange 2010 Performance Monitoring Templates. Removed unsupported items and replaced them with equivalents that could be found. Added some new items and graphs.\n\n\n\n## Author\n\nmatt snead\n", "template_file": "template_exchange_server_2016_performance_monitoring.yaml", "name": "Exchange 2016" @@ -1322,7 +1560,7 @@ "name": "template_fortinet_fortimail", "template": "Fortimail 60D", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Mail_servers", @@ -1333,14 +1571,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275489, + "sync": 1646290179, "description": "## Author\n\nMikhail Norenberg", "template_file": "template_fortinet_fortimail.xml", "name": "Fortimail 60D" }, { "version": 5.4, - "sync": 1646275489, + "sync": 1646290179, + "description": "## Author\n\nMikhail Norenberg\n", + "template_file": "template_fortinet_fortimail.yaml", + "name": "Fortimail 60D" + }, + { + "version": 6.0, + "sync": 1646290179, "description": "## Author\n\nMikhail Norenberg\n", "template_file": "template_fortinet_fortimail.yaml", "name": "Fortimail 60D" @@ -1358,7 +1603,7 @@ "name": "template_mdaemon_fr", "template": "App MDaemon", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Mail_servers", @@ -1369,14 +1614,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275489, + "sync": 1646290179, "description": "## Overview\n\nHi, \n\n\n \n\n\nNew here, I updated the english version to french since mdaemon perf indicator are localized.", "template_file": "template_mdaemon_fr.xml", "name": "App MDaemon" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290179, + "description": "## Overview\n\nHi, \n\n\n \n\n\nNew here, I updated the english version to french since mdaemon perf indicator are localized.\n", + "template_file": "template_mdaemon_fr.yaml", + "name": "App MDaemon" + }, + { + "version": 6.0, + "sync": 1646290179, "description": "## Overview\n\nHi, \n\n\n \n\n\nNew here, I updated the english version to french since mdaemon perf indicator are localized.\n", "template_file": "template_mdaemon_fr.yaml", "name": "App MDaemon" @@ -1392,7 +1644,7 @@ "name": "template_mdaemon_rus", "template": "App MDaemon", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Mail_servers", @@ -1403,14 +1655,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290179, "description": "## Overview\n\nTemplate for Mdaemon russian version.", "template_file": "template_mdaemon_rus.xml", "name": "App MDaemon" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290179, + "description": "## Overview\n\nTemplate for Mdaemon russian version. \n", + "template_file": "template_mdaemon_rus.yaml", + "name": "App MDaemon" + }, + { + "version": 6.0, + "sync": 1646290179, "description": "## Overview\n\nTemplate for Mdaemon russian version. \n", "template_file": "template_mdaemon_rus.yaml", "name": "App MDaemon" @@ -1426,7 +1685,7 @@ "name": "template_monitor_axigen_with_zabbix", "template": "App Axigen-Services", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Mail_servers", @@ -1437,14 +1696,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290179, "description": "## Description\n\nAxigen template\n\n## Overview\n\nZabbix-Axigen\n=============\n\n\nMonitor Axigen With Zabbix\n\n\nUsage\n=====\n\n\nGo to your Axigen Web-Admin -> Status & Monitoring -> Reporting Service -Ensure your SNMP listner is enable\n\n\n* Scroll down to SNMP Parameters and enable snmp also Set SNMP community.\n* Use the Snmp community in template \"\" or you can also set your own Macro.\n* On the Axigen Web Admin Go to Services > Services Mangement > Scroll down and reload Reporting Service.\n\n\n Status & Monitoring -> Reporting Service -Ensure your SNMP listner is enable\n\n\n* Scroll down to SNMP Parameters and enable snmp also Set SNMP community.\n* Use the Snmp community in template \"\" or you can also set your own Macro.\n* On the Axigen Web Admin Go to Services > Services Mangement > Scroll down and reload Reporting Service.\n\n\n Status & Monitoring -> Reporting Service -Ensure your SNMP listner is enable\n\n\n* Scroll down to SNMP Parameters and enable snmp also Set SNMP community.\n* Use the Snmp community in template \"\" or you can also set your own Macro.\n* On the Axigen Web Admin Go to Services > Services Mangement > Scroll down and reload Reporting Service.\n\n\n /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.amavis.status,awk '/amavis/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.antispam.status,awk '/antispam/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.antivirus.status,awk '/antivirus/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.cbpolicyd.status,awk '/cbpolicyd/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.mailbox.status,awk '/mailbox/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.mta.status,awk '/mta/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.zmconfigd.status,awk '/zmconfigd/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.webmail.status,awk '/service webapp/{print $3}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.webadm.status,awk '/zimbraAdmin/{print $3}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.proxy.status,awk '/proxy/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.mailq.active,/opt/zimbra/libexec/zmqstat | grep active | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.corrupt,/opt/zimbra/libexec/zmqstat | grep corrupt | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.hold,/opt/zimbra/libexec/zmqstat | grep hold | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.deferred,/opt/zimbra/libexec/zmqstat | grep deferred | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.incoming,/opt/zimbra/libexec/zmqstat | grep incoming | cut -d= -f2\n\n\n\n## Author\n\nCarlos Eduardo", "template_file": "template_zimbra_collaboration.xml", "name": "Zimbra" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290179, + "description": "## Overview\n\nÉ necessário habilitar o Allow root e o comando externo.\n\n\nColeta status dos serviços, fila e spam.\n\n\nAdicionar ao Userparameter \n\n\n UserParameter=zimbra.mailq,/opt/zimbra/common/sbin/mailq | grep -v \"Mail queue is empty\" | grep -c '^[0-9A-Z]'\n\n\nUserParameter=zimbra.service.status,su - zimbra -c\"zmcontrol status\" > /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.amavis.status,awk '/amavis/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.antispam.status,awk '/antispam/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.antivirus.status,awk '/antivirus/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.cbpolicyd.status,awk '/cbpolicyd/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.mailbox.status,awk '/mailbox/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.mta.status,awk '/mta/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.zmconfigd.status,awk '/zmconfigd/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.webmail.status,awk '/service webapp/{print $3}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.webadm.status,awk '/zimbraAdmin/{print $3}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.proxy.status,awk '/proxy/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.mailq.active,/opt/zimbra/libexec/zmqstat | grep active | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.corrupt,/opt/zimbra/libexec/zmqstat | grep corrupt | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.hold,/opt/zimbra/libexec/zmqstat | grep hold | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.deferred,/opt/zimbra/libexec/zmqstat | grep deferred | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.incoming,/opt/zimbra/libexec/zmqstat | grep incoming | cut -d= -f2\n\n\n\n## Author\n\nCarlos Eduardo\n", + "template_file": "template_zimbra_collaboration.yaml", + "name": "Zimbra" + }, + { + "version": 6.0, + "sync": 1646290180, "description": "## Overview\n\nÉ necessário habilitar o Allow root e o comando externo.\n\n\nColeta status dos serviços, fila e spam.\n\n\nAdicionar ao Userparameter \n\n\n UserParameter=zimbra.mailq,/opt/zimbra/common/sbin/mailq | grep -v \"Mail queue is empty\" | grep -c '^[0-9A-Z]'\n\n\nUserParameter=zimbra.service.status,su - zimbra -c\"zmcontrol status\" > /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.amavis.status,awk '/amavis/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.antispam.status,awk '/antispam/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.antivirus.status,awk '/antivirus/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.cbpolicyd.status,awk '/cbpolicyd/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.mailbox.status,awk '/mailbox/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.mta.status,awk '/mta/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.zmconfigd.status,awk '/zmconfigd/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.webmail.status,awk '/service webapp/{print $3}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.webadm.status,awk '/zimbraAdmin/{print $3}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.proxy.status,awk '/proxy/{print $2}' /tmp/zimbrastatus.txt\n\n\nUserParameter=zimbra.mailq.active,/opt/zimbra/libexec/zmqstat | grep active | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.corrupt,/opt/zimbra/libexec/zmqstat | grep corrupt | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.hold,/opt/zimbra/libexec/zmqstat | grep hold | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.deferred,/opt/zimbra/libexec/zmqstat | grep deferred | cut -d= -f2\n\n\nUserParameter=zimbra.mailq.incoming,/opt/zimbra/libexec/zmqstat | grep incoming | cut -d= -f2\n\n\n\n## Author\n\nCarlos Eduardo\n", "template_file": "template_zimbra_collaboration.yaml", "name": "Zimbra" @@ -1495,7 +1768,7 @@ "name": "template_zimbra_zmcontrol_status", "template": "Zimbra", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Mail_servers", @@ -1506,14 +1779,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290180, "description": "## Overview\n\nWith this template you can monitor the status of some parameters of your Zimbra server, in particular some of the \"zmcontrol status\" output.\n\n\n1) prepare the Zimbra server, by adding the following line to the ROOT CRONTAB. This will put the output of the \"zmcontrol status\" on a file in /tmp. It will run every 3 min:\n\n\n*/3 * * * * sudo -u zimbra /opt/zimbra/bin/zmcontrol status > /tmp/zmcontrol\\_status\n\n\n2) add the following UserParameter to the zabbix\\_agentd.conf file, or the conf.d folder:\n\n\nUserParameter=zimbra.amavis.status,awk '/amavis/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.antispam.status,awk '/antispam/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.antivirus.status,awk '/antivirus/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.mailbox.status,awk '/mailbox/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.mta.status,awk '/mta/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.zmconfigd.status,awk '/zmconfigd/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.webmail.status,awk '/service webapp/{print $3}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.webadm.status,awk '/zimbraAdmin/{print $3}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.proxy.status,awk '/proxy/{print $2}' /tmp/zmcontrol\\_status\n\n\n \n\n\n\n## Author\n\nLeleKimi", "template_file": "template_zimbra_zmcontrol_status.xml", "name": "Zimbra" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290180, + "description": "## Overview\n\nWith this template you can monitor the status of some parameters of your Zimbra server, in particular some of the \"zmcontrol status\" output.\n\n\n1) prepare the Zimbra server, by adding the following line to the ROOT CRONTAB. This will put the output of the \"zmcontrol status\" on a file in /tmp. It will run every 3 min:\n\n\n*/3 * * * * sudo -u zimbra /opt/zimbra/bin/zmcontrol status > /tmp/zmcontrol\\_status\n\n\n2) add the following UserParameter to the zabbix\\_agentd.conf file, or the conf.d folder:\n\n\nUserParameter=zimbra.amavis.status,awk '/amavis/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.antispam.status,awk '/antispam/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.antivirus.status,awk '/antivirus/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.mailbox.status,awk '/mailbox/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.mta.status,awk '/mta/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.zmconfigd.status,awk '/zmconfigd/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.webmail.status,awk '/service webapp/{print $3}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.webadm.status,awk '/zimbraAdmin/{print $3}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.proxy.status,awk '/proxy/{print $2}' /tmp/zmcontrol\\_status\n\n\n \n\n\n\n## Author\n\nLeleKimi\n", + "template_file": "template_zimbra_zmcontrol_status.yaml", + "name": "Zimbra" + }, + { + "version": 6.0, + "sync": 1646290180, "description": "## Overview\n\nWith this template you can monitor the status of some parameters of your Zimbra server, in particular some of the \"zmcontrol status\" output.\n\n\n1) prepare the Zimbra server, by adding the following line to the ROOT CRONTAB. This will put the output of the \"zmcontrol status\" on a file in /tmp. It will run every 3 min:\n\n\n*/3 * * * * sudo -u zimbra /opt/zimbra/bin/zmcontrol status > /tmp/zmcontrol\\_status\n\n\n2) add the following UserParameter to the zabbix\\_agentd.conf file, or the conf.d folder:\n\n\nUserParameter=zimbra.amavis.status,awk '/amavis/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.antispam.status,awk '/antispam/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.antivirus.status,awk '/antivirus/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.mailbox.status,awk '/mailbox/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.mta.status,awk '/mta/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.zmconfigd.status,awk '/zmconfigd/{print $2}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.webmail.status,awk '/service webapp/{print $3}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.webadm.status,awk '/zimbraAdmin/{print $3}' /tmp/zmcontrol\\_status \nUserParameter=zimbra.proxy.status,awk '/proxy/{print $2}' /tmp/zmcontrol\\_status\n\n\n \n\n\n\n## Author\n\nLeleKimi\n", "template_file": "template_zimbra_zmcontrol_status.yaml", "name": "Zimbra" @@ -1531,13 +1811,13 @@ { "name": "Misc", "type": "folder", - "sync": 1646275490, + "sync": 1646290180, "next": [ { "name": "template_lync_2013_mediation_role", "template": "App Skype for business Mediation Role", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Misc", @@ -1548,14 +1828,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290180, "description": "## Description\n\nThis template assesses the status and overall health of services as well as the performance of the Mediation Microsoft Skype for Business Server 2015. Note: You need to set thresholds for these counters according to your environment. It is recommended to monitor these counters for some period of time to understand potential value ranges and then set the thresholds accordingly. This documentation is based on: https://technet.microsoft.com/en-us/library/gg398616.aspx.\n\n## Overview\n\nLync 2013 Mediation role template", "template_file": "template_lync_2013_mediation_role.xml", "name": "App Skype for business Mediation Role" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290180, + "description": "## Description\n\nThis template assesses the status and overall health of services as well as the performance of the Mediation Microsoft Skype for Business Server 2015. Note: You need to set thresholds for these counters according to your environment. It is recommended to monitor these counters for some period of time to understand potential value ranges and then set the thresholds accordingly. This documentation is based on: https://technet.microsoft.com/en-us/library/gg398616.aspx.\n\n## Overview\n\nLync 2013 Mediation role template\n", + "template_file": "template_lync_2013_mediation_role.yaml", + "name": "App Skype for business Mediation Role" + }, + { + "version": 6.0, + "sync": 1646290180, "description": "## Description\n\nThis template assesses the status and overall health of services as well as the performance of the Mediation Microsoft Skype for Business Server 2015. Note: You need to set thresholds for these counters according to your environment. It is recommended to monitor these counters for some period of time to understand potential value ranges and then set the thresholds accordingly. This documentation is based on: https://technet.microsoft.com/en-us/library/gg398616.aspx.\n\n## Overview\n\nLync 2013 Mediation role template\n", "template_file": "template_lync_2013_mediation_role.yaml", "name": "App Skype for business Mediation Role" @@ -1572,13 +1859,13 @@ { "name": "Monitoring_System", "type": "folder", - "sync": 1646275491, + "sync": 1646290181, "next": [ { "name": "template_bcmstat_for_raspberry_pi", "template": "App bcmstat", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Monitoring_System", @@ -1589,14 +1876,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290180, "description": "", "template_file": "template_bcmstat_for_raspberry_pi.xml", "name": "App bcmstat" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290180, + "description": "", + "template_file": "template_bcmstat_for_raspberry_pi.yaml", + "name": "App bcmstat" + }, + { + "version": 6.0, + "sync": 1646290180, "description": "", "template_file": "template_bcmstat_for_raspberry_pi.yaml", "name": "App bcmstat" @@ -1615,7 +1909,7 @@ "name": "template_get_nagiostats", "template": "App Nagios stats", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Monitoring_System", @@ -1626,14 +1920,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290180, "description": "## Overview\n\nget nagios's statistics with nagiostats\n\n\n（Nagios 3.x）\n\n\ninstall\n\n\n1. add zabbix user into nagios group to execute nagiostats.\n\n\n2. deploy the script and Userparameter.\n\n\n3. import the template.\n\n\nenjoy\n\n\n\n\n---\n\n\nUserParameter\n\n\nUserParameter=get.nagiostats,/etc/zabbix/scripts/get-nagiostats.sh\n\n\n\n\n---\n\n\nScript\n\n\n\n\n\n \n\n\n=20161126\n\n\nAdded Graphs and Screen in the template.\n\n\n\n## Author\n\nsewata", "template_file": "template_get_nagiostats.xml", "name": "App Nagios stats" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290180, + "description": "## Overview\n\nget nagios's statistics with nagiostats\n\n\n（Nagios 3.x）\n\n\ninstall\n\n\n1. add zabbix user into nagios group to execute nagiostats.\n\n\n2. deploy the script and Userparameter.\n\n\n3. import the template.\n\n\nenjoy\n\n\n\n\n---\n\n\nUserParameter\n\n\nUserParameter=get.nagiostats,/etc/zabbix/scripts/get-nagiostats.sh\n\n\n\n\n---\n\n\nScript\n\n\n\n\n\n \n\n\n=20161126\n\n\nAdded Graphs and Screen in the template.\n\n\n\n## Author\n\nsewata\n", + "template_file": "template_get_nagiostats.yaml", + "name": "App Nagios stats" + }, + { + "version": 6.0, + "sync": 1646290180, "description": "## Overview\n\nget nagios's statistics with nagiostats\n\n\n（Nagios 3.x）\n\n\ninstall\n\n\n1. add zabbix user into nagios group to execute nagiostats.\n\n\n2. deploy the script and Userparameter.\n\n\n3. import the template.\n\n\nenjoy\n\n\n\n\n---\n\n\nUserParameter\n\n\nUserParameter=get.nagiostats,/etc/zabbix/scripts/get-nagiostats.sh\n\n\n\n\n---\n\n\nScript\n\n\n\n\n\n \n\n\n=20161126\n\n\nAdded Graphs and Screen in the template.\n\n\n\n## Author\n\nsewata\n", "template_file": "template_get_nagiostats.yaml", "name": "App Nagios stats" @@ -1646,7 +1947,7 @@ "name": "template_graylog_node_monitoring_using_zabbix", "template": "graylog_nodes", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Monitoring_System", @@ -1657,14 +1958,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290180, "description": "## Overview\n\nTemplate created to monitor GrayLog nodes through LLD (Low Level Discovery)\n\n\nWe added a feature of Zabbix called LLD (Low Level Discovery) in the model, this automation seeks to facilitate the discovery of the nodes in GrayLog, so that you do not have to register the nodes manually just set the time of the discovery rule.\n\n\nMonitoring Itens:\n-----------------\n\n\n* GrayLog: Filter execution Time (FIltered, Incomming, Outgoing, Process)\n* GrayLog: Internal Log Message (Error, Fatal, Trace, Warn)\n* GrayLog: Journal ( Journal Size)\n* GrayLog: Node Memory(LLD)/( Free Memory, Max Memory, Total Memory, Used Memory)\n* GrayLog: Node Status (Lifecycle, Processing, Status )\n* GrayLog: Services\n\n\nRequirements\n------------\n\n\n* Zabbix 3.4;\n* Graylog 2.4;\n* Zabbix Agent install on Graylog;\n* Python 3.4 or > Python3;\n* Imports;\n\t+ import requests;\n\t+ import json;\n\t+ import sys\n\n\n## Author\n\nBeza", "template_file": "template_graylog_node_monitoring_using_zabbix.xml", "name": "graylog_nodes" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290180, + "description": "## Overview\n\nTemplate created to monitor GrayLog nodes through LLD (Low Level Discovery)\n\n\nWe added a feature of Zabbix called LLD (Low Level Discovery) in the model, this automation seeks to facilitate the discovery of the nodes in GrayLog, so that you do not have to register the nodes manually just set the time of the discovery rule.\n\n\nMonitoring Itens:\n-----------------\n\n\n* GrayLog: Filter execution Time (FIltered, Incomming, Outgoing, Process)\n* GrayLog: Internal Log Message (Error, Fatal, Trace, Warn)\n* GrayLog: Journal ( Journal Size)\n* GrayLog: Node Memory(LLD)/( Free Memory, Max Memory, Total Memory, Used Memory)\n* GrayLog: Node Status (Lifecycle, Processing, Status )\n* GrayLog: Services\n\n\nRequirements\n------------\n\n\n* Zabbix 3.4;\n* Graylog 2.4;\n* Zabbix Agent install on Graylog;\n* Python 3.4 or > Python3;\n* Imports;\n\t+ import requests;\n\t+ import json;\n\t+ import sys\n\n\n## Author\n\nBeza\n", + "template_file": "template_graylog_node_monitoring_using_zabbix.yaml", + "name": "graylog_nodes" + }, + { + "version": 6.0, + "sync": 1646290181, "description": "## Overview\n\nTemplate created to monitor GrayLog nodes through LLD (Low Level Discovery)\n\n\nWe added a feature of Zabbix called LLD (Low Level Discovery) in the model, this automation seeks to facilitate the discovery of the nodes in GrayLog, so that you do not have to register the nodes manually just set the time of the discovery rule.\n\n\nMonitoring Itens:\n-----------------\n\n\n* GrayLog: Filter execution Time (FIltered, Incomming, Outgoing, Process)\n* GrayLog: Internal Log Message (Error, Fatal, Trace, Warn)\n* GrayLog: Journal ( Journal Size)\n* GrayLog: Node Memory(LLD)/( Free Memory, Max Memory, Total Memory, Used Memory)\n* GrayLog: Node Status (Lifecycle, Processing, Status )\n* GrayLog: Services\n\n\nRequirements\n------------\n\n\n* Zabbix 3.4;\n* Graylog 2.4;\n* Zabbix Agent install on Graylog;\n* Python 3.4 or > Python3;\n* Imports;\n\t+ import requests;\n\t+ import json;\n\t+ import sys\n\n\n## Author\n\nBeza\n", "template_file": "template_graylog_node_monitoring_using_zabbix.yaml", "name": "graylog_nodes" @@ -1680,7 +1988,7 @@ "name": "template_junos_space", "template": "Junos Space", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Monitoring_System", @@ -1691,14 +1999,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290181, "description": "## Overview\n\nmonitor critical services for Junos Space monitoring system\n\n\n\n## Author\n\nDmitry Lavrukhin", "template_file": "template_junos_space.xml", "name": "Junos Space" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290181, + "description": "## Overview\n\nmonitor critical services for Junos Space monitoring system\n\n\n\n## Author\n\nDmitry Lavrukhin\n", + "template_file": "template_junos_space.yaml", + "name": "Junos Space" + }, + { + "version": 6.0, + "sync": 1646290181, "description": "## Overview\n\nmonitor critical services for Junos Space monitoring system\n\n\n\n## Author\n\nDmitry Lavrukhin\n", "template_file": "template_junos_space.yaml", "name": "Junos Space" @@ -1715,7 +2030,7 @@ "name": "template_ozeki_sms_gateway", "template": "8 Ozeki", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Monitoring_System", @@ -1726,14 +2041,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290181, "description": "## Overview\n\nOzeki SMS Gateway\n\n\nTemplate provide server information, connection status, users and queue sizes, trigger for disconnection and filling queues and display queue sizes in graph.\n\n\nTested on zabbix 3.4", "template_file": "template_ozeki_sms_gateway.xml", "name": "8 Ozeki" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290181, + "description": "## Overview\n\nOzeki SMS Gateway\n\n\nTemplate provide server information, connection status, users and queue sizes, trigger for disconnection and filling queues and display queue sizes in graph.\n\n\nTested on zabbix 3.4\n", + "template_file": "template_ozeki_sms_gateway.yaml", + "name": "8 Ozeki" + }, + { + "version": 6.0, + "sync": 1646290181, "description": "## Overview\n\nOzeki SMS Gateway\n\n\nTemplate provide server information, connection status, users and queue sizes, trigger for disconnection and filling queues and display queue sizes in graph.\n\n\nTested on zabbix 3.4\n", "template_file": "template_ozeki_sms_gateway.yaml", "name": "8 Ozeki" @@ -1749,7 +2071,7 @@ "name": "template_proximvision_nms", "template": "ProximVision NMS", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Monitoring_System", @@ -1760,14 +2082,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290181, "description": "## Overview\n\nMonitor critical services for ProximWireless Proximvision NMS\n\n\n\n## Author\n\nDmitry Lavrukhin", "template_file": "template_proximvision_nms.xml", "name": "ProximVision NMS" }, { "version": 5.4, - "sync": 1646275490, + "sync": 1646290181, + "description": "## Overview\n\nMonitor critical services for ProximWireless Proximvision NMS\n\n\n\n## Author\n\nDmitry Lavrukhin\n", + "template_file": "template_proximvision_nms.yaml", + "name": "ProximVision NMS" + }, + { + "version": 6.0, + "sync": 1646290181, "description": "## Overview\n\nMonitor critical services for ProximWireless Proximvision NMS\n\n\n\n## Author\n\nDmitry Lavrukhin\n", "template_file": "template_proximvision_nms.yaml", "name": "ProximVision NMS" @@ -1783,7 +2112,7 @@ "name": "template_zabbix_monitor_housekeeper", "template": "Housekeeping Metrics", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Monitoring_System", @@ -1794,14 +2123,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275490, + "sync": 1646290181, "description": "## Description\n\nLanguage: English Autor: Bernardo Lankheet Blog: www.bernardolankheet.com.br Repositorio: https://github.com/bernardolankheet/Zabbix-Monitor-Housekeeper\n\n## Overview\n\nProject Name: Zabbix-Monitor-Housekeeper\nAuthor: Bernardo Lankheet\nTelegram: [@bernardolankheet](https://t.me/bernardolankheet)\nDescription BR: Coleta de métricas sobre a execução do Housekeeper. *Não se aplica em ambientes que utiliza particionamento de tabelas ou outras rotinas para manutenção do banco de dados.*\nDescription EN: Collect Metrics on Housekeeper Execution. *It does not apply in environments that use table partitioning or other routines for maintaining the bank.*\nOBS EN: Based on projet Diego Cavalcante [ZAKEEP.zabbix.housekeeper.monitor](https://github.com/suportecavalcante/zabbix.templates/tree/master/linux/ZAKEEP.zabbix.housekeeper.monitor)\nOBS BR: Ideia retirada do projeto do Diego Cavalcante [ZAKEEP.zabbix.housekeeper.monitor](https://github.com/suportecavalcante/zabbix.templates/tree/master/linux/ZAKEEP.zabbix.housekeeper.monitor) \n \n#### **## Usage**\n\n\nEN: Import your Template into Zabbix, link to the Host \"Zabbix server\" and wait for the items to be collected, collection is carried out according to the housekeeping schedule. Image 03 \n\n\nBR: Importe seu Template para o Zabbix, vincula o template ao Host \"Zabbix server\" e aguarde os itens serem coletados, a coleta é realizada conforme a programação do housekeeping. Imagem 03 \n\n\n#### **## How it works?**\n\n\nEN: Whenever housekeeping is performed by zabbix-server, a line is generated containing the information deleted from zabbix\\_server.log. The item Syslog Housekeeping, of the log type, captures the information via active checking and the other dependent items are pre-filled according to parent item information. \n\n\nBR: Sempre que a manutenção é realizada pelo zabbix-server, uma linha é gerada contendo as informações excluídas do zabbix\\_server.log. O item Syslog Housekeeping, do tipo log, captura as informações por meio de verificação ativa e os demais itens dependentes são pré-preenchidos de acordo com as informações do item pai. \n\n\n#### **## Macros**\n\n\n* {$ PATHLOG} - /var/log/zabbix/zabbix\\_server.log - Path to zabbix\\_server.log\\\n* {$ REGEXLOG} -. * Deleted. * [0-9] + hist \\ /trends.* - Regex to capture the line for housekepping inside the log\n\n\n#### **## Homolog**\n\n\n* Zabbix 4.4\n* Zabbix 5.0.6\n\n\n#### **## Templates**\n\n\n* Template Housekeeping Metrics-EN-US - English version (on github)\n* Template Housekeeping Metricas - PT-BR (no github)\n\n\n## Author\n\nBernardo Lankheet", "template_file": "template_zabbix_monitor_housekeeper.xml", "name": "Housekeeping Metrics" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290181, + "description": "## Description\n\nLanguage: English Autor: Bernardo Lankheet Blog: www.bernardolankheet.com.br Repositorio: https://github.com/bernardolankheet/Zabbix-Monitor-Housekeeper\n\n## Overview\n\nProject Name: Zabbix-Monitor-Housekeeper\nAuthor: Bernardo Lankheet\nTelegram: [@bernardolankheet](https://t.me/bernardolankheet)\nDescription BR: Coleta de métricas sobre a execução do Housekeeper. *Não se aplica em ambientes que utiliza particionamento de tabelas ou outras rotinas para manutenção do banco de dados.*\nDescription EN: Collect Metrics on Housekeeper Execution. *It does not apply in environments that use table partitioning or other routines for maintaining the bank.*\nOBS EN: Based on projet Diego Cavalcante [ZAKEEP.zabbix.housekeeper.monitor](https://github.com/suportecavalcante/zabbix.templates/tree/master/linux/ZAKEEP.zabbix.housekeeper.monitor)\nOBS BR: Ideia retirada do projeto do Diego Cavalcante [ZAKEEP.zabbix.housekeeper.monitor](https://github.com/suportecavalcante/zabbix.templates/tree/master/linux/ZAKEEP.zabbix.housekeeper.monitor) \n \n#### **## Usage**\n\n\nEN: Import your Template into Zabbix, link to the Host \"Zabbix server\" and wait for the items to be collected, collection is carried out according to the housekeeping schedule. Image 03 \n\n\nBR: Importe seu Template para o Zabbix, vincula o template ao Host \"Zabbix server\" e aguarde os itens serem coletados, a coleta é realizada conforme a programação do housekeeping. Imagem 03 \n\n\n#### **## How it works?**\n\n\nEN: Whenever housekeeping is performed by zabbix-server, a line is generated containing the information deleted from zabbix\\_server.log. The item Syslog Housekeeping, of the log type, captures the information via active checking and the other dependent items are pre-filled according to parent item information. \n\n\nBR: Sempre que a manutenção é realizada pelo zabbix-server, uma linha é gerada contendo as informações excluídas do zabbix\\_server.log. O item Syslog Housekeeping, do tipo log, captura as informações por meio de verificação ativa e os demais itens dependentes são pré-preenchidos de acordo com as informações do item pai. \n\n\n#### **## Macros**\n\n\n* {$ PATHLOG} - /var/log/zabbix/zabbix\\_server.log - Path to zabbix\\_server.log\\\n* {$ REGEXLOG} -. * Deleted. * [0-9] + hist \\ /trends.* - Regex to capture the line for housekepping inside the log\n\n\n#### **## Homolog**\n\n\n* Zabbix 4.4\n* Zabbix 5.0.6\n\n\n#### **## Templates**\n\n\n* Template Housekeeping Metrics-EN-US - English version (on github)\n* Template Housekeeping Metricas - PT-BR (no github)\n\n\n## Author\n\nBernardo Lankheet\n", + "template_file": "template_zabbix_monitor_housekeeper.yaml", + "name": "Housekeeping Metrics" + }, + { + "version": 6.0, + "sync": 1646290181, "description": "## Description\n\nLanguage: English Autor: Bernardo Lankheet Blog: www.bernardolankheet.com.br Repositorio: https://github.com/bernardolankheet/Zabbix-Monitor-Housekeeper\n\n## Overview\n\nProject Name: Zabbix-Monitor-Housekeeper\nAuthor: Bernardo Lankheet\nTelegram: [@bernardolankheet](https://t.me/bernardolankheet)\nDescription BR: Coleta de métricas sobre a execução do Housekeeper. *Não se aplica em ambientes que utiliza particionamento de tabelas ou outras rotinas para manutenção do banco de dados.*\nDescription EN: Collect Metrics on Housekeeper Execution. *It does not apply in environments that use table partitioning or other routines for maintaining the bank.*\nOBS EN: Based on projet Diego Cavalcante [ZAKEEP.zabbix.housekeeper.monitor](https://github.com/suportecavalcante/zabbix.templates/tree/master/linux/ZAKEEP.zabbix.housekeeper.monitor)\nOBS BR: Ideia retirada do projeto do Diego Cavalcante [ZAKEEP.zabbix.housekeeper.monitor](https://github.com/suportecavalcante/zabbix.templates/tree/master/linux/ZAKEEP.zabbix.housekeeper.monitor) \n \n#### **## Usage**\n\n\nEN: Import your Template into Zabbix, link to the Host \"Zabbix server\" and wait for the items to be collected, collection is carried out according to the housekeeping schedule. Image 03 \n\n\nBR: Importe seu Template para o Zabbix, vincula o template ao Host \"Zabbix server\" e aguarde os itens serem coletados, a coleta é realizada conforme a programação do housekeeping. Imagem 03 \n\n\n#### **## How it works?**\n\n\nEN: Whenever housekeeping is performed by zabbix-server, a line is generated containing the information deleted from zabbix\\_server.log. The item Syslog Housekeeping, of the log type, captures the information via active checking and the other dependent items are pre-filled according to parent item information. \n\n\nBR: Sempre que a manutenção é realizada pelo zabbix-server, uma linha é gerada contendo as informações excluídas do zabbix\\_server.log. O item Syslog Housekeeping, do tipo log, captura as informações por meio de verificação ativa e os demais itens dependentes são pré-preenchidos de acordo com as informações do item pai. \n\n\n#### **## Macros**\n\n\n* {$ PATHLOG} - /var/log/zabbix/zabbix\\_server.log - Path to zabbix\\_server.log\\\n* {$ REGEXLOG} -. * Deleted. * [0-9] + hist \\ /trends.* - Regex to capture the line for housekepping inside the log\n\n\n#### **## Homolog**\n\n\n* Zabbix 4.4\n* Zabbix 5.0.6\n\n\n#### **## Templates**\n\n\n* Template Housekeeping Metrics-EN-US - English version (on github)\n* Template Housekeeping Metricas - PT-BR (no github)\n\n\n## Author\n\nBernardo Lankheet\n", "template_file": "template_zabbix_monitor_housekeeper.yaml", "name": "Housekeeping Metrics" @@ -1815,13 +2151,13 @@ { "name": "NTP", "type": "folder", - "sync": 1646275491, + "sync": 1646290182, "next": [ { "name": "template_chrony_accuracy", "template": "App Chrony Service", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "NTP", @@ -1832,14 +2168,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290181, "description": "## Overview\n\nThis template will parse the various types of data from the acquisition result of chronyc tracking command. \nThis allows you to detect the change of the time of displacement and Stratum by chrony.", "template_file": "template_chrony_accuracy.xml", "name": "App Chrony Service" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290181, + "description": "## Overview\n\nThis template will parse the various types of data from the acquisition result of chronyc tracking command. \nThis allows you to detect the change of the time of displacement and Stratum by chrony.\n", + "template_file": "template_chrony_accuracy.yaml", + "name": "App Chrony Service" + }, + { + "version": 6.0, + "sync": 1646290181, "description": "## Overview\n\nThis template will parse the various types of data from the acquisition result of chronyc tracking command. \nThis allows you to detect the change of the time of displacement and Stratum by chrony.\n", "template_file": "template_chrony_accuracy.yaml", "name": "App Chrony Service" @@ -1855,7 +2198,7 @@ "name": "template_chrony_accuracy_1", "template": "chrony_Monitoring", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "NTP", @@ -1866,14 +2209,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290181, "description": "## Overview\n\nchrony accuracy Infomation Template\n\n\nJapanese version template is in the . \n日本語版テンプレートは\n\n\nSammeln Sie alle Informationen, die in der chronyc Befehl angezeigt wird.\n\n\nWhen you use a template \nPlease make the following settings zabbix\\_agentd.conf.\n\n\nEnableRemoteCommands=1\n\n\nUnsafeUserParameters=1\n\n\n \n \n\nIn ZabbixAgent is installed environment \nIt will use the chrony template.", "template_file": "template_chrony_accuracy_1.xml", "name": "chrony_Monitoring" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290181, + "description": "## Overview\n\nchrony accuracy Infomation Template\n\n\nJapanese version template is in the . \n日本語版テンプレートは\n\n\nSammeln Sie alle Informationen, die in der chronyc Befehl angezeigt wird.\n\n\nWhen you use a template \nPlease make the following settings zabbix\\_agentd.conf.\n\n\nEnableRemoteCommands=1\n\n\nUnsafeUserParameters=1\n\n\n \n \n\nIn ZabbixAgent is installed environment \nIt will use the chrony template. \n", + "template_file": "template_chrony_accuracy_1.yaml", + "name": "chrony_Monitoring" + }, + { + "version": 6.0, + "sync": 1646290181, "description": "## Overview\n\nchrony accuracy Infomation Template\n\n\nJapanese version template is in the . \n日本語版テンプレートは\n\n\nSammeln Sie alle Informationen, die in der chronyc Befehl angezeigt wird.\n\n\nWhen you use a template \nPlease make the following settings zabbix\\_agentd.conf.\n\n\nEnableRemoteCommands=1\n\n\nUnsafeUserParameters=1\n\n\n \n \n\nIn ZabbixAgent is installed environment \nIt will use the chrony template. \n", "template_file": "template_chrony_accuracy_1.yaml", "name": "chrony_Monitoring" @@ -1886,7 +2236,7 @@ "name": "template_chrony_accuracy_english", "template": "chrony_Monitoring", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "NTP", @@ -1897,14 +2247,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290181, "description": "## Overview\n\nchrony accuracy Infomation Template\n\n\nJapanese version template is in the [link](cat-app/ntp/chrony-accuracy-template-japanese). \n日本語版テンプレートは[こちら](cat-app/ntp/chrony-accuracy-template-japanese)\n\n\nSammeln Sie alle Informationen, die in der chronyc Befehl angezeigt wird.\n\n\nWhen you use a template \nPlease make the following settings zabbix\\_agentd.conf.\n\n\nEnableRemoteCommands=1\n\n\nUnsafeUserParameters=1\n\n\n \n \n\nIn ZabbixAgent is installed environment \nIt will use the chrony template.", "template_file": "template_chrony_accuracy_english.xml", "name": "chrony_Monitoring" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290181, + "description": "## Overview\n\nchrony accuracy Infomation Template\n\n\nJapanese version template is in the [link](cat-app/ntp/chrony-accuracy-template-japanese). \n日本語版テンプレートは[こちら](cat-app/ntp/chrony-accuracy-template-japanese)\n\n\nSammeln Sie alle Informationen, die in der chronyc Befehl angezeigt wird.\n\n\nWhen you use a template \nPlease make the following settings zabbix\\_agentd.conf.\n\n\nEnableRemoteCommands=1\n\n\nUnsafeUserParameters=1\n\n\n \n \n\nIn ZabbixAgent is installed environment \nIt will use the chrony template. \n \n", + "template_file": "template_chrony_accuracy_english.yaml", + "name": "chrony_Monitoring" + }, + { + "version": 6.0, + "sync": 1646290181, "description": "## Overview\n\nchrony accuracy Infomation Template\n\n\nJapanese version template is in the [link](cat-app/ntp/chrony-accuracy-template-japanese). \n日本語版テンプレートは[こちら](cat-app/ntp/chrony-accuracy-template-japanese)\n\n\nSammeln Sie alle Informationen, die in der chronyc Befehl angezeigt wird.\n\n\nWhen you use a template \nPlease make the following settings zabbix\\_agentd.conf.\n\n\nEnableRemoteCommands=1\n\n\nUnsafeUserParameters=1\n\n\n \n \n\nIn ZabbixAgent is installed environment \nIt will use the chrony template. \n \n", "template_file": "template_chrony_accuracy_english.yaml", "name": "chrony_Monitoring" @@ -1920,7 +2277,7 @@ "name": "template_chrony_accuracy_japanese", "template": "chrony_Monitoring-Japanese", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "NTP", @@ -1931,18 +2288,25 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290181, "description": "## Overview\n\nchrony accuracy Template Englishの日本語版です \n英語版は[こちら](cat-app/ntp/chrony-accuracy-template-english)\n\n\nEnglish version of the template is in the [link](cat-app/ntp/chrony-accuracy-template-english) .\n\n\n \n\n\nテンプレートを利用する場合zabbix\\_agentd.confでリモートコマンドを有効にしてください。\n\n\nEnableRemoteCommands=1 \nUnsafeUserParameters=1\n\n\nZabbixAgentがインストールされた環境に対しては \nchrony テンプレートが使用できます。", "template_file": "template_chrony_accuracy_japanese.xml", "name": "chrony_Monitoring-Japanese" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290181, "description": "## Overview\n\nchrony accuracy Template Englishの日本語版です \n英語版は[こちら](cat-app/ntp/chrony-accuracy-template-english)\n\n\nEnglish version of the template is in the [link](cat-app/ntp/chrony-accuracy-template-english) .\n\n\n \n\n\nテンプレートを利用する場合zabbix\\_agentd.confでリモートコマンドを有効にしてください。\n\n\nEnableRemoteCommands=1 \nUnsafeUserParameters=1\n\n\nZabbixAgentがインストールされた環境に対しては \nchrony テンプレートが使用できます。\n\n\n \n\n\n \n", "template_file": "template_chrony_accuracy_japanese.yaml", "name": "chrony_Monitoring-Japanese" - } + }, + { + "version": 6.0, + "sync": 1646290181, + "description": "## Overview\n\nchrony accuracy Template Englishの日本語版です \n英語版は[こちら](cat-app/ntp/chrony-accuracy-template-english)\n\n\nEnglish version of the template is in the [link](cat-app/ntp/chrony-accuracy-template-english) .\n\n\n \n\n\nテンプレートを利用する場合zabbix\\_agentd.confでリモートコマンドを有効にしてください。\n\n\nEnableRemoteCommands=1 \nUnsafeUserParameters=1\n\n\nZabbixAgentがインストールされた環境に対しては \nchrony テンプレートが使用できます。\n\n\n \n\n\n \n", + "template_file": "template_chrony_accuracy_japanese.yaml", + "name": "chrony_Monitoring-Japanese" + } ], "tags": [ "category:services", @@ -1954,7 +2318,7 @@ "name": "template_ntp_accuracy", "template": "NTP-remote", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "NTP", @@ -1965,14 +2329,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290181, "description": "", "template_file": "template_ntp_accuracy.xml", "name": "NTP-remote" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290181, + "description": "", + "template_file": "template_ntp_accuracy.yaml", + "name": "NTP-remote" + }, + { + "version": 6.0, + "sync": 1646290181, "description": "", "template_file": "template_ntp_accuracy.yaml", "name": "NTP-remote" @@ -1988,7 +2359,7 @@ "name": "template_ntp_accuracy_japanese", "template": "NTP-remote-Japanese", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "NTP", @@ -1999,14 +2370,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290181, "description": "", "template_file": "template_ntp_accuracy_japanese.xml", "name": "NTP-remote-Japanese" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290181, + "description": "## Overview\n\nNTP accuracy Template の日本語版です \n英語版は[こちら](cat-app/ntp-accuracy-template)English version of the template is in the [link](cat-app/ntp-accuracy-template) .\n\n\n \n\n\nテンプレートを利用する場合zabbix\\_agentd.confでリモートコマンドを有効にしてください。\n\n\nEnableRemoteCommands=1 \nUnsafeUserParameters=1\n\n\nZabbixAgentがインストールされた環境に対しては \nNTPテンプレートが使用できます。\n\n\nNTPアプライアンスなどZabbixAgentが使用できない環境のNTPサーバに対しては \nNTPテンプレート（リモート）が使用できます。\n\n\nNTPテンプレート（リモート）を利用する場合はホストマクロにおいて \n{$NTP\\_IP}に監視対象のIPアドレスを指定してください。\n\n\nntpqによって表示されるすべての項目が監視できます。\n\n\nNTP精度情報をグラフ化することが可能です。\n\n\n \n", + "template_file": "template_ntp_accuracy_japanese.yaml", + "name": "NTP-remote-Japanese" + }, + { + "version": 6.0, + "sync": 1646290182, "description": "## Overview\n\nNTP accuracy Template の日本語版です \n英語版は[こちら](cat-app/ntp-accuracy-template)English version of the template is in the [link](cat-app/ntp-accuracy-template) .\n\n\n \n\n\nテンプレートを利用する場合zabbix\\_agentd.confでリモートコマンドを有効にしてください。\n\n\nEnableRemoteCommands=1 \nUnsafeUserParameters=1\n\n\nZabbixAgentがインストールされた環境に対しては \nNTPテンプレートが使用できます。\n\n\nNTPアプライアンスなどZabbixAgentが使用できない環境のNTPサーバに対しては \nNTPテンプレート（リモート）が使用できます。\n\n\nNTPテンプレート（リモート）を利用する場合はホストマクロにおいて \n{$NTP\\_IP}に監視対象のIPアドレスを指定してください。\n\n\nntpqによって表示されるすべての項目が監視できます。\n\n\nNTP精度情報をグラフ化することが可能です。\n\n\n \n", "template_file": "template_ntp_accuracy_japanese.yaml", "name": "NTP-remote-Japanese" @@ -2023,13 +2401,13 @@ { "name": "Others", "type": "folder", - "sync": 1646275491, + "sync": 1646290183, "next": [ { "name": "template_e2guardian_4.1.x", "template": "App e2guardian - Active", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Others", @@ -2040,14 +2418,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290182, "description": "## Description\n\nhttps://github.com/e2guardian/e2guardian/blob/master/notes/dstats_format USER.MACRO={$E2GUARDIAN_DSTATS} UserParameter=e2guardian[*],tail -1 $1 | cut -f $2\n\n## Overview\n\nIntroduction\n============\n\n\nThis is my approach for a performance monitoring Template of [E2guardian](http://e2guardian.org/).\n\n\nThis Template was created on and for Zabbix 3.4 and E2Guardian 4.1.x on Debian 9 Stretch.\n\n\nInstallation\n------------\n\n\nPlease check the GitHub Page for latest version and instructions. \n\n\nChanges\n-------\n\n\n \n\n\n* February 2018: initial commit.\n* 03 April 2018: Switch to Zabbix agent (active) & converted s\n\n\n## Author\n\nMarco Hofmann", "template_file": "template_e2guardian_4.1.x.xml", "name": "App e2guardian - Active" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290182, + "description": "## Description\n\nhttps://github.com/e2guardian/e2guardian/blob/master/notes/dstats_format USER.MACRO={$E2GUARDIAN_DSTATS} UserParameter=e2guardian[*],tail -1 $1 | cut -f $2\n\n## Overview\n\nIntroduction\n============\n\n\nThis is my approach for a performance monitoring Template of [E2guardian](http://e2guardian.org/).\n\n\nThis Template was created on and for Zabbix 3.4 and E2Guardian 4.1.x on Debian 9 Stretch.\n\n\nInstallation\n------------\n\n\nPlease check the GitHub Page for latest version and instructions. \n\n\nChanges\n-------\n\n\n \n\n\n* February 2018: initial commit.\n* 03 April 2018: Switch to Zabbix agent (active) & converted s\n\n\n## Author\n\nMarco Hofmann\n", + "template_file": "template_e2guardian_4.1.x.yaml", + "name": "App e2guardian - Active" + }, + { + "version": 6.0, + "sync": 1646290182, "description": "## Description\n\nhttps://github.com/e2guardian/e2guardian/blob/master/notes/dstats_format USER.MACRO={$E2GUARDIAN_DSTATS} UserParameter=e2guardian[*],tail -1 $1 | cut -f $2\n\n## Overview\n\nIntroduction\n============\n\n\nThis is my approach for a performance monitoring Template of [E2guardian](http://e2guardian.org/).\n\n\nThis Template was created on and for Zabbix 3.4 and E2Guardian 4.1.x on Debian 9 Stretch.\n\n\nInstallation\n------------\n\n\nPlease check the GitHub Page for latest version and instructions. \n\n\nChanges\n-------\n\n\n \n\n\n* February 2018: initial commit.\n* 03 April 2018: Switch to Zabbix agent (active) & converted s\n\n\n## Author\n\nMarco Hofmann\n", "template_file": "template_e2guardian_4.1.x.yaml", "name": "App e2guardian - Active" @@ -2064,7 +2449,7 @@ "name": "template_haproxy_v2_stats_via_prometheus", "template": "_T_Zbx_Lin_HAPROXY2_stats_Prometheus", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Others", @@ -2075,14 +2460,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290182, "description": "## Description\n\nfrontend stats bind *:8880 http-request use-service prometheus-exporter if { path /metrics } stats enable stats uri /stats stats refresh 10s\n\n## Overview\n\nPermit getting stats via prometheus exporter (since haproxy 2.0)\n\n\nFirst, configure your haproxy to expose frontend stats page like this :\n\n\nfrontend stats \n bind *:8880 \n http-request use-service prometheus-exporter if { path /metrics } \n stats enable \n stats uri /stats \n stats refresh 10s\n\n\nThen, check the item haproxy.prometheus.allmetrics URL.\n\n\nDiscovery for frontends, backends, servers.\n\n\n* Check if <50% of backend are down (not up, like DRAIN, NOLB, etc )on a frontend.\n* Check if connections are >90/95% of the limit on frontend\n* Check status of frontend and backend.", "template_file": "template_haproxy_v2_stats_via_prometheus.xml", "name": "_T_Zbx_Lin_HAPROXY2_stats_Prometheus" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290182, + "description": "## Description\n\nfrontend stats bind *:8880 http-request use-service prometheus-exporter if { path /metrics } stats enable stats uri /stats stats refresh 10s\n\n## Overview\n\nPermit getting stats via prometheus exporter (since haproxy 2.0)\n\n\nFirst, configure your haproxy to expose frontend stats page like this :\n\n\nfrontend stats \n bind *:8880 \n http-request use-service prometheus-exporter if { path /metrics } \n stats enable \n stats uri /stats \n stats refresh 10s\n\n\nThen, check the item haproxy.prometheus.allmetrics URL.\n\n\nDiscovery for frontends, backends, servers.\n\n\n* Check if <50% of backend are down (not up, like DRAIN, NOLB, etc )on a frontend.\n* Check if connections are >90/95% of the limit on frontend\n* Check status of frontend and backend.\n", + "template_file": "template_haproxy_v2_stats_via_prometheus.yaml", + "name": "_T_Zbx_Lin_HAPROXY2_stats_Prometheus" + }, + { + "version": 6.0, + "sync": 1646290182, "description": "## Description\n\nfrontend stats bind *:8880 http-request use-service prometheus-exporter if { path /metrics } stats enable stats uri /stats stats refresh 10s\n\n## Overview\n\nPermit getting stats via prometheus exporter (since haproxy 2.0)\n\n\nFirst, configure your haproxy to expose frontend stats page like this :\n\n\nfrontend stats \n bind *:8880 \n http-request use-service prometheus-exporter if { path /metrics } \n stats enable \n stats uri /stats \n stats refresh 10s\n\n\nThen, check the item haproxy.prometheus.allmetrics URL.\n\n\nDiscovery for frontends, backends, servers.\n\n\n* Check if <50% of backend are down (not up, like DRAIN, NOLB, etc )on a frontend.\n* Check if connections are >90/95% of the limit on frontend\n* Check status of frontend and backend.\n", "template_file": "template_haproxy_v2_stats_via_prometheus.yaml", "name": "_T_Zbx_Lin_HAPROXY2_stats_Prometheus" @@ -2099,7 +2491,7 @@ "name": "template_needrestart", "template": "App Needrestart", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Others", @@ -2110,14 +2502,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290182, "description": "## Overview\n\nTemplate for needrestart to check if the server needs a reboot / restart of services after package upgrade.\n\n\n[www.kaneo-gmbh.de](https://www.kaneo-gmbh.de)\n\n\n### Install packages\n\n\n\n```\napt install needrestart\n```\n\n### Zabbix agent user parameter:\n\n\n\n```\nUserParameter=needrestart.kernel,sudo needrestart -b -r l -k | grep 'NEEDRESTART-KSTA:' | grep -Eo '[0-9]' \nUserParameter=needrestart.libs,sudo needrestart -b -r l -l | grep NEEDRESTART-SVC | wc -l\n```\n\n### sudoers entry:\n\n\n\n```\n# allow zabbix to check for needrestart in batch listing mode \nzabbix ALL = NOPASSWD: /usr/sbin/needrestart -b -r l * \n \n\n```\n\n\n## Author\n\nkaneo GmbH", "template_file": "template_needrestart.xml", "name": "App Needrestart" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290182, + "description": "## Overview\n\nTemplate for needrestart to check if the server needs a reboot / restart of services after package upgrade.\n\n\n[www.kaneo-gmbh.de](https://www.kaneo-gmbh.de)\n\n\n### Install packages\n\n\n\n```\napt install needrestart\n```\n\n### Zabbix agent user parameter:\n\n\n\n```\nUserParameter=needrestart.kernel,sudo needrestart -b -r l -k | grep 'NEEDRESTART-KSTA:' | grep -Eo '[0-9]' \nUserParameter=needrestart.libs,sudo needrestart -b -r l -l | grep NEEDRESTART-SVC | wc -l\n```\n\n### sudoers entry:\n\n\n\n```\n# allow zabbix to check for needrestart in batch listing mode \nzabbix ALL = NOPASSWD: /usr/sbin/needrestart -b -r l * \n \n\n```\n\n\n## Author\n\nkaneo GmbH\n", + "template_file": "template_needrestart.yaml", + "name": "App Needrestart" + }, + { + "version": 6.0, + "sync": 1646290182, "description": "## Overview\n\nTemplate for needrestart to check if the server needs a reboot / restart of services after package upgrade.\n\n\n[www.kaneo-gmbh.de](https://www.kaneo-gmbh.de)\n\n\n### Install packages\n\n\n\n```\napt install needrestart\n```\n\n### Zabbix agent user parameter:\n\n\n\n```\nUserParameter=needrestart.kernel,sudo needrestart -b -r l -k | grep 'NEEDRESTART-KSTA:' | grep -Eo '[0-9]' \nUserParameter=needrestart.libs,sudo needrestart -b -r l -l | grep NEEDRESTART-SVC | wc -l\n```\n\n### sudoers entry:\n\n\n\n```\n# allow zabbix to check for needrestart in batch listing mode \nzabbix ALL = NOPASSWD: /usr/sbin/needrestart -b -r l * \n \n\n```\n\n\n## Author\n\nkaneo GmbH\n", "template_file": "template_needrestart.yaml", "name": "App Needrestart" @@ -2133,7 +2532,7 @@ "name": "template_okta_ad_agent_status", "template": "OKTA AD Agent Healthcheck", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Others", @@ -2144,14 +2543,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290182, "description": "## Overview\n\nEasy to use, just add the template in and link it\n\n\n\n## Author\n\nBilal Habib", "template_file": "template_okta_ad_agent_status.xml", "name": "OKTA AD Agent Healthcheck" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290182, + "description": "## Overview\n\nEasy to use, just add the template in and link it\n\n\n\n## Author\n\nBilal Habib\n", + "template_file": "template_okta_ad_agent_status.yaml", + "name": "OKTA AD Agent Healthcheck" + }, + { + "version": 6.0, + "sync": 1646290182, "description": "## Overview\n\nEasy to use, just add the template in and link it\n\n\n\n## Author\n\nBilal Habib\n", "template_file": "template_okta_ad_agent_status.yaml", "name": "OKTA AD Agent Healthcheck" @@ -2167,7 +2573,7 @@ "name": "template_openvpn_for_thevpncompany", "template": "OpenVPN", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Others", @@ -2178,14 +2584,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290182, "description": "## Description\n\nTemplate to monitor VPN Services according to the Open Source configuration provided at https://thevpncompany.com.au The VPN Company provides the source code to create an end-to-end VPN Company.\n\n## Overview\n\n[TheVPNCompany.com.au](https://thevpncompany.com.au) offers an open source end to end solution for VPN Companies. In order to manage the OpenVPN Infrastructure, those templates are published.\n\n\nPlease visit [TheVPNCompany.com.au](https://thevpncompany.com.au) on how to install and configure the templates.\n\n\nThose templates allows the user to:\n\n\n - Discover how many users are connected to the OpenVPN backend\n\n\n - Monitor how much bandwidth those users have consumed in the current month\n\n\n - Monitor how much total bandwidth the OpenVPN server has consumed in the current month", "template_file": "template_openvpn_for_thevpncompany.xml", "name": "OpenVPN" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290182, + "description": "## Description\n\nTemplate to monitor VPN Services according to the Open Source configuration provided at https://thevpncompany.com.au The VPN Company provides the source code to create an end-to-end VPN Company.\n\n## Overview\n\n[TheVPNCompany.com.au](https://thevpncompany.com.au) offers an open source end to end solution for VPN Companies. In order to manage the OpenVPN Infrastructure, those templates are published.\n\n\nPlease visit [TheVPNCompany.com.au](https://thevpncompany.com.au) on how to install and configure the templates.\n\n\nThose templates allows the user to:\n\n\n - Discover how many users are connected to the OpenVPN backend\n\n\n - Monitor how much bandwidth those users have consumed in the current month\n\n\n - Monitor how much total bandwidth the OpenVPN server has consumed in the current month\n\n\n \n\n\n \n\n\n \n\n\n \n\n\n \n", + "template_file": "template_openvpn_for_thevpncompany.yaml", + "name": "OpenVPN" + }, + { + "version": 6.0, + "sync": 1646290182, "description": "## Description\n\nTemplate to monitor VPN Services according to the Open Source configuration provided at https://thevpncompany.com.au The VPN Company provides the source code to create an end-to-end VPN Company.\n\n## Overview\n\n[TheVPNCompany.com.au](https://thevpncompany.com.au) offers an open source end to end solution for VPN Companies. In order to manage the OpenVPN Infrastructure, those templates are published.\n\n\nPlease visit [TheVPNCompany.com.au](https://thevpncompany.com.au) on how to install and configure the templates.\n\n\nThose templates allows the user to:\n\n\n - Discover how many users are connected to the OpenVPN backend\n\n\n - Monitor how much bandwidth those users have consumed in the current month\n\n\n - Monitor how much total bandwidth the OpenVPN server has consumed in the current month\n\n\n \n\n\n \n\n\n \n\n\n \n\n\n \n", "template_file": "template_openvpn_for_thevpncompany.yaml", "name": "OpenVPN" @@ -2201,7 +2614,7 @@ "name": "template_sap_process", "template": "SAP Availability Linux", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Others", @@ -2212,14 +2625,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290182, "description": "## Overview\n\n================ SAP-Process ================ \n \nO presente documento tem por objetivo apresentar todas as etapas técnicas \npara implantação do monitoramento dos Processos SAP utilizando shell script \ne saphostctrl, e a função do Userparameter do agente Zabbix. \n \nProjeto idealizado por Wilson Fernandes. \n \nA ideia do projeto foi monitorar os processos SAP abaixo: \n \n- Compile Server \n- Daemon \n- Xsengine \n- Nameserver \n- Preprocessor \n- Webdispatcher\n\n\n\n## Author\n\nwilsonwers", "template_file": "template_sap_process.xml", "name": "SAP Availability Linux" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290182, + "description": "## Overview\n\n================ SAP-Process ================ \n \nO presente documento tem por objetivo apresentar todas as etapas técnicas \npara implantação do monitoramento dos Processos SAP utilizando shell script \ne saphostctrl, e a função do Userparameter do agente Zabbix. \n \nProjeto idealizado por Wilson Fernandes. \n \nA ideia do projeto foi monitorar os processos SAP abaixo: \n \n- Compile Server \n- Daemon \n- Xsengine \n- Nameserver \n- Preprocessor \n- Webdispatcher\n\n\n\n## Author\n\nwilsonwers\n", + "template_file": "template_sap_process.yaml", + "name": "SAP Availability Linux" + }, + { + "version": 6.0, + "sync": 1646290182, "description": "## Overview\n\n================ SAP-Process ================ \n \nO presente documento tem por objetivo apresentar todas as etapas técnicas \npara implantação do monitoramento dos Processos SAP utilizando shell script \ne saphostctrl, e a função do Userparameter do agente Zabbix. \n \nProjeto idealizado por Wilson Fernandes. \n \nA ideia do projeto foi monitorar os processos SAP abaixo: \n \n- Compile Server \n- Daemon \n- Xsengine \n- Nameserver \n- Preprocessor \n- Webdispatcher\n\n\n\n## Author\n\nwilsonwers\n", "template_file": "template_sap_process.yaml", "name": "SAP Availability Linux" @@ -2236,7 +2656,7 @@ "name": "template_tacacs_service", "template": "App TACACS Service", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Others", @@ -2247,14 +2667,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290182, "description": "## Overview\n\nSimple TCP Check of TACACS Service running in TCP Port 49.\n\n\nIncludes:\n\n\n* Item\n* Trigger\n* Graph\n\n\nCreated with Zabbix 3.0, but it can be ported to versions 2.2 and 2.4\n\n\n\n## Author\n\nJose Rosa", "template_file": "template_tacacs_service.xml", "name": "App TACACS Service" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290182, + "description": "## Overview\n\nSimple TCP Check of TACACS Service running in TCP Port 49.\n\n\nIncludes:\n\n\n* Item\n* Trigger\n* Graph\n\n\nCreated with Zabbix 3.0, but it can be ported to versions 2.2 and 2.4\n\n\n\n## Author\n\nJose Rosa\n", + "template_file": "template_tacacs_service.yaml", + "name": "App TACACS Service" + }, + { + "version": 6.0, + "sync": 1646290182, "description": "## Overview\n\nSimple TCP Check of TACACS Service running in TCP Port 49.\n\n\nIncludes:\n\n\n* Item\n* Trigger\n* Graph\n\n\nCreated with Zabbix 3.0, but it can be ported to versions 2.2 and 2.4\n\n\n\n## Author\n\nJose Rosa\n", "template_file": "template_tacacs_service.yaml", "name": "App TACACS Service" @@ -2271,7 +2698,7 @@ "name": "template_trassir_cctv_dvr_sdk", "template": "Template Module ICMP Ping", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Others", @@ -2282,7 +2709,14 @@ "versions": [ { "version": 5.4, - "sync": 1646275491, + "sync": 1646290182, + "description": "Template Module ICMP Ping version: 0.12", + "template_file": "template_trassir_cctv_dvr_sdk.yaml", + "name": "Template Module ICMP Ping" + }, + { + "version": 6.0, + "sync": 1646290182, "description": "Template Module ICMP Ping version: 0.12", "template_file": "template_trassir_cctv_dvr_sdk.yaml", "name": "Template Module ICMP Ping" @@ -2299,7 +2733,7 @@ "name": "template_wireguard_vpn", "template": "App WireGuard", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Others", @@ -2310,14 +2744,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290182, "description": "## Overview\n\nHi,\n\n\nI tried to create a template to monitor WireGuard with Zabbix. \nWireGuard does not really provide any monitoring tool so I had to do with \"wg show\" commands.\n\n\nIt's probably not perfect so if you want to help I'm interested.\n\n\nTemplate provides 2 discovery rules :\n\n\nInterfaces Discovery (wg0, wg1...) : \n- Items to get active peers, total peers, port used and check firewall mark. \n- Triggers to check changes on port, fwmark and numbers of clients. \n- Graph to monitor active and total peers (even if connections are never released by WG once established). \n\n\n\nPeers Discovery (based on public key) : \nI had to truncate keys to 10 characters for easy reading. It should not be a problem because they're random. \n- Items to get for each endpoint : allowed IPs, IP address, port used, incoming/outgoing traffic, keepalive status and the last handshake. \n- Triggers to track changes on allowed IPs, connection port, IP address, keeaplive status and to monitor high traffic and unreachable endpoint. \n- Graph to monitor incoming/outgoing network traffic. \n\n\n\nThis template may work with previous versions of Zabbix but it was tested for Zabbix 4.0 on a Debian 9.6 server.\n\n\nPlease follow the link for instructions and files.\n\n\nHave fun !\n\n\n\n## Author\n\nCryptage21", "template_file": "template_wireguard_vpn.xml", "name": "App WireGuard" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290182, + "description": "## Overview\n\nHi,\n\n\nI tried to create a template to monitor WireGuard with Zabbix. \nWireGuard does not really provide any monitoring tool so I had to do with \"wg show\" commands.\n\n\nIt's probably not perfect so if you want to help I'm interested.\n\n\nTemplate provides 2 discovery rules :\n\n\nInterfaces Discovery (wg0, wg1...) : \n- Items to get active peers, total peers, port used and check firewall mark. \n- Triggers to check changes on port, fwmark and numbers of clients. \n- Graph to monitor active and total peers (even if connections are never released by WG once established). \n\n\n\nPeers Discovery (based on public key) : \nI had to truncate keys to 10 characters for easy reading. It should not be a problem because they're random. \n- Items to get for each endpoint : allowed IPs, IP address, port used, incoming/outgoing traffic, keepalive status and the last handshake. \n- Triggers to track changes on allowed IPs, connection port, IP address, keeaplive status and to monitor high traffic and unreachable endpoint. \n- Graph to monitor incoming/outgoing network traffic. \n\n\n\nThis template may work with previous versions of Zabbix but it was tested for Zabbix 4.0 on a Debian 9.6 server.\n\n\nPlease follow the link for instructions and files.\n\n\nHave fun !\n\n\n\n## Author\n\nCryptage21\n", + "template_file": "template_wireguard_vpn.yaml", + "name": "App WireGuard" + }, + { + "version": 6.0, + "sync": 1646290182, "description": "## Overview\n\nHi,\n\n\nI tried to create a template to monitor WireGuard with Zabbix. \nWireGuard does not really provide any monitoring tool so I had to do with \"wg show\" commands.\n\n\nIt's probably not perfect so if you want to help I'm interested.\n\n\nTemplate provides 2 discovery rules :\n\n\nInterfaces Discovery (wg0, wg1...) : \n- Items to get active peers, total peers, port used and check firewall mark. \n- Triggers to check changes on port, fwmark and numbers of clients. \n- Graph to monitor active and total peers (even if connections are never released by WG once established). \n\n\n\nPeers Discovery (based on public key) : \nI had to truncate keys to 10 characters for easy reading. It should not be a problem because they're random. \n- Items to get for each endpoint : allowed IPs, IP address, port used, incoming/outgoing traffic, keepalive status and the last handshake. \n- Triggers to track changes on allowed IPs, connection port, IP address, keeaplive status and to monitor high traffic and unreachable endpoint. \n- Graph to monitor incoming/outgoing network traffic. \n\n\n\nThis template may work with previous versions of Zabbix but it was tested for Zabbix 4.0 on a Debian 9.6 server.\n\n\nPlease follow the link for instructions and files.\n\n\nHave fun !\n\n\n\n## Author\n\nCryptage21\n", "template_file": "template_wireguard_vpn.yaml", "name": "App WireGuard" @@ -2334,7 +2775,7 @@ "name": "template_zabbix_zookeper", "template": "App Zookeeper", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Others", @@ -2345,14 +2786,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290182, "description": "## Description\n\nZookeper Monitoring Need this userparameter in zabbix_agentd.conf: UserParameter=echo2nc[*],echo $1 | nc $2 $3\n\n## Overview\n\nSystem requirements\n-------------------\n\n\n* [zabbix](http://www.zabbix.com/downloads/) >= 3.4 (preprocessing used by this template)\n* [zookeeper](https://zookeeper.apache.org/releases.html) >= 3.4 (mntr stats)\n* netcat\n\n\nFeatures\n--------\n\n\n* ruok check , mntr stats , graphs, screen\n\n\nZabbix Configuration\n--------------------\n\n\nUserParameter=echo2nc[*],echo $1 | nc $2 $3\n\n\n\n## Author\n\nPatrick Fouquet", "template_file": "template_zabbix_zookeper.xml", "name": "App Zookeeper" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290182, + "description": "## Description\n\nZookeper Monitoring Need this userparameter in zabbix_agentd.conf: UserParameter=echo2nc[*],echo $1 | nc $2 $3\n\n## Overview\n\nSystem requirements\n-------------------\n\n\n* [zabbix](http://www.zabbix.com/downloads/) >= 3.4 (preprocessing used by this template)\n* [zookeeper](https://zookeeper.apache.org/releases.html) >= 3.4 (mntr stats)\n* netcat\n\n\nFeatures\n--------\n\n\n* ruok check , mntr stats , graphs, screen\n\n\nZabbix Configuration\n--------------------\n\n\nUserParameter=echo2nc[*],echo $1 | nc $2 $3\n\n\n\n## Author\n\nPatrick Fouquet\n", + "template_file": "template_zabbix_zookeper.yaml", + "name": "App Zookeeper" + }, + { + "version": 6.0, + "sync": 1646290183, "description": "## Description\n\nZookeper Monitoring Need this userparameter in zabbix_agentd.conf: UserParameter=echo2nc[*],echo $1 | nc $2 $3\n\n## Overview\n\nSystem requirements\n-------------------\n\n\n* [zabbix](http://www.zabbix.com/downloads/) >= 3.4 (preprocessing used by this template)\n* [zookeeper](https://zookeeper.apache.org/releases.html) >= 3.4 (mntr stats)\n* netcat\n\n\nFeatures\n--------\n\n\n* ruok check , mntr stats , graphs, screen\n\n\nZabbix Configuration\n--------------------\n\n\nUserParameter=echo2nc[*],echo $1 | nc $2 $3\n\n\n\n## Author\n\nPatrick Fouquet\n", "template_file": "template_zabbix_zookeper.yaml", "name": "App Zookeeper" @@ -2370,13 +2818,13 @@ { "name": "Queue_managers", "type": "folder", - "sync": 1646275492, + "sync": 1646290183, "next": [ { "name": "template_activemq_jmx", "template": "App ActiveMQ JMX", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Queue_managers", @@ -2387,14 +2835,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290183, "description": "## Overview\n\nYou can configure like the image;\n\n\n![](http://prntscr.com/hk7sbu)\n\n\n\n## Author\n\nArmagan Yaman", "template_file": "template_activemq_jmx.xml", "name": "App ActiveMQ JMX" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290183, + "description": "## Overview\n\nYou can configure like the image;\n\n\n![](http://prntscr.com/hk7sbu)\n\n\n\n## Author\n\nArmagan Yaman\n", + "template_file": "template_activemq_jmx.yaml", + "name": "App ActiveMQ JMX" + }, + { + "version": 6.0, + "sync": 1646290183, "description": "## Overview\n\nYou can configure like the image;\n\n\n![](http://prntscr.com/hk7sbu)\n\n\n\n## Author\n\nArmagan Yaman\n", "template_file": "template_activemq_jmx.yaml", "name": "App ActiveMQ JMX" @@ -2411,7 +2866,7 @@ "name": "template_activemq_jmx_discovery", "template": "JMX ActiveMQ", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Queue_managers", @@ -2422,14 +2877,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290183, "description": "## Overview\n\nDownload and import the Zabbix server.\n\n\n\n## Author\n\nArmagan Yaman", "template_file": "template_activemq_jmx_discovery.xml", "name": "JMX ActiveMQ" }, { "version": 5.4, - "sync": 1646275491, + "sync": 1646290183, + "description": "## Overview\n\nDownload and import the Zabbix server.\n\n\n\n## Author\n\nArmagan Yaman\n", + "template_file": "template_activemq_jmx_discovery.yaml", + "name": "JMX ActiveMQ" + }, + { + "version": 6.0, + "sync": 1646290183, "description": "## Overview\n\nDownload and import the Zabbix server.\n\n\n\n## Author\n\nArmagan Yaman\n", "template_file": "template_activemq_jmx_discovery.yaml", "name": "JMX ActiveMQ" @@ -2446,7 +2908,7 @@ "name": "template_kafka_jmx_discovery", "template": "App Kafka", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Queue_managers", @@ -2457,14 +2919,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275491, + "sync": 1646290183, "description": "## Overview\n\nThis template will use JMX discovery to get metrics about resource usage, topics stats and much more from a Kafka node.", "template_file": "template_kafka_jmx_discovery.xml", "name": "App Kafka" }, { "version": 5.4, - "sync": 1646275492, + "sync": 1646290183, + "description": "## Overview\n\nThis template will use JMX discovery to get metrics about resource usage, topics stats and much more from a Kafka node.\n", + "template_file": "template_kafka_jmx_discovery.yaml", + "name": "App Kafka" + }, + { + "version": 6.0, + "sync": 1646290183, "description": "## Overview\n\nThis template will use JMX discovery to get metrics about resource usage, topics stats and much more from a Kafka node.\n", "template_file": "template_kafka_jmx_discovery.yaml", "name": "App Kafka" @@ -2482,13 +2951,13 @@ { "name": "Security", "type": "folder", - "sync": 1646275492, + "sync": 1646290184, "next": [ { "name": "template_canary_files_monitoring", "template": "Canary", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Security", @@ -2499,14 +2968,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275492, + "sync": 1646290183, "description": "## Overview\n\nCanary files can help you identify information breaches or ransomware attacks.\n\n\nThe script monitors when a file, or set of files, are accessed and upon detection execute several commands to help identify the source of the event.\n\n\nThis script should be run by cron every minute.\n\n\nThe file files2monitor should contain the files to monitor, all in one line, space separated.\n\n\nDependencies: inotify-tools, flock, zabbix\\_sender\n\n\nScript and Zabbix template to:\n\n\nDetect actions on canary files, read, write or open.\n\n\nSupport for multiple files monitoring.\n\n\nAvoid multiple simultaneous execution of the script using flock.\n\n\nSends information to zabbix only when incident happens, for monitoring resource optimization.\n\n\nRecords information from inotify, top, netstat, lsof, who, ps and fuser upon event detection.\n\n\nDependencies: inotify-tools, flock, zabbix\\_sender\n\n\nhttps://github.com/rggassner/gassnerZabbixScripts/tree/master/canary\n\n\nThe shell script can be found in the github repository above.\n\n\nSuggestions are welcome!", "template_file": "template_canary_files_monitoring.xml", "name": "Canary" }, { "version": 5.4, - "sync": 1646275492, + "sync": 1646290184, + "description": "## Overview\n\nCanary files can help you identify information breaches or ransomware attacks.\n\n\nThe script monitors when a file, or set of files, are accessed and upon detection execute several commands to help identify the source of the event.\n\n\nThis script should be run by cron every minute.\n\n\nThe file files2monitor should contain the files to monitor, all in one line, space separated.\n\n\nDependencies: inotify-tools, flock, zabbix\\_sender\n\n\nScript and Zabbix template to:\n\n\nDetect actions on canary files, read, write or open.\n\n\nSupport for multiple files monitoring.\n\n\nAvoid multiple simultaneous execution of the script using flock.\n\n\nSends information to zabbix only when incident happens, for monitoring resource optimization.\n\n\nRecords information from inotify, top, netstat, lsof, who, ps and fuser upon event detection.\n\n\nDependencies: inotify-tools, flock, zabbix\\_sender\n\n\nhttps://github.com/rggassner/gassnerZabbixScripts/tree/master/canary\n\n\nThe shell script can be found in the github repository above.\n\n\nSuggestions are welcome!\n", + "template_file": "template_canary_files_monitoring.yaml", + "name": "Canary" + }, + { + "version": 6.0, + "sync": 1646290184, "description": "## Overview\n\nCanary files can help you identify information breaches or ransomware attacks.\n\n\nThe script monitors when a file, or set of files, are accessed and upon detection execute several commands to help identify the source of the event.\n\n\nThis script should be run by cron every minute.\n\n\nThe file files2monitor should contain the files to monitor, all in one line, space separated.\n\n\nDependencies: inotify-tools, flock, zabbix\\_sender\n\n\nScript and Zabbix template to:\n\n\nDetect actions on canary files, read, write or open.\n\n\nSupport for multiple files monitoring.\n\n\nAvoid multiple simultaneous execution of the script using flock.\n\n\nSends information to zabbix only when incident happens, for monitoring resource optimization.\n\n\nRecords information from inotify, top, netstat, lsof, who, ps and fuser upon event detection.\n\n\nDependencies: inotify-tools, flock, zabbix\\_sender\n\n\nhttps://github.com/rggassner/gassnerZabbixScripts/tree/master/canary\n\n\nThe shell script can be found in the github repository above.\n\n\nSuggestions are welcome!\n", "template_file": "template_canary_files_monitoring.yaml", "name": "Canary" @@ -2523,7 +2999,7 @@ "name": "template_cve-2016-0728_check", "template": "cve-2016-0728", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Security", @@ -2534,14 +3010,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275492, + "sync": 1646290184, "description": "", "template_file": "template_cve-2016-0728_check.xml", "name": "cve-2016-0728" }, { "version": 5.4, - "sync": 1646275492, + "sync": 1646290184, + "description": "", + "template_file": "template_cve-2016-0728_check.yaml", + "name": "cve-2016-0728" + }, + { + "version": 6.0, + "sync": 1646290184, "description": "", "template_file": "template_cve-2016-0728_check.yaml", "name": "cve-2016-0728" @@ -2554,7 +3037,7 @@ "name": "template_devline_windows_monitoring_cctv", "template": "DEVLINE", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Security", @@ -2565,14 +3048,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275492, + "sync": 1646290184, "description": "## Overview\n\nUserParameter=devline.discovery,\"C:\\Windows\\zabbix\\addons\\devline-discovery.exe\" user password 127.0.0.1\n\n\nUserParameter=devline.viewpic[*],\"C:\\Windows\\zabbix\\addons\\devline-check-picture.exe\" user password 127.0.0.1 $1\n\n\n \n\n\n$1 = image-uri\n\n\n \n\n\nТребуется .NetFramework 3.5 на хосте с сервером наблюдения.\n\n\n \n\n\nUPD 2019-13-02: Исправил шаблон. Обнаружил проблему, когда одна из плат видеозахвата перестает работать, то утилита посылает текст вместо числа.\n\n\n \n\n- /etc/zabbix/zabbix\\_agentd.d/hls.conf\n\n\n4. Import template into zabbix server\n\n\n5. Apply template to host\n\n\n6. Add macros {$HLSURI} = \"http://yourdmain.local/playlist.m3u8\"\n\n\n \n\n\nIf you have additions or comments you are welcome!\n\n\n\n## Author\n\nKirill Savin", "template_file": "template_service_hls.xml", "name": "Service HLS" }, { "version": 5.4, - "sync": 1646275495, + "sync": 1646290191, + "description": "## Overview\n\nThis is beta version of HLS checker.\n\n\nThis template can discovery different streams (playlist in playlists file) and show next parameters:\n\n\nThere is presented ts file\n\n\nTotal lenght of ts file\n\n\nTarget duration of ts file\n\n\nDuration of ts file\n\n\nSpended time for download ts file\n\n\nAverage speed for download ts file\n\n\nNot created: different paraneters of ts file from ffprobe. May be later.\n\n\n \n\n\nYou need install python2, m3u8 library and ffmpeg if you want:\n\n\napt install python python-m3u8 python-requests ffmpeg\n\n\n \n\n\n1. Put script to /path\\_to\\_script/check\\_hls\n\n\n2. Give him executable flag by: \n\n\nchmod ugo+x check\\_hls\n\n\n3. Add userparameter into zabbix agent:\n\n\necho \"UserParameter=hls[*], /usr/bin/python /path\\_to\\_script/check\\_hls \\$1 \\$2\" > /etc/zabbix/zabbix\\_agentd.d/hls.conf\n\n\n4. Import template into zabbix server\n\n\n5. Apply template to host\n\n\n6. Add macros {$HLSURI} = \"http://yourdmain.local/playlist.m3u8\"\n\n\n \n\n\nIf you have additions or comments you are welcome!\n\n\n\n## Author\n\nKirill Savin\n", + "template_file": "template_service_hls.yaml", + "name": "Service HLS" + }, + { + "version": 6.0, + "sync": 1646290191, "description": "## Overview\n\nThis is beta version of HLS checker.\n\n\nThis template can discovery different streams (playlist in playlists file) and show next parameters:\n\n\nThere is presented ts file\n\n\nTotal lenght of ts file\n\n\nTarget duration of ts file\n\n\nDuration of ts file\n\n\nSpended time for download ts file\n\n\nAverage speed for download ts file\n\n\nNot created: different paraneters of ts file from ffprobe. May be later.\n\n\n \n\n\nYou need install python2, m3u8 library and ffmpeg if you want:\n\n\napt install python python-m3u8 python-requests ffmpeg\n\n\n \n\n\n1. Put script to /path\\_to\\_script/check\\_hls\n\n\n2. Give him executable flag by: \n\n\nchmod ugo+x check\\_hls\n\n\n3. Add userparameter into zabbix agent:\n\n\necho \"UserParameter=hls[*], /usr/bin/python /path\\_to\\_script/check\\_hls \\$1 \\$2\" > /etc/zabbix/zabbix\\_agentd.d/hls.conf\n\n\n4. Import template into zabbix server\n\n\n5. Apply template to host\n\n\n6. Add macros {$HLSURI} = \"http://yourdmain.local/playlist.m3u8\"\n\n\n \n\n\nIf you have additions or comments you are welcome!\n\n\n\n## Author\n\nKirill Savin\n", "template_file": "template_service_hls.yaml", "name": "Service HLS" @@ -2626,7 +3123,7 @@ "name": "template_vizrt_viz_engine_snmp", "template": "Vizrt SNMP", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "TV_Broadcasting", @@ -2637,14 +3134,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275495, + "sync": 1646290191, "description": "## Overview\n\n Hello!\n\n\nThis is simple SNMP tepmplate fo monitor Graphical Inserter Vizrt Viz Engine. \n\n\nVizrt support SNMP beginning with version 3.11.\n\n\nThis is my first publish.\n\n\nI am glad to any wishes and questions.\n\n\n \n\n\nChecks:\n\n\nReady For Connect\n\n\nOn Air\n\n\nConnected To Db\n\n\nPost Render Mode\n\n\nNLE Mode\n\n\nCurrent Frame Rate\n\n\nRetrace Counter\n\n\nViz Engine Version\n\n\nSystem ID\n\n\nComputer Type\n\n\nTCP Port\n\n\nGenlock Status\n\n\nVideo In 1 Status\n\n\nVideo In 2 Status\n\n\nVideo In 3 Status\n\n\nVideo In 4 Status\n\n\nVideo In 5 Status\n\n\nVideo In 6 Status\n\n\nVideo In 7 Status\n\n\nVideo In 8 Status\n\n\nClip 1 Status\n\n\nClip 2 Status\n\n\nClip 3 Status\n\n\nClip 4 Status\n\n\nClip 5 Status\n\n\nClip 6 Status\n\n\nClip 7 Status\n\n\nClip 8 Status\n\n\nTexture Memory Free\n\n\nTexture Memory Total\n\n\nTexture Memory Used\n\n\nRenderer Scene Front\n\n\nRenderer Scene Middle\n\n\nRenderer Scene Back\n\n\nPost Scene Front\n\n\nPost Scene Middle\n\n\nPost Scene Back\n\n\nRetrace Counter Moving\n\n\n \n\n\nTriggers:\n\n\nVizrt Clip Status is not ok \n\n\nVizrt Engine not OnAIR!!!\n\n\nVizrt Genlock Status is not ok \n\n\nVizrt not Connected To DB (Graphic HUB)\n\n\nVizrt not Ready for connect\n\n\nVizrt Texture Memory used more 80%\n\n\nVizrt Texture Memory used more 90%\n\n\nVizrt Video In Status is not ok \n\n\n\n## Author\n\nKirill Savin", "template_file": "template_vizrt_viz_engine_snmp.xml", "name": "Vizrt SNMP" }, { "version": 5.4, - "sync": 1646275495, + "sync": 1646290191, + "description": "## Overview\n\n Hello!\n\n\nThis is simple SNMP tepmplate fo monitor Graphical Inserter Vizrt Viz Engine. \n\n\nVizrt support SNMP beginning with version 3.11.\n\n\nThis is my first publish.\n\n\nI am glad to any wishes and questions.\n\n\n \n\n\nChecks:\n\n\nReady For Connect\n\n\nOn Air\n\n\nConnected To Db\n\n\nPost Render Mode\n\n\nNLE Mode\n\n\nCurrent Frame Rate\n\n\nRetrace Counter\n\n\nViz Engine Version\n\n\nSystem ID\n\n\nComputer Type\n\n\nTCP Port\n\n\nGenlock Status\n\n\nVideo In 1 Status\n\n\nVideo In 2 Status\n\n\nVideo In 3 Status\n\n\nVideo In 4 Status\n\n\nVideo In 5 Status\n\n\nVideo In 6 Status\n\n\nVideo In 7 Status\n\n\nVideo In 8 Status\n\n\nClip 1 Status\n\n\nClip 2 Status\n\n\nClip 3 Status\n\n\nClip 4 Status\n\n\nClip 5 Status\n\n\nClip 6 Status\n\n\nClip 7 Status\n\n\nClip 8 Status\n\n\nTexture Memory Free\n\n\nTexture Memory Total\n\n\nTexture Memory Used\n\n\nRenderer Scene Front\n\n\nRenderer Scene Middle\n\n\nRenderer Scene Back\n\n\nPost Scene Front\n\n\nPost Scene Middle\n\n\nPost Scene Back\n\n\nRetrace Counter Moving\n\n\n \n\n\nTriggers:\n\n\nVizrt Clip Status is not ok \n\n\nVizrt Engine not OnAIR!!!\n\n\nVizrt Genlock Status is not ok \n\n\nVizrt not Connected To DB (Graphic HUB)\n\n\nVizrt not Ready for connect\n\n\nVizrt Texture Memory used more 80%\n\n\nVizrt Texture Memory used more 90%\n\n\nVizrt Video In Status is not ok \n\n\n\n## Author\n\nKirill Savin\n", + "template_file": "template_vizrt_viz_engine_snmp.yaml", + "name": "Vizrt SNMP" + }, + { + "version": 6.0, + "sync": 1646290191, "description": "## Overview\n\n Hello!\n\n\nThis is simple SNMP tepmplate fo monitor Graphical Inserter Vizrt Viz Engine. \n\n\nVizrt support SNMP beginning with version 3.11.\n\n\nThis is my first publish.\n\n\nI am glad to any wishes and questions.\n\n\n \n\n\nChecks:\n\n\nReady For Connect\n\n\nOn Air\n\n\nConnected To Db\n\n\nPost Render Mode\n\n\nNLE Mode\n\n\nCurrent Frame Rate\n\n\nRetrace Counter\n\n\nViz Engine Version\n\n\nSystem ID\n\n\nComputer Type\n\n\nTCP Port\n\n\nGenlock Status\n\n\nVideo In 1 Status\n\n\nVideo In 2 Status\n\n\nVideo In 3 Status\n\n\nVideo In 4 Status\n\n\nVideo In 5 Status\n\n\nVideo In 6 Status\n\n\nVideo In 7 Status\n\n\nVideo In 8 Status\n\n\nClip 1 Status\n\n\nClip 2 Status\n\n\nClip 3 Status\n\n\nClip 4 Status\n\n\nClip 5 Status\n\n\nClip 6 Status\n\n\nClip 7 Status\n\n\nClip 8 Status\n\n\nTexture Memory Free\n\n\nTexture Memory Total\n\n\nTexture Memory Used\n\n\nRenderer Scene Front\n\n\nRenderer Scene Middle\n\n\nRenderer Scene Back\n\n\nPost Scene Front\n\n\nPost Scene Middle\n\n\nPost Scene Back\n\n\nRetrace Counter Moving\n\n\n \n\n\nTriggers:\n\n\nVizrt Clip Status is not ok \n\n\nVizrt Engine not OnAIR!!!\n\n\nVizrt Genlock Status is not ok \n\n\nVizrt not Connected To DB (Graphic HUB)\n\n\nVizrt not Ready for connect\n\n\nVizrt Texture Memory used more 80%\n\n\nVizrt Texture Memory used more 90%\n\n\nVizrt Video In Status is not ok \n\n\n\n## Author\n\nKirill Savin\n", "template_file": "template_vizrt_viz_engine_snmp.yaml", "name": "Vizrt SNMP" @@ -2662,13 +3166,13 @@ { "name": "Web-servers", "type": "folder", - "sync": 1646275496, + "sync": 1646290193, "next": [ { "name": "template_apache_http_server", "template": "Apache", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Web-servers", @@ -2679,14 +3183,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275495, + "sync": 1646290191, "description": "## Overview\n\nThis template is for Apache HTTP server monitoring. It contains one master item that connects to HTTP Agent every 10 seconds, requests server-status page, provided by mod-status Apache module and spreads collected information between 18 dependent items. No triggers. See screenshot for details.\n\n\nRefer to the blog post\n\n\n\n\n\nfor even more details.\n\n\n\n## Author\n\nAndris Zeila", "template_file": "template_apache_http_server.xml", "name": "Apache" }, { "version": 5.4, - "sync": 1646275495, + "sync": 1646290191, + "description": "## Overview\n\nThis template is for Apache HTTP server monitoring. It contains one master item that connects to HTTP Agent every 10 seconds, requests server-status page, provided by mod-status Apache module and spreads collected information between 18 dependent items. No triggers. See screenshot for details.\n\n\nRefer to the blog post\n\n\n\n\n\nfor even more details.\n\n\n\n## Author\n\nAndris Zeila\n", + "template_file": "template_apache_http_server.yaml", + "name": "Apache" + }, + { + "version": 6.0, + "sync": 1646290191, "description": "## Overview\n\nThis template is for Apache HTTP server monitoring. It contains one master item that connects to HTTP Agent every 10 seconds, requests server-status page, provided by mod-status Apache module and spreads collected information between 18 dependent items. No triggers. See screenshot for details.\n\n\nRefer to the blog post\n\n\n\n\n\nfor even more details.\n\n\n\n## Author\n\nAndris Zeila\n", "template_file": "template_apache_http_server.yaml", "name": "Apache" @@ -2704,7 +3215,7 @@ "name": "template_apache_solr_statistics_via_json", "template": "App Solr", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Web-servers", @@ -2715,14 +3226,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275495, + "sync": 1646290191, "description": "## Description\n\nTemplate for monitoring Solr using json statistics. http://{USERNAME}@{PASSWORD}:{HOST.CONN}/solr/admin/metrics\n\n## Overview\n\n**Zabbix Template Solr statistics**\n-----------------------------------\n\n\n Template for monitoring Solr using JSON statistics.\n\n\n \n\n\n**Versions**\n------------\n\n\n I tested this using zabbix 5.0.9 and Solr 8.6.3, but maybe it works with different versions.\n\n\n \n\n\n**Requirements**\n----------------\n\n\n Zabbix version > 5.0 because template is using HTTP agent, Dependent items and JSON Path. You need to setup user and password for accessing Solr statistics JSON:\n\n\n* [http://{USERNAME}:{PASSWORD}@{HOST.CONN}/solr/admin/metrics](http://{USERNAME}@{PASSWORD}{HOST.CONN})\n\n\n \n\n\n**Installation**\n----------------\n\n\n* Download Zabbix template\n* Import the template on Zabbix\n* Create host on Zabbix and apply the template (I have configured to connect to DNS name, because it will be used in {HOST.CONN})\n* On host configuration, modify macros {$SOLR\\_USERNAME} and {$SOLR\\_PASSWORD} with the information you created.\n* You can change macros {$PROTOCOL}, {$URI} from host and/or template to your environment\n\n\n## Author\n\nFelipe de Moura Vieira", "template_file": "template_apache_solr_statistics_via_json.xml", "name": "App Solr" }, { "version": 5.4, - "sync": 1646275496, + "sync": 1646290191, + "description": "## Description\n\nTemplate for monitoring Solr using json statistics. http://{USERNAME}@{PASSWORD}:{HOST.CONN}/solr/admin/metrics\n\n## Overview\n\n**Zabbix Template Solr statistics**\n-----------------------------------\n\n\n Template for monitoring Solr using JSON statistics.\n\n\n \n\n\n**Versions**\n------------\n\n\n I tested this using zabbix 5.0.9 and Solr 8.6.3, but maybe it works with different versions.\n\n\n \n\n\n**Requirements**\n----------------\n\n\n Zabbix version > 5.0 because template is using HTTP agent, Dependent items and JSON Path. You need to setup user and password for accessing Solr statistics JSON:\n\n\n* [http://{USERNAME}:{PASSWORD}@{HOST.CONN}/solr/admin/metrics](http://{USERNAME}@{PASSWORD}{HOST.CONN})\n\n\n \n\n\n**Installation**\n----------------\n\n\n* Download Zabbix template\n* Import the template on Zabbix\n* Create host on Zabbix and apply the template (I have configured to connect to DNS name, because it will be used in {HOST.CONN})\n* On host configuration, modify macros {$SOLR\\_USERNAME} and {$SOLR\\_PASSWORD} with the information you created.\n* You can change macros {$PROTOCOL}, {$URI} from host and/or template to your environment\n\n\n## Author\n\nFelipe de Moura Vieira\n", + "template_file": "template_apache_solr_statistics_via_json.yaml", + "name": "App Solr" + }, + { + "version": 6.0, + "sync": 1646290192, "description": "## Description\n\nTemplate for monitoring Solr using json statistics. http://{USERNAME}@{PASSWORD}:{HOST.CONN}/solr/admin/metrics\n\n## Overview\n\n**Zabbix Template Solr statistics**\n-----------------------------------\n\n\n Template for monitoring Solr using JSON statistics.\n\n\n \n\n\n**Versions**\n------------\n\n\n I tested this using zabbix 5.0.9 and Solr 8.6.3, but maybe it works with different versions.\n\n\n \n\n\n**Requirements**\n----------------\n\n\n Zabbix version > 5.0 because template is using HTTP agent, Dependent items and JSON Path. You need to setup user and password for accessing Solr statistics JSON:\n\n\n* [http://{USERNAME}:{PASSWORD}@{HOST.CONN}/solr/admin/metrics](http://{USERNAME}@{PASSWORD}{HOST.CONN})\n\n\n \n\n\n**Installation**\n----------------\n\n\n* Download Zabbix template\n* Import the template on Zabbix\n* Create host on Zabbix and apply the template (I have configured to connect to DNS name, because it will be used in {HOST.CONN})\n* On host configuration, modify macros {$SOLR\\_USERNAME} and {$SOLR\\_PASSWORD} with the information you created.\n* You can change macros {$PROTOCOL}, {$URI} from host and/or template to your environment\n\n\n## Author\n\nFelipe de Moura Vieira\n", "template_file": "template_apache_solr_statistics_via_json.yaml", "name": "App Solr" @@ -2739,7 +3257,7 @@ "name": "template_app_nginx_for_zabbix_3.4.x", "template": "App Nginx by Alex Gluck", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Web-servers", @@ -2750,14 +3268,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275496, + "sync": 1646290192, "description": "## Overview\n\nSystem requirements\n-------------------\n\n\n[Nginx](http://nginx.org/ \"Nginx\"), with configured `http\\_stub\\_status\\_module`\n\n\nFeatures\n--------\n\n\n##### HTTP/HTTPS support\n\n\n##### Connection Statistics:\n\n\n* Active\n* Reading\n* Waiting\n* Writing\n\n\n##### Request Statistics:\n\n\n* Accepted\n* Handled\n* Total\n\n\n##### Graph and screen:\n\n\n* 'Requests Statistics' graph\n* 'Connection Status' graph\n* Screen combining both graph\n\n\n##### Macros for customization:\n\n\n* {$NGINX\\_HOST}\n* {$NGINX\\_STATS\\_URI}\n* {$NGINX\\_PORT}\n* {$NGINX\\_REQ\\_NUM}\n* {$NGINX\\_CON\\_NUM}\n\n\nInstallation\n------------\n\n\n### Nginx Configuration\n\n\n \n\n\nAdd the following example to your default vhost configuration file:\n\n\n\n```\nlocation /nginx\\_status { \n stub\\_status on; \n access\\_log off; \n allow 127.0.0.1; \n allow ::1; \n deny all; \n}\n```\n\n\n```\n \n```\n\n### Zabbix Configuration\n\n\n \n\n\n1. Import XML template file (`zbx\\_template\\_nginx.xml`) into Zabbix via Web GUI (Configuration -> Templates -> Import).\n2. Assign the imported template to a host and enjoy!\n\n\n## Author\n\nAlex Gluck", "template_file": "template_app_nginx_for_zabbix_3.4.x.xml", "name": "App Nginx by Alex Gluck" }, { "version": 5.4, - "sync": 1646275496, + "sync": 1646290192, + "description": "## Overview\n\nSystem requirements\n-------------------\n\n\n[Nginx](http://nginx.org/ \"Nginx\"), with configured `http\\_stub\\_status\\_module`\n\n\nFeatures\n--------\n\n\n##### HTTP/HTTPS support\n\n\n##### Connection Statistics:\n\n\n* Active\n* Reading\n* Waiting\n* Writing\n\n\n##### Request Statistics:\n\n\n* Accepted\n* Handled\n* Total\n\n\n##### Graph and screen:\n\n\n* 'Requests Statistics' graph\n* 'Connection Status' graph\n* Screen combining both graph\n\n\n##### Macros for customization:\n\n\n* {$NGINX\\_HOST}\n* {$NGINX\\_STATS\\_URI}\n* {$NGINX\\_PORT}\n* {$NGINX\\_REQ\\_NUM}\n* {$NGINX\\_CON\\_NUM}\n\n\nInstallation\n------------\n\n\n### Nginx Configuration\n\n\n \n\n\nAdd the following example to your default vhost configuration file:\n\n\n\n```\nlocation /nginx\\_status { \n stub\\_status on; \n access\\_log off; \n allow 127.0.0.1; \n allow ::1; \n deny all; \n}\n```\n\n\n```\n \n```\n\n### Zabbix Configuration\n\n\n \n\n\n1. Import XML template file (`zbx\\_template\\_nginx.xml`) into Zabbix via Web GUI (Configuration -> Templates -> Import).\n2. Assign the imported template to a host and enjoy!\n\n\n## Author\n\nAlex Gluck\n", + "template_file": "template_app_nginx_for_zabbix_3.4.x.yaml", + "name": "App Nginx by Alex Gluck" + }, + { + "version": 6.0, + "sync": 1646290192, "description": "## Overview\n\nSystem requirements\n-------------------\n\n\n[Nginx](http://nginx.org/ \"Nginx\"), with configured `http\\_stub\\_status\\_module`\n\n\nFeatures\n--------\n\n\n##### HTTP/HTTPS support\n\n\n##### Connection Statistics:\n\n\n* Active\n* Reading\n* Waiting\n* Writing\n\n\n##### Request Statistics:\n\n\n* Accepted\n* Handled\n* Total\n\n\n##### Graph and screen:\n\n\n* 'Requests Statistics' graph\n* 'Connection Status' graph\n* Screen combining both graph\n\n\n##### Macros for customization:\n\n\n* {$NGINX\\_HOST}\n* {$NGINX\\_STATS\\_URI}\n* {$NGINX\\_PORT}\n* {$NGINX\\_REQ\\_NUM}\n* {$NGINX\\_CON\\_NUM}\n\n\nInstallation\n------------\n\n\n### Nginx Configuration\n\n\n \n\n\nAdd the following example to your default vhost configuration file:\n\n\n\n```\nlocation /nginx\\_status { \n stub\\_status on; \n access\\_log off; \n allow 127.0.0.1; \n allow ::1; \n deny all; \n}\n```\n\n\n```\n \n```\n\n### Zabbix Configuration\n\n\n \n\n\n1. Import XML template file (`zbx\\_template\\_nginx.xml`) into Zabbix via Web GUI (Configuration -> Templates -> Import).\n2. Assign the imported template to a host and enjoy!\n\n\n## Author\n\nAlex Gluck\n", "template_file": "template_app_nginx_for_zabbix_3.4.x.yaml", "name": "App Nginx by Alex Gluck" @@ -2774,7 +3299,7 @@ "name": "template_domain_registration_expiration_and_ssl_certificates_check_lld", "template": "SSL check LLD", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Web-servers", @@ -2785,14 +3310,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275496, + "sync": 1646290192, "description": "## Overview\n\nMain idea is monitoring several URL with SSL in one Zabbix host. Data for LLD provide JSON file.\n\n\nThis is originally based on [https://share.zabbix.com/cat-app/web-servers/ssl-certificates-check](cat-app/web-servers/ssl-certificates-check) with modifications to the script and template.\n\n\nAdded domain registration expiration check", "template_file": "template_domain_registration_expiration_and_ssl_certificates_check_lld.xml", "name": "SSL check LLD" }, { "version": 5.4, - "sync": 1646275496, + "sync": 1646290192, + "description": "## Overview\n\nMain idea is monitoring several URL with SSL in one Zabbix host. Data for LLD provide JSON file.\n\n\nThis is originally based on [https://share.zabbix.com/cat-app/web-servers/ssl-certificates-check](cat-app/web-servers/ssl-certificates-check) with modifications to the script and template.\n\n\nAdded domain registration expiration check\n", + "template_file": "template_domain_registration_expiration_and_ssl_certificates_check_lld.yaml", + "name": "SSL check LLD" + }, + { + "version": 6.0, + "sync": 1646290192, "description": "## Overview\n\nMain idea is monitoring several URL with SSL in one Zabbix host. Data for LLD provide JSON file.\n\n\nThis is originally based on [https://share.zabbix.com/cat-app/web-servers/ssl-certificates-check](cat-app/web-servers/ssl-certificates-check) with modifications to the script and template.\n\n\nAdded domain registration expiration check\n", "template_file": "template_domain_registration_expiration_and_ssl_certificates_check_lld.yaml", "name": "SSL check LLD" @@ -2810,7 +3342,7 @@ "name": "template_fcgi_stat_getter._monitor_php-fpm_without_nginx_proxy", "template": "App PHP-FPM", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Web-servers", @@ -2821,14 +3353,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275496, + "sync": 1646290192, "description": "## Overview\n\nEnglish description - \n\n\nСкрипт для получения статистики из PHP-FPM, который можно использовать в Zabbix. Реализация на Go вот этого скрипта - \n\n\ngo version go1.7.4 darwin/amd64\n\n\nНастройка PHP-FPM\n-----------------\n\n\nВ конфиге PHP-FPM пула нужно включить статус и пинг:\n\n\n\n```\npm.status\\_path = /status \n```\n\n\n```\nping.path = /ping \n```\n\nИ сделать restart сервера.\n\n\nНастройка Zabbix\n----------------\n\n\nНужно скомпилировать бинарник под ту платформу, на которой запущен Zabbix сервер, для этого нужно использовать команду:\n\n\n\n```\nenv GOOS={OS} GOARCH={ARCH} go build -v github.com/username/fcgi\\_stat\\_getter\n```\n\n{OS} - тип операционной системы, может быть:\n\n\n* Mac os - darwin\n* Windows - windows\n* Linux - linux\n* FreeBSD - freebsd\n\n\n{ARCH} - архитектура, может быть:\n\n\n* x86\\_64 - amd64\n* x86 - 386\n* ARM - arm (linux only)\n\n\nExample:\n\n\n\n```\n$ env GOOS=linux GOARCH=amd64 go build -v github.com/tonymadbrain/fcgi\\_stat\\_getter\n```\n\nЗакинуть бинарник на сервер Zabbix в каталог /usr/lib/zabbix/externalscripts, сделать его исполняемым:\n\n\n\n```\n chmod +x fcgi\\_stat\\_getter \n```\n\nсделать владельцем файла Zabbix:\n\n\n\n```\nchown zabbix:zabbix fcgi\\_stat\\_getter \n```\n\nЗатем нужно импортировать шаблон *zbx\\_fcgi\\_template.xml* в Zabbix фронтенде и прикрепить его к нужному серверу. Ждать данных.\n\n\n\n## Author\n\nAntony Ryabov", "template_file": "template_fcgi_stat_getter._monitor_php-fpm_without_nginx_proxy.xml", "name": "App PHP-FPM" }, { "version": 5.4, - "sync": 1646275496, + "sync": 1646290192, + "description": "## Overview\n\nEnglish description - \n\n\nСкрипт для получения статистики из PHP-FPM, который можно использовать в Zabbix. Реализация на Go вот этого скрипта - \n\n\ngo version go1.7.4 darwin/amd64\n\n\nНастройка PHP-FPM\n-----------------\n\n\nВ конфиге PHP-FPM пула нужно включить статус и пинг:\n\n\n\n```\npm.status\\_path = /status \n```\n\n\n```\nping.path = /ping \n```\n\nИ сделать restart сервера.\n\n\nНастройка Zabbix\n----------------\n\n\nНужно скомпилировать бинарник под ту платформу, на которой запущен Zabbix сервер, для этого нужно использовать команду:\n\n\n\n```\nenv GOOS={OS} GOARCH={ARCH} go build -v github.com/username/fcgi\\_stat\\_getter\n```\n\n{OS} - тип операционной системы, может быть:\n\n\n* Mac os - darwin\n* Windows - windows\n* Linux - linux\n* FreeBSD - freebsd\n\n\n{ARCH} - архитектура, может быть:\n\n\n* x86\\_64 - amd64\n* x86 - 386\n* ARM - arm (linux only)\n\n\nExample:\n\n\n\n```\n$ env GOOS=linux GOARCH=amd64 go build -v github.com/tonymadbrain/fcgi\\_stat\\_getter\n```\n\nЗакинуть бинарник на сервер Zabbix в каталог /usr/lib/zabbix/externalscripts, сделать его исполняемым:\n\n\n\n```\n chmod +x fcgi\\_stat\\_getter \n```\n\nсделать владельцем файла Zabbix:\n\n\n\n```\nchown zabbix:zabbix fcgi\\_stat\\_getter \n```\n\nЗатем нужно импортировать шаблон *zbx\\_fcgi\\_template.xml* в Zabbix фронтенде и прикрепить его к нужному серверу. Ждать данных.\n\n\n\n## Author\n\nAntony Ryabov\n", + "template_file": "template_fcgi_stat_getter._monitor_php-fpm_without_nginx_proxy.yaml", + "name": "App PHP-FPM" + }, + { + "version": 6.0, + "sync": 1646290192, "description": "## Overview\n\nEnglish description - \n\n\nСкрипт для получения статистики из PHP-FPM, который можно использовать в Zabbix. Реализация на Go вот этого скрипта - \n\n\ngo version go1.7.4 darwin/amd64\n\n\nНастройка PHP-FPM\n-----------------\n\n\nВ конфиге PHP-FPM пула нужно включить статус и пинг:\n\n\n\n```\npm.status\\_path = /status \n```\n\n\n```\nping.path = /ping \n```\n\nИ сделать restart сервера.\n\n\nНастройка Zabbix\n----------------\n\n\nНужно скомпилировать бинарник под ту платформу, на которой запущен Zabbix сервер, для этого нужно использовать команду:\n\n\n\n```\nenv GOOS={OS} GOARCH={ARCH} go build -v github.com/username/fcgi\\_stat\\_getter\n```\n\n{OS} - тип операционной системы, может быть:\n\n\n* Mac os - darwin\n* Windows - windows\n* Linux - linux\n* FreeBSD - freebsd\n\n\n{ARCH} - архитектура, может быть:\n\n\n* x86\\_64 - amd64\n* x86 - 386\n* ARM - arm (linux only)\n\n\nExample:\n\n\n\n```\n$ env GOOS=linux GOARCH=amd64 go build -v github.com/tonymadbrain/fcgi\\_stat\\_getter\n```\n\nЗакинуть бинарник на сервер Zabbix в каталог /usr/lib/zabbix/externalscripts, сделать его исполняемым:\n\n\n\n```\n chmod +x fcgi\\_stat\\_getter \n```\n\nсделать владельцем файла Zabbix:\n\n\n\n```\nchown zabbix:zabbix fcgi\\_stat\\_getter \n```\n\nЗатем нужно импортировать шаблон *zbx\\_fcgi\\_template.xml* в Zabbix фронтенде и прикрепить его к нужному серверу. Ждать данных.\n\n\n\n## Author\n\nAntony Ryabov\n", "template_file": "template_fcgi_stat_getter._monitor_php-fpm_without_nginx_proxy.yaml", "name": "App PHP-FPM" @@ -2846,7 +3385,7 @@ "name": "template_microsoft_iis_7.5,_8.0,_8.5_and_10_services,_ports_and_performance_counters", "template": "App IIS Service", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Web-servers", @@ -2857,14 +3396,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275496, + "sync": 1646290192, "description": "## Overview\n\n16 Items, 4 Triggers 5 Graphs and 2 Screens built for IIS 7.5, 8.0, 8.5 and 10 Services, Ports and Performance Counters.\n\n\nDeveloped through \"Template Windows 2008 R2 IIS Server\" template. ([https://share.zabbix.com/cat-app/web-servers/template-windows-2008-r2-iis-server](cat-app/web-servers/template-windows-2008-r2-iis-server))", "template_file": "template_microsoft_iis_7.5,_8.0,_8.5_and_10_services,_ports_and_performance_counters..xml", "name": "App IIS Service" }, { "version": 5.4, - "sync": 1646275496, + "sync": 1646290192, + "description": "## Overview\n\n16 Items, 4 Triggers 5 Graphs and 2 Screens built for IIS 7.5, 8.0, 8.5 and 10 Services, Ports and Performance Counters.\n\n\nDeveloped through \"Template Windows 2008 R2 IIS Server\" template. ([https://share.zabbix.com/cat-app/web-servers/template-windows-2008-r2-iis-server](cat-app/web-servers/template-windows-2008-r2-iis-server))\n", + "template_file": "template_microsoft_iis_7.5,_8.0,_8.5_and_10_services,_ports_and_performance_counters..yaml", + "name": "App IIS Service" + }, + { + "version": 6.0, + "sync": 1646290192, "description": "## Overview\n\n16 Items, 4 Triggers 5 Graphs and 2 Screens built for IIS 7.5, 8.0, 8.5 and 10 Services, Ports and Performance Counters.\n\n\nDeveloped through \"Template Windows 2008 R2 IIS Server\" template. ([https://share.zabbix.com/cat-app/web-servers/template-windows-2008-r2-iis-server](cat-app/web-servers/template-windows-2008-r2-iis-server))\n", "template_file": "template_microsoft_iis_7.5,_8.0,_8.5_and_10_services,_ports_and_performance_counters..yaml", "name": "App IIS Service" @@ -2877,7 +3423,7 @@ "name": "template_microsoft_iis_8,_8.5,_10_for_rus_server", "template": "App IIS Service_RUS", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Web-servers", @@ -2888,14 +3434,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275496, + "sync": 1646290192, "description": "## Overview\n\n16 Items, 4 Triggers 5 Graphs and 2 Screens built for IIS 7.5, 8.0, 8.5 and 10 Services, Ports and Performance Counters. Developed through \"Template Windows 2008 R2 IIS Server\\_RUS\" for RUSSIAN Location", "template_file": "template_microsoft_iis_8,_8.5,_10_for_rus_server.xml", "name": "App IIS Service_RUS" }, { "version": 5.4, - "sync": 1646275496, + "sync": 1646290192, + "description": "## Overview\n\n16 Items, 4 Triggers 5 Graphs and 2 Screens built for IIS 7.5, 8.0, 8.5 and 10 Services, Ports and Performance Counters. Developed through \"Template Windows 2008 R2 IIS Server\\_RUS\" for RUSSIAN Location\n", + "template_file": "template_microsoft_iis_8,_8.5,_10_for_rus_server.yaml", + "name": "App IIS Service_RUS" + }, + { + "version": 6.0, + "sync": 1646290192, "description": "## Overview\n\n16 Items, 4 Triggers 5 Graphs and 2 Screens built for IIS 7.5, 8.0, 8.5 and 10 Services, Ports and Performance Counters. Developed through \"Template Windows 2008 R2 IIS Server\\_RUS\" for RUSSIAN Location\n", "template_file": "template_microsoft_iis_8,_8.5,_10_for_rus_server.yaml", "name": "App IIS Service_RUS" @@ -2912,7 +3465,7 @@ "name": "template_nginx_for_zabbix_3.4.x", "template": "App Nginx by Alex Gluck", "type": "template", - "sync": 1646275486, + "sync": 1646290172, "path": [ "Applications", "Web-servers", @@ -2923,14 +3476,21 @@ "versions": [ { "version": 5.0, - "sync": 1646275496, + "sync": 1646290192, "description": "## Overview\n\nSystem requirements\n-------------------\n\n\n* Nginx, [http://nginx.org](http://nginx.org/)/, with configured `http\\_stub\\_status\\_module`\n\n\nFeatures\n--------\n\n\nConnection Statistics:\n\n\n* Active\n* Reading\n* Waiting\n* Writing\n\n\nRequest Statistics:\n\n\n