Pular para o conteúdo principal

Instalacao de Agente Zabbix em ambiente Windows

Introdução:

O monitoramento de servidores e/ou estações de trabalho com MS-Windows pode ser feito através do protocolo SNMP ou através do Agente Zabbix, neste tutorial será abordada a instalação do Agente Zabbix.

Obtendo os arquivos:

Podemos fazer o download do agente no site do Zabbix (external link), ou copia-lo do diretório que contém os fontes de instalação do Zabbix Server, neste caso os arquivos se encontram em zabbix-versão/bin, dentro deste diretório temos 2 sub-diretórios (win32 e win64) cada um respectivo a arquitetura do seu processador, a cópia do Linux para o Windows pode ser feita através do software WinSCP (external link).

Instalação:

Copiar ou Descompactar os arquivos, dependendo da sua escolha no passo anterior, na raíz do C:\, renomear a pasta para Zabbix.
Copiar ou criar o arquivo zabbix_agentd.conf dentro da pasta C:\Zabbix, um arquivo de exemplo pode ser encontrado no diretório que contém os fontes de instalação do Zabbix Server, no diretório zabbix-versão/misc/conf.

Conteúdo mínimo do arquivo zabbix_agentd.conf:

Server=IP do Servidor do Zabbix
Hostname=Nome da máquina Cliente
StartAgents=5
DebugLevel=3
LogFile=C:\Zabbix\zabbix_agentd.log
Timeout=3

Criando um serviço ZABBIX Agent no Windows:

Abrir um prompt de comando e executar o seguinte comando:
C:\Zabbix\zabbix_agentd.exe -i -c C:\Zabbix\zabbix_agentd.conf


Se tudo ocorreu bem você recebera as mensagens:
zabbix_agentd.exe [1540]: Service "ZABBIX Agent" installed successfully.
zabbix_agentd.exe [1540]: Event source "ZABBIX Agent" installed successfully.

Se desejar ver as demais opções do agente execute o seguinte comando:
C:\Zabbix\zabbix_agentd.exe --help


Verificando o status do serviço do Zabbix:

Iniciar // Painel de Controle // Ferramentas administrativas // Serviços:


Verificando as propriedades do serviço:

Duplo clique em ZABBIX Agent


Removendo o serviço:

Abrir um prompt de comando e executar o seguinte comando:
C:\Zabbix\zabbix_agentd.exe -d -c C:\Zabbix\zabbix_agentd.conf


Se tudo ocorreu bem você recebera as mensagens:
zabbix_agentd.exe [4156]: Service "ZABBIX Agent" uninstalled successfully.
zabbix_agentd.exe [4156]: Event source "ZABBIX Agent" uninstalled successfully.

Verificando se o serviço do zabbix foi removido:

Iniciar // Painel de Controle // Ferramentas administrativas // Serviços:


Criado por: André Déo

Comentários

Postagens mais visitadas deste blog

Upgrading Iomega ix2-200 to Cloud Edition

You just got your ix2-200 from eBay and there are no disks inside the NAS. Or you have a brand new ix2-200 -yet you could not afford Cloud Edition. No problem. With just a USB stick and a SATA adapter or desktop PC, you will easily upgrade your ix2-200 to ix2-200 Cloud Edition. Not only your ix2-200 will have a brand new interface and Cloud options, but also will become Mac OS X Lion compatible! What do we need? Decrypted! ix2-200 Cloud Edition Firmware 3.1.12.47838 S endSpace or RapidShare * USB Flash Drive with at least 2 GB capacity and LED indicator** SATA to USB adapter or desktop PC Toothpick or paperclip Preparing Hard Drives Preparing hard drives is the first step because you have to wipe all the data inside the hard drives and make them just like brand new. We used 2 x Seagate 2 TB 5900 RPM Drives. Backup any files if you have and then remove both disks from ix2-200 and attach them to SATA to USB adapter or your desktop PC's SATA port. Using ...

How to Fix sub-process /usr/bin/dpkg returned an error code (1)

Introduction The error message “Sub-process /usr/bin/dpkg returned an error code (1)” indicates a problem with the package installer. This can happen in Ubuntu after a failed software installation, or if the installer becomes corrupted. The key phrase in this error is /usr/bin/dpkg. This refers to the dpkg package installer for Linux. A package installer is an application that tracks software, updates, and dependencies. If it is damaged, any new software installation will cause this error message. We cover several possible solutions, from easily-solved and straightforward solutions to more complex processes. This guide will help you resolve the dpkg returned an error code 1 on an Ubuntu operating system. Prerequisites A user account with sudo privileges A terminal window/command-line ( Ctrl - Alt - T ) Options to Fix sub-process /usr/bin/dpkg returned an error code (1) Method 1: Reconfigure dpkg Database ...

Installing OpenVAS (GVM) on CentOS 7 (New Manual)

   This is a walkthough for installing and configuring OpenVAS (GVM) on CentOS 7. OpenVAS (Open Vulnerability Assessment System) is an opensource vulnerability scanner. Update 20April2019: Greenbone is deprecating OpenVAS version 9 and version 10 is now known as Greenbone Vulnerability Manager (GVM). Likewise, the new rpms are called ‘greenbone-vulnerability-manager’ and ‘gvm-libs’ which replace the ‘openvas’ and ‘openvas-libraries’ rpms. I f you are upgrading from 9 to the latest version, you may lose your previous tasks and reports so beware! Also, if you are still on version 9 and you simply need a temporary workaround for “Report outdated Scan Engine / Environment (local)” error, scroll to the bottom.  Brief History OpenVAS forked from Nessus when Tenable took the previously opensource product to closed source back in 2005. That’s worth mentioning primarily because on a side note, I’ve used Nessus for many years and I remember when it was forked. S...