Information Systems:Zabbix NMS - Revision history

Anmolm at 21:21, 24 October 2022

2022-10-24T21:21:11Z

Norwinu: /* Configuration */

2021-05-07T07:31:18Z

Configuration

Norwinu: /* Linux and Windows Agent */

2021-05-07T07:28:05Z

Linux and Windows Agent

Norwinu: /* Linux Agents */

2021-05-03T21:55:09Z

Linux Agents

Norwinu: Added Linux agent info

2021-05-03T21:53:37Z

Added Linux agent info

Norwinu: Norwinu moved page Information Systems:Zabbix NMS VM Appliance to Information Systems:Zabbix NMS

2021-05-03T17:30:38Z

Norwinu moved page Information Systems:Zabbix NMS VM Appliance to Information Systems:Zabbix NMS

Norwinu at 19:34, 26 April 2021

2021-04-26T19:34:04Z

Norwinu: /* Original notes */

2021-04-26T19:33:22Z

Original notes

Norwinu at 19:33, 26 April 2021

2021-04-26T19:33:08Z

Norwinu at 19:30, 26 April 2021

2021-04-26T19:30:15Z

@@ Line 3: / Line 3: @@
 * http://zabbix.unipharm.local/zabbix
-* Username is Admin
+* Username is admin
 * Password is zabbix
 * As of July 19 2019, AD logins are working but the above credentials are superior than an AD login.  The Linux appliance username is "appliance".

← Older revision		Revision as of 07:31, 7 May 2021
Line 26:		Line 26:

	This file must be edited after installation for the agent to be able to communicate with the server. Refer to one to see a typical config.		This file must be edited after installation for the agent to be able to communicate with the server. Refer to one to see a typical config.
		+
		+	The Zabbix agent on the client (or even the one that runs on the server for self-monitoring) can do more than self-monitor its hardware resources (CPU, memory, storage etc.). For example, the agent can monitor MySQL. The Linux servers do run MySQL (MariaDB) and therefore have been additionally configured to report on the local MySQL instance to Zabbix. Read official documentation on how this and other Zabbix agent extensions can be configured.

	==Additional Notes==		==Additional Notes==

@@ Line 19: / Line 19: @@
 ==Configuration==
 ===Linux and Windows Agent===
-The Zabbix agent can be installed on Linux servers for resource monitoring. Our current Linux server VMs are Debian-based, and therefore the zabbix-agent package is available in the apt repository. The configuration file is located in /etc/zabbix and has to be changed to point to the zabbix server.
+The Zabbix agent can be installed on Linux servers for resource monitoring. Our 2 current Linux server VMs (owl and uwdoss) are Debian-based, and therefore the zabbix-agent package is available in the apt repository. Zabbix also offers an agent for Windows, which is downloadable from their site. It is installed and run as a Windows service.
 ==Additional Notes==

@@ Line 18: / Line 18: @@
 ==Configuration==
-===Linux Agents===
+===Linux and Windows Agent===
 The Zabbix agent can be installed on Linux servers for resource monitoring. Our current Linux server VMs are Debian-based, and therefore the zabbix-agent package is available in the apt repository. The configuration file is located in /etc/zabbix and has to be changed to point to the zabbix server.
 ==Additional Notes==

@@ Line 17: / Line 17: @@
 As mentioned above, network discovery in Zabbix, at least for switches and printers doesn't work in an obvious way - it might but I couldn't figure it out.  Discovery of the VMware infrastructure does indeed work and infact it works a little too well.  The Host groups get a little untidy with how Zabbix displays virtual machines because it is showing by cluster and then by host so individual guests show up twice.  Anywho, as of July 2019, the config of how Zabbix displays and tracks statistic info from the VMHosts and from the guests is correct.  There are some yummy graphs in the Screens section and those screen should show anyone all the info they would ever need to see what's happening on the infrastructure.
-==Notes==
+==Configuration==
 ===Documentation to-do===
 * Zabbix configuration - /etc/zabbix/, number of pollers, unreachable pollers, SNMP monitors

← Older revision	Revision as of 17:30, 3 May 2021
(No difference)

← Older revision		Revision as of 19:34, 26 April 2021
Line 43:		Line 43:
	* External monitoring - this one appears to be super complicated but there may be potential for Zabbix to replace the 24x7 Zoho service we use. Of course the downside of that is that because Zabbix is a VM it is internal and dependent on everything else working to be able to properly monitor external sites. The extended thought is that Zabbix as a "thing" won't be able to alert on anything if either the VM hangs or the host it is on hangs or is otherwise down itself. Funny how we didn't build in that redundancy to the VMware environment.		* External monitoring - this one appears to be super complicated but there may be potential for Zabbix to replace the 24x7 Zoho service we use. Of course the downside of that is that because Zabbix is a VM it is internal and dependent on everything else working to be able to properly monitor external sites. The extended thought is that Zabbix as a "thing" won't be able to alert on anything if either the VM hangs or the host it is on hangs or is otherwise down itself. Funny how we didn't build in that redundancy to the VMware environment.

−	[[Category: I.T. Projects and Ideas]]
	[[Category: Power, Alarms, and Monitoring]]		[[Category: Power, Alarms, and Monitoring]]

@@ Line 34: / Line 34: @@
 ==Original notes==
- Darren originally wrote this page. Some stuff has since been addressed, but his comments - as well as old sections - will be moved here for reference.
+ Darren originally wrote this page. Some stuff has since been addressed, so his comments - as well as old sections - will be moved here for reference.
 * Updating Zabbix.  I don't know how to do this, so either leave the Linux appliance as is, which is safe, or do some command line advanced magic to do in place upgrades of the Zabbix ... files.  Oh and there is some sort of sharing page on the public Zabbix site where new or customized templates are available, that may be helpful in the future if we are using hardware that isn't included by default.  A lot of hours were put into getting Zabbix usable, please take care of it, at the very least take a snapshot before doing anything crazy so that you can revert back.

@@ Line 19: / Line 19: @@
 Updating Zabbix.  I don't know how to do this, so either leave the Linux appliance as is, which is safe, or do some command line advanced magic to do in place upgrades of the Zabbix ... files.  Oh and there is some sort of sharing page on the public Zabbix site where new or customized templates are available, that may be helpful in the future if we are using hardware that isn't included by default.  A lot of hours were put into getting Zabbix usable, please take care of it, at the very least take a snapshot before doing anything crazy so that you can revert back.
-==Things Still To Do==
+===Things Still To Do===
 * Zabbix does apparently speak WMI to Windows machines but I could not figure out how to do this because the documentation is not great.  It would be useful for Zabbix to get WMI info.
 * Better map icons.  The default icons that are available in Zabbix are very limited and don't make creating maps as easy as it could.  There is a way to import more icons/shapes but I wasn't able to get that far
 * External monitoring - this one appears to be super complicated but there may be potential for Zabbix to replace the 24x7 Zoho service we use.  Of course the downside of that is that because Zabbix is a VM it is internal and dependent on everything else working to be able to properly monitor external sites.  The extended thought is that Zabbix as a "thing" won't be able to alert on anything if either the VM hangs or the host it is on hangs or is otherwise down itself.  Funny how we didn't build in that redundancy to the VMware environment.
 ===Zabbix Upgrade - March 2021===
 Zabbix was upgraded from 4.2 to 5.2 (the latest version). This was its first ever upgrade -[[User:Norwinu|norwizzle]]. Some notes from the upgrade:
@@ Line 33: / Line 38: @@
 * Ubuntu had to be upgraded from 16.04 to 18.04. A general Ubuntu upgrade guide was followed. Caution should always be taken when performing a major OS upgrade. On the other hand, Zabbix was not being used much by anyone, so YOLO.
 * And then...Zabbix did not start upon the post-upgrade system restart. Turns out the upgrade overrwrote zabbix_server.conf (I was cavalier during the debconf/apt diff process) and the php conf in web/ and the DB password was now blank. The upgrade did ask for confirmation regarding this change, but looking at the diff, the removal of the DB password line seemed reasonable. It wasn't reasonable. A new password was set using <code>mysql -u root</code> then <code>SET PASSWORD 'zabbix'@'localhost' = '<hidden>'</code> etc. Zabbix booted after that.
 [[Category: I.T. Projects and Ideas]]