|
||||||
|
Recap So in the previous post I put together a simple script for getting the data out of a specified registry entry that handled the REG DWORD BIG ENDIAN data type. In this one I’ll go over the general process of getting the registry based perf data into Zabbix and setting up alerting based [...] This is just an update, but the scripts I wrote for use with Nagios and ESX3i seem to work just fine with ESX4i (at least in my home lab environment using Dell Poweredge 2850s). BackgroundThis is the first of a couple of posts on how I’ve cobbled together some basic monitoring of Neverfail’s Neverfail Heartbeat H/A software which is also now the basis for VMWare’s vCenter Server Heartbeat. Since Neverfail seems to consider their command lines privileged information I will only cover how to do some simple monitoring using the registry. When starting on this effort internally I was only interested initially in figuring out a quick and simple way to get the info I needed and not so much on the how to get it into something part. I’ve been working with another team where I work to look at Zabbix as an alternative for some of the monitoring we do in our environment. We use Microsoft Operations Manager 2005 (MOM) but haven’t fully cut over from out previous monitoring solution. I had looked at Zabbix earlier as a potential solution for monitoring a bunch of VMware ESX boxes but another team ended up getting tasked with that particular duty. So I had had some experience with Zabbix but hadn’t done too much with it since. One of the things that’d been rattling around in my brain is using the capabilities of using the zabbix_sender feature/client to monitor some of other components/things we can’t easily get into MOM. Zabbix_Sender is a utility that is available for use with Zabbix that allows one to “send” information to Zabbix. In my case it was appealing because we’re already running two different monitoring agents on the Exchange servers where we have Neverfail installed. Since I only wanted to use Zabbix to monitor a small set of data related specifically to Neverfail zabbix_sender lets me do that without having to run the fullblown zabbix_agent as a service on the boxes. Continue reading Simple Neverfail monitoring with Zabbix part 1 Where I work we use AppAssure’s Replay product to back up some of our Exchange servers. Because the servers in question are very geographically dispersed we have multiple servers running Replay. Monitoring and keeping an eye on them to assure backups are happening properly was requiring more time than I wanted to spend because [...] I was working today on trying to write some scripts to help me better monitor our various installations of Neverfail. The command line tools they provide don’t provide all the performance information I need but (strangely enough) they do write some of it into the Registry where it gets updated very frequently. In writing [...] One of the things I wanted to check in looking at Zabbix was how hard it would be to use the Nagios plugins I wrote/modified for monitoring ESX 3i in Zabbix. It turns out that they are usable pretty much as is though there is a minor modification that needs to be made on how they accept/expect parameters. There are however a couple of ways to approach setting them up. Zabbix supports maintaining a couple of different kinds of data for external checks (as well as in general). These include:
The Nagios plugins I ‘m concerned in looking at will probably work with either the Log type or Integer. The external check “Item” type is just that a check. In and of itself it doesn’t make anything happen in terms of alerting or notifications. For that we need to set up “Triggers.” I’ll cover setting up an Item using Log type data in this post. Continue reading Creating Monitoring Items in Zabbix for Nagios plugins – part 1 (Log data) I’ve been working with one of my coworkers in looking at Zabbix for monitoring rather than Nagios for the Global Ops Virtualization rollout. I’ve already done work on some monitoring of ESX3i with Nagios by writing some plugins to monitor different hardware components. (For more info see this blog post) Zabbix supports multiple methods [...] I had a little time today and needed to mentally switch gears so I took a look again at the 3i storage script for Nagios and made some changes to it to clean it up a little bit. I also made clones…er …versions rather…. for monitoring CPU status, memory status, and sensor data (i.e. [...] In earlier posts when I mentioned the use of IPMI I don’t think I ever circled back around on where we stood with that. While we can get some information about the status of the hardware via IPMI I haven’t been able to figure out how to get at the array controller to get the status. I’ve looked at sites like Nagios Exchange and some others, but none of those had what I was looking for. I found one script that came close but would only tell me when the RAID disk was actually rebuilding, not when it was degraded. If we were to use RAID5 it might have been useful, but since we’re talking about going forward with RAID 6 to minimize our window of vulnerability and we’re using large disks. So that’s why I went back and looked at the VMware SDK and VI-Perl toolkit. Now that I have a script that will work from the command line I needed to take it and make it work for Nagios since that’s what we’ll probably end up using to monitor these servers once they’re deployed. (We’ll look at Dell’s IT Assistant again since we’re a dot version or two behind but I’m not holding out high hopes.) Continue reading Nagios Monitoring of ESX 3i on our PowerEdge |
||||||
|
Copyright © 2012 Carlos' Corner - All Rights Reserved
|
||||||
Recent Comments