Monitoring templates for Azure VM Supports reading diagnostic data for virtual machines on Azure. How to use. Create a VM with Zabbix installed Install Zabbix server manually according to the or use.
Install Zabbix agent on the same machine, and config to to talk to the server. The quick start sample will automaticlly do this. Prepare the hosting VM Install nodejs, and make sure 'node' and 'npm' command line is accessable via PATH environment variable.
Please find a stable version at, v6.10+ is recommended. Or please visit for installing using package manager. Clone the project and run setup sudo apt install -y git git clone pushd azure-zabbix-templates npm install npm run release popd.
Set up zabbix agent. Link the project to '/opt', you can also use any location you want, but remember to update azuremonitoringagentd.conf, so that it would point to correct path.
Copy config file for zabbix agent. Restart zabbix agent. Sudo ln -s $(pwd)/azure-zabbix-templates/dist/azure-zabbix-templates /opt/azure-zabbix sudo cp azure-zabbix-templates/conf/azuremonitoringagentd.conf /etc/zabbix/zabbixagentd.conf.d/ sudo service zabbix-agent restart.
Setup conf.json If you haven't got powershell for Windows installed, please check page.aspx). From a powershell console, log in an Azure account, then run genconf.ps1, it would automatically scan all VM with diagnostic data, and generate a 'conf.json'. Copy 'conf.json' to /opt/azure-zabbix/lib/. Import zabbix tempate Import 'conf/azuremonitoringtemplstes.xml' through Zabbix portal, and link the current host to template 'Azure Monitoring'. Screenshots Monitoring CPU usage percentage of same period on Azure portal and Zabbix Portal: Contributing This project welcomes contributions and suggestions.
Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. This project has adopted the.
For more information see the or contact with any additional questions or comments.
Parameter Description Name Unique name of the rule. For example, “Local network”. Discovery by proxy What performs discovery: no proxy - Zabbix server is doing discovery - this proxy performs discovery IP range The range of IP addresses for discovery. It may have the following formats: Single IP: 192.168.1.33 Range of IP addresses: 192.168.1-10.1-255. The range is limited by the total number of covered addresses (less than 64K).
IP mask: 192.168.4.0/24 supported IP masks: /16 - /30 for IPv4 addresses /112 - /128 for IPv6 addresses List: 192.168.1.1-255, 192.168.2.1-100, 192.168.2.200, 192.168.4.0/24 Since Zabbix 3.0.0 this field supports spaces, tabulation and multiple lines. Delay (in sec) This parameter defines how often Zabbix will execute the rule. Delay is measured after the execution of previous discovery instance ends so there is no overlap.
![]()
Checks Zabbix will use this list of checks for discovery. Supported checks: SSH, LDAP, SMTP, FTP, HTTP, HTTPS, POP, NNTP, IMAP, TCP, Telnet, Zabbix agent, SNMPv1 agent, SNMPv2 agent, SNMPv3 agent, ICMP ping.
A protocol-based discovery uses the net.tcp.service functionality to test each host, except for SNMP which queries an SNMP OID. Zabbix agent is tested by querying an item in unencrypted mode. Please see for more details. The 'Ports' parameter may be one of following: Single port: 22 Range of ports: 22-45 List: 22-45,55,60-70 Device uniqueness criteria Uniqueness criteria may be: IP address - no processing of multiple single-IP devices. If a device with the same IP already exists it will be considered already discovered and a new host will not be added.
Type of discovery check - either SNMP or Zabbix agent check. Enabled With the check-box marked the rule is active and will be executed by Zabbix server. If unmarked, the rule is not active. It won't be executed.
Download Zabbix Agent For Windows
Changing proxy setting. Defining a network discovery rule for our IP range. Zabbix will try to discover hosts in the IP range of 192.168.1.1-192.168.1.254 by connecting to Zabbix agents and getting the value from system.uname key. The value received from the agent can be used to apply different actions for different operating systems. For example, link Windows servers to Template OS Windows, Linux servers to Template OS Linux. The rule will be executed every 10 minutes (600 seconds).
Zabbix Free
Playclaw keygen download mac. When this rule is added, Zabbix will automatically start the discovery and generating discovery-based events for further processing.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |